this post was submitted on 29 Oct 2023
1 points (100.0% liked)

Self-Hosted Main

502 readers
1 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
 

Hey there!

I am building an open-source project, built with React and NestJS. This in turn has a few dependencies on certain services, all running from docker (postgres, minio, browserless etc.).

I need some guidance on how I can package this as a single open source project, that would make it easier for folks to just pull and image and run as-is, or copy the docker-compose.yaml and have it running on their system.

I'm facing issues particularly with how to allow all these different services to communicate with each other. My hunch was to use a single nginx config that would route requests to minio, browserless, the client or the server depending on their route, but I do not have much experience with nginx either (also, not sure if that provides the best experience for self-hosters, hence why I'm posting this question here).

How can you help, you ask? A brief description of what services I can use to orchestrate this architecture, or a GitHub repository where you or someone else has done something similar might help.

I would be very very appreciative of anyone who can help, I've been stuck on this for the past week. It feels really depressing especially to have put in so much into the product to build it well, but run into a wall because I don't know how to package it to users.

top 1 comments
sorted by: hot top controversial new old
[–] [email protected] 2 points 10 months ago

They way that most projects I've seen that have multiple dependencies handle this is to just provide an example docker compose file. I really think that's all you need. Personally I really don't want an "overpackaged" solution, because that just adds bloat and takes away flexibility. I don't need yet another proxy running, if I need to proxy access to some service, I'll integrate it into my existing proxy.