Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to Docker/ansible hybrid hosting solution #41

Open
carlnewton opened this issue Jan 26, 2025 · 1 comment
Open

Move to Docker/ansible hybrid hosting solution #41

carlnewton opened this issue Jan 26, 2025 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Milestone

Comments

@carlnewton
Copy link
Owner

No description provided.

@carlnewton carlnewton converted this from a draft issue Jan 26, 2025
@carlnewton carlnewton added enhancement New feature or request help wanted Extra attention is needed labels Jan 26, 2025
@carlnewton carlnewton added this to the Phase 1: Core milestone Jan 26, 2025
@carlnewton
Copy link
Owner Author

Nutomic, a Lemmy developer has advised a way that Lemmy solves a problem I'm having with supporting both Docker container hosting and linux server hosting. Lemmy supports provisioning of a linux server with docker-compose, and then running docker containers on that server. This approach should unify efforts in config by moving everything into the docker config.

The unknowns in this area are quite daunting for me, but I know that it'll be the right solution going forward so here's a bunch of the things I need to understand before I can adopt it:

Deployment - Docker hosting solutions have to hold the container process open, once it is stopped, the container is destroyed. This would presumably not be the case in our scenario here, and so we could perhaps still use PHP deployer for deployments. What that looks like in practice, I'm not sure.

Database - Perhaps, just as with local development, a second container for mysql should be created. What would this mean in terms of backups etc?

Image storage - How does Lemmy deal with growing storage demands? Does it also support something like AWS S3? Does it suffer from fixed volume sizes?

Swap - On what layer will the swap need to exist? Perhaps both?

Once I have explored how Lemmy (and presumably Mastodon) deals with the above, I can then make the decision as to how best to deal with them for Habitat.

@carlnewton carlnewton moved this from Todo to In Progress in Habitat Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
Status: In Progress
Development

No branches or pull requests

1 participant