3 ms·
I agree. MediaWiki is a solid solution and is very easy to setup. You can one-click deploy on DigitalOcean for $10/month and just enable daily snapshots. You ca
by movedx 2y ago
I agree. MediaWiki is a solid solution and is very easy to setup. You can one-click deploy on DigitalOcean for $10/month and just enable daily snapshots. You can even use a managed DB if you want.
- snozolli 2y agoYou can one-click deploy on DigitalOcean for $10/month Am I the only person left who simply has a web server? Untar Mediawiki, edit a few config variables, run an established database script, and off you go. Maybe I'm wildly out of touch, but I don't see why everything has to be a container or a monthly paid service around here. I get it for something like an email server, where misconfiguration could lead to your server being a zombie, but I don't get it for something like a wiki.
- Arrowmaster 2y agoContainer makes it easy to update. I don't need to go read the instructions about which files I need to replace or what to do about modified files. If it's built properly to run from a container and uses sane version numbering, all I need to do is pull the new image and restart the container. There are still plenty of not sane container builds that don't make it easy. If I need to checkout a git repo and mount a path into the container it's not sane. Pulling an image and starting a docker-compose should be all that's needed.
- deleted 2y ago[deleted]
- 1oooqooq 2y agoand subscribe to yet another security announce email, i hope
- movedx 2y agoActually I’m on your side there. I have three servers in the garage on a 250mbit private fibre link… that I never use. I want to get my backside in gear and get the ProxMox cluster running a bit of web infrastructure and then forward to it on the Mikrotik that terminates the fibre. The only reason I recommended DO is it’s just simple and not too expensive. But your point is fair.