I've got a Git server on a Synology at my office where we host our webapp's master repo. The network has a static public IP, and we've got several servers behind a load balancer running a replicated version of our webapp. I'm looking to establish a solid CI/CD pipeline that allows for seamless updates from the master repo to these replicated servers. Ideally, I'd like to automate SSH logins to each server to perform a 'git pull' from the Synology's public IP whenever there are changes to the master repo. I'm using Panic's Nova for this. Is this approach solid, or should I consider doing it differently? Perhaps I should SSH from my local machine and 'git push' instead? I'd really appreciate any advice or best practices you might have!
2 Answers
Are you using Synology's built-in Git service or perhaps a containerized solution like Gogs or GitLab? There are a few different ways you could handle the CI/CD setup depending on that choice. If it's just the native Git, you might have limited features compared to these other options.
I came across this guide on DigitalOcean about automatic Git deployment with a VPS, but it seemed a bit complex. You might want to check it out to see if it sparks any ideas for your setup. Just remember that simplifying the process is key for CI/CD.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures