New deployment type
The current deployment should be changed. For that the Wiki files and config should be on this repo.
After doing that and open-sourcing the custom theme (#3), the deployment should work like this:
- Use Dokuwiki Docker file
- Pull wiki and theme files from the according repos
The following should be apply:
- Nothing (except the config for the user management) should have to saved on the server, so no volume.
- About the parathesis in the point above, maybe that can be implemented in an .env file. I'm pretty sure that Dokuwiki doesn't support this for the current auth setup, so a few changes to Dokuwiki are necessary.
- When a change is made over the web overview, it will be saved on the server (better said inside the Docker VM), so there needs to be some kind of sync. Either on file change there should be a git fetch or every few minutes, if something has changed.
- It should be possible to change the config on the repo and the server should fetch those and not break because of git conflicts.
- Maybe the config and wiki data should be seperated into two repos, as the wiki data should not be changed over git, except for the server.
Why do this?
- This basically serves as a backup of the info on the Wiki
- If something does happen with the server this would be easier to redeploy than the current solution
- This ensure that changes on the Wiki are replicable and that the Wiki maintainers can spin it up locally and test changes on the config without breaking prod