You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm new to deploy automation.
Here we have a backend app made in golang, coded by a team with two developers.
Our code is versioned in bitbucket git.
The deploy environment is a DigitalOcean droplet (vps).
I'm not using Docker, once each app runs in a dedicated server. But if you tell me a good reason, I'll be happy to use it.
Our goal is to send one directory with an executable, one static assets directory and a single config json file.
Our current procedure today is:
- Git push to master;
- Git pull ( from target/deploy server )
- delete previous version
- go build and copy the executable to target directory
- copy the other asset files to destiny folder
- run the app ( as nohup )
How to move from this manual procedure to automated mode, considering our simple scenario?
Is Bitbucket Pipelines the best option?
Is it better to build in my machine and send the executable, or git-pull from deploy machine and then build there?
Should I use another ci tool, like rundeck?
Am I looking to the wrong direction?