Consultant, Full Stack Dev, Game addict. Tech Lead @ MOBIKO. Loving Nodejs, Typescript and Vue. Interested in Clean Code, agile methods and Software Engineering
There are a few strategies here but docker is just a vessel. You would perform the same steps as if you didn’t use docker
that basically means I would have to
shutdown the container
install a local postgresql database service in the old version
mount the database
run the upgrade installer which updates the database files to the current version
start a container with the new version having mounted the updated database files
For every Environment that was deployed?
Isn't that the point where every developer wants to shoot himself, if he ever brought up docker to the table?
Assuming they are compatible and there are no breaking changes you could roll out the new container
I'm coming from IT Service Management (Patch Management, Software deployment and so on) and pretty much every application does something in their update scripts (which is, of course, why they exist), that's why this sounds really shocking to me...
My professional interests are cloud and big data technologies, machine learning, and software development. I like to read source code and research papers to understand how stuff works.
Pronoun: He
Isn't that the point where every developer wants to shoot himself, if he ever brought up docker to the table?
I guess that's the point where you should think about either automating the work or using a managed DB. You could of course also attempt to modify the existing container and save the state but that kind of defeats the purpose of Docker.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey,
thank you for your answer.
that basically means I would have to
For every Environment that was deployed?
Isn't that the point where every developer wants to shoot himself, if he ever brought up docker to the table?
I'm coming from IT Service Management (Patch Management, Software deployment and so on) and pretty much every application does something in their update scripts (which is, of course, why they exist), that's why this sounds really shocking to me...
I guess that's the point where you should think about either automating the work or using a managed DB. You could of course also attempt to modify the existing container and save the state but that kind of defeats the purpose of Docker.