This is a copy of the Github readme.
Find the original on https://github.com/liporuwcha/c___configuration_migration_updates

c___configuration_migration_updates

liporuwcha namespace c___ configuration, migration, updates

work-in-progress rustlang postgres License c_configuration_migration_updates

c___ configuration, migration, update

Every project evolves and the code and the database need to be updated. Sometimes it is called "migration". Living with a database is very dynamic. Much more than just living with a program.

The same database can contain more than one project coded by different teams. The order of changes must not be linear. It means, that the team must know what projects are exclusively theirs and what projects are common and must be coordinated with other teams. When writing the code it must be always careful, that it does not break when a new field is added.

To achieve integrity of the database all the code is concentrated inside the database. So other parts of the project can use common code.

ca__ database objects

cj__ migration

how to migrate every table separately. Ideally without server downtime.

cs__ backup and restore

ct__ development, testing and production environment

Open-source and free as a beer

My open-source projects are free as a beer (MIT license).
I just love programming.
But I need also to drink. If you find my projects and tutorials helpful, please buy me a beer by donating to my PayPal.
You know the price of a beer in your local bar ;-)
So I can drink a free beer for your health :-)
Na zdravje! Alla salute! Prost! Nazdravlje! 🍻

//bestia.dev
//github.com/bestia-dev
//bestiadev.substack.com
//youtube.com/@bestia-dev-tutorials