Infrastructure: Difference between revisions
Appearance
| Line 5: | Line 5: | ||
=== To-do === | === To-do === | ||
* Set <code>$wgCapitalLinks</code> to <code>false</code> | * Set <code>$wgCapitalLinks</code> to <code>false</code> | ||
* Attempt to make a back up and restore to local machine. If successful: | |||
** Take snapshots and keep them in my standard set of backed up files. | |||
** Automate the mirroring of the source-of-truth VPS wiki to a home-based LAN server. | |||
* Get file uploads working | * Get file uploads working | ||
* Change logo | * Change logo | ||
Revision as of 20:52, 20 May 2025
This wiki
This wiki is served from a Docker container running Mediawiki, reverse-proxied by Caddy. It works well and wasn't too hard to set up.
To-do
- Set
$wgCapitalLinkstofalse - Attempt to make a back up and restore to local machine. If successful:
- Take snapshots and keep them in my standard set of backed up files.
- Automate the mirroring of the source-of-truth VPS wiki to a home-based LAN server.
- Get file uploads working
- Change logo
- Install markdown extension? Or does madness lie down that path?
Caddy
For later
https://github.com/DoTheEvo/selfhosted-apps-docker
Try these two configs out:
subdomain1.example.com {
# Static files. More info: https://caddyserver.com/docs/caddyfile/directives/file_server
root * /host_path/to/your/files
file_server
}
subdomain2.example.com {
# Reverse proxy to a service on the host. More info: https://caddyserver.com/docs/quick-starts/reverse-proxy
# Maybe useful for working on a Flask site outside of Docker-land. Does it work?
reverse_proxy 172.17.0.1:8080
}