Buddy is a Git and Continuous Delivery Platform.
See Buddy homepage for more information.
TODO: Marko will create documention with screenshots.
- Select your Git Provider: GitHub
- Select your Git repository
- Create
- Skip "Create your first action" step
- Delete "My first pipeline" pipeline
- In the project view, select Add a new pipeline
- Select "Clone existing pipeline"
- Select some pipeline e.g. "Deploy to Testing" from some project
- Select "Clone all action from this pipeline"
- Clone actions
- User account to Buddy application
- Buddy IPs whitelisted in firewall(s) for the targeted server(s)
- Buddy public key on the server(s)
- Name:
Deploy to Testing
- Trigger mode:
on every push
- Branch or tag assigment:
development
- Make database backup
- Create a new build and make and artifact file (e.g. in Docker)
- Upload the artifact file to targeted server
- Extract artifact to
releases
- Symlink e.g.
public
toreleases/release_${execution.id}
(where public is the webroot) - Run any after deploy commands needed
- On success: inform on Slack channel and/or send email
- On failure: inform on Slack channel and/or send email
These are the IPs where commands against the server originate from and they must be allowed by the firewall.
If your firewall supports adding DNS source, make sure to whitelist the new servers with this command:
iptables -A INPUT -p tcp -s workers.buddy.works -j ACCEPT
Current list of deployment IP’s:
91.200.38.2
108.163.203.146
184.154.12.42
184.154.193.210
13.59.138.22
18.220.79.31
18.221.94.43
18.220.233.117
52.14.34.6
52.15.76.37
Buddy public keys are project relative. You can find the public key from actions which need access to your servers.