Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
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: I have a developm...
#2: Post edited
by
Mu3
·
2022-02-11T08:20:36Z (almost 3 years ago)
Updated question
- 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.
## Questions* What is a good way to set up development/production databases?* What would be necessary to self-host the entire pipeline?
- 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?
#1: Initial revision
by
Mu3
·
2022-02-10T09:06:10Z (almost 3 years ago)
Best practices in setting up a development & production environments
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. ## Questions * What is a good way to set up development/production databases? * What would be necessary to self-host the entire pipeline?