bookwyrm seems neat but un-docker-ifying it seems like a bunch of work
maybe for another day
maybe for another day
spins up its own nginx and postgres and all sorts of shit
I just wanna run the service and integrate it with my other stuff
I just wanna run the service and integrate it with my other stuff
okay so getting rid of nginx and psql seems simple enough, those are fairly standard
also if I ran this on an existing machine with an existing db it’d fight with the database so that’s spectacularly stupid
volumes:
- pgdata:/var/lib/postgresql/data
you know what? there's an open issue to write docs to accomodate non-docker usecases
I'm just going to wait until someone does that rather than try to figure out how to cut this stuff out of docker
I'm just going to wait until someone does that rather than try to figure out how to cut this stuff out of docker
:BlobhajTransPrideHeart:
@izaya@social.shadowkat.net
@2ck All of the above. Docker encourages a bunch of bad practices, but for my specific usecase I already have a containerisation system - LXC - set up. The docker setup here also doesn't allow me to configure it to use my existing nginx and postgres.
@izaya makes sense. LXC is better somehow? never used it
@2ck LXC is designed for a different usecase; it's not "download a container and run", it's "install an OS inside a container and your software on that," like virtual machines but lighter
@izaya I think I understand. https://www.upguard.com/blog/docker-vs-lxc helped characterize the differences for me.
