JC1

It’s a long time crusade from RFK. No need to short the stock or anything. RFK is just applying his dogma instead of real science and since he believes in bullshit, he will try to do everything he can to shut down science in favour of his beliefs. At this point the question is out on how many millions of deaths he will be responsible for with his policies, but it sure will be in the millions. He’s an agent of death.

Trump is just a puppet.

This happens in some part of downtown here, mainly the business district. It’s dead during any part of the day other than noon on weekdays. The reason isn’t high fees, it’s just that it’s a boring part of the city center where there’s nothing to do and it’s very very car focused. Not a lot of interesting places can sustain by catering to cars. Every other part that isn’t infested with cars is vibrant with life at any time of day. Raising parking fees, removing parking and removing car trafic has the opposite effect : it makes it so that the city center stops suffocating under cars.

Unfortunately, the idea of the city center being sustained by suburbs with cars is just a myth. It’s mostly strangled by them in most north american cities. It can sustain on it’s own by catering to the population that lives in them or close by. And if there’s not enough population, densify. A focus on active transportation and public transit is the way to go.

I work per stack. Each stack can have multiple services/containers. So one db per stack. I usually work with the compose file provided by the app I want to run and they usually provide their database container in those. My persistent data for a stack is in a single folder for every services. For backup, I only have to backup the compose and environment files and also the persistent folder and that’s it. Every stack is independent from each other so it’s easier to move them from a server to another if I want to use more than one server.

I used to use only one db container for all db. It worked well, until I had a data corruption issue. I had to rollback from a backup for all services that used this db. Then I moved to 1 db per stack and it happened again, but this time, only that stack was impacted, so no big deal. Just did a rollback and everything was fine.