![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
And can be automated easily.
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.
Not only neurodivergent people need the “/s”. Not all subtle speech cues are easily transmitted through text.