Selfhosted

40441 readers

811 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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

Are you reusing one postgres instance for all services? (jemmy.jeena.net)

submitted 8 months ago* (last edited 8 months ago) by [email protected] to c/selfhosted

41 comments fedilink hide all child comments

I have many services running on my server and about half of them use postgres. As long as I installed them manually I would always create a new database and reuse the same postgres instance for each service, which seems to me quite logical. The least amount of overhead, fast boot, etc.

But since I started to use docker, most of the docker-compose files come with their own instance of postgres. Until now I just let them do it and were running a couple of instances of postgres. But it's kind of getting rediciolous how many postgres instances I run on one server.

Do you guys run several dockerized instances of postgres or do you rewrite the docker compose files to give access to your one central postgres instance? And are there usually any problems with that like version incompatibilities, etc.?

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

[+] marcos -18 points 8 months ago (5 children)

Do not run databases in Docker unless you know really well what you are doing.

It's completely possible to run them correctly in Docker. But it's far from trivial, and if you need to ask this, it means that you probably won't be able to.

[–] foggy 19 points 8 months ago* (last edited 8 months ago) (4 children)

Nothing worse in Linux communities than gatekeeper answers like this.

It's fine to point out that something's challenging to someone who may be a novice, but to suggest it's above them? Eat it. At the very least, provide a resource and let them confirm for themselves.

[–] richmondez 5 points 8 months ago (1 children)

This right here... This whole community is about learning to do things for yourself. It might be after been given resources to learn you do decide its too much for you but people should be given the chance to discover that themselves.

[–] foggy 1 points 8 months ago

Shout out to hack the box.

If you're a noob or a veteran in any branch of IT looking for a good cybersecurity community/platform...

Most of us IT folk check the box of "knowledge peaks and valleys". They're the first community I've found that seems to actually respect the idea that someone might know way more about XSS and SQL injection in react apps than some other guy knows about binary exploits through packet disassembly, and that both of them are fucking experts and neither of them are lacking for not knowing what the other knows.

load more comments (2 replies)