I am developing a web app that is tied to a database. My codebase is stored on a private GitLab instance. I would like to set up a workflow that would look something like this:

1. I have a development environment where I am free to do anything with the app or the database. Once I made changes, I commit them to the GitLab instance.
2. GitLab builds and tests the app as well as executes all necessary migrations for the database. Ideally this is first done in a test environment.
3. If step 2 is successful, the code is deployed to the production server.

I would like to host this app on my local network, so no hosting solutions like AWS. I can get a reasonably powerful tower to act as the server.

However, when looking into it I found differing opinions on what this setup should look like, especially the differences between development and production databases. Therefore, I am curious if there are some general "best practices" that I can apply to this system.

Question

• What would be a good way to set up a development database in a way that is still resembles the production one, but at the same time is easy to configure and work with?

posted almost 3 years ago

CC BY-SA 4.0

3y ago

Mu3‭

29 reputation 1 0 5 1