It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
Adding the backup file to the image means that you have to rebuild the image whenever it changes. Mounting a directory from the host system as a volume would be more efficient. You might have to write a proper Dockerfile to do that though, I've never created images from running containers.
You are correct, but I think building a final image can be helpful when database development is completed and then we can push it to the docker-hub, so that anyone pulls that image can have a preset database.
Please let me know if any better option is out there.
Thanks :)
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.
Adding the backup file to the image means that you have to rebuild the image whenever it changes. Mounting a directory from the host system as a volume would be more efficient. You might have to write a proper Dockerfile to do that though, I've never created images from running containers.
Hi Dian,
Thanks for your feedback.
You are correct, but I think building a final image can be helpful when database development is completed and then we can push it to the docker-hub, so that anyone pulls that image can have a preset database.
Please let me know if any better option is out there.
Thanks :)