Selfhosted

39251 readers

283 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Adding services to an existing Docker nginx container (lemmy.ca)

submitted 8 months ago* (last edited 8 months ago) by mudeth@lemmy.ca to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

Hi, I'm just getting started with Docker, so apologies in advance if this seems silly.

I used to self-host multiple services (RSS reader, invoicing software, personal wiki) directly on a VPS using nginx and mariadb. I messed it up recently and am starting again, but this time I took the docker route.

So I've set up the invoicing software (InvoiceNinja), and everything is working as I want.

Now that I want to add the other services (ttrss and dokuwiki), should I set up new containers? It feels wasteful.

Instead, if I add additional configs to the existing servers that the InvoiceNinja docker-compose generated (nginx and mysql), I'm worried that an update to Invoiceninja would have a chance of messing up the other setups as well.

It shouldn't, from my understanding of how docker containers work, but I'm not 100% sure. What would be the best way to proceed?

you are viewing a single comment's thread
view the rest of the comments

[–] Illecors@lemmy.cafe 2 points 8 months ago (1 children)

I would suggest having an nginx as a reverse proxy (I prefer avoiding a container as it's easier to manage) and the have your services in whatever medium you prefer.

[–] mudeth@lemmy.ca 1 points 8 months ago (1 children)

Yes, that's exactly what I'm doing now, I was only unsure about how to map the remaining services - in the same docker containers, or in new ones.

[–] Illecors@lemmy.cafe 1 points 8 months ago (1 children)

Separate. That's the whole point of containerisation! Otherwise you're just doing a regular deploy with extra steps

[–] mudeth@lemmy.ca 0 points 8 months ago (1 children)

Thank you. Yes makes sense. I guess it's fairly obvious in hindsight.

[–] Illecors@lemmy.cafe 2 points 8 months ago