Development environment #40
BenasB
announced in
Announcements
Replies: 4 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
1 reply
-
Update: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Continuous delivery/deployment
We're already using CI for our PRs, so the next logical step is to embrace CICD as a whole – implement the CD part. For the time being, only a
dev
elopment environment should suffice our needs.What does that mean for developers?
When you push changes to the
dev
branch, an automated system will pick it up, rebuild our projects and deploy them – we'll have a dedicated environment showing the current development state of our application. You will be able to go to some URL and see the application (as if it was "released" but just for development purposes). This is a common practice. As developers, we'll be able to see our progress on the application incrementally without needing to pull new changes and run them locally.The plan
I have spent a significant amount of time researching various options and decided on the plan:
apsitvarkom-infra
createde2-micro
Compute Engine VM and run whatever SQL server we like, so we'll be fine.P.S. I will handle this part, since it's pretty advanced stuff (for a uni project)
Beta Was this translation helpful? Give feedback.
All reactions