It’s such a difficult topic. I have family that left their country because, although they can adopt a child as a same sex couple, the culture is so bigoted they dont want to subject their future children (and themselves) to the sort of interactions they have to deal with.

I prefer 100 quality posters to 100,000 shitposters.

Not just making but interpreting can be very good too. One can learn the basic chords and play almost any song.

And can be automated easily.

You usually want to prioritize changing the container’s build config instead of getting into them and modifying them. Much better to get into the mindset of them not being pets you have to nurture.

Separating the different services into containers is overall a good practice but having the DB in one can be a pain as it’s easier to work with stateless applications. The isolation aspect is very valuable as its easier to debug a problem. I would look into container orchestration if there isn’t already and making sure logs are centralized first.

The problem is that it’s public. A private company could very well exist to sell to its users a good service. It being public means it’s beholden to the investor’s desire for constant growth.

The problem is that it’s public. A private company could very well exist to sell to its users a good service. It being public means it’s beholden to the investor’s desire for constant growth.