CodingAdam
AP Explains: How computers see faces and other objects
5 military phrases for DevOps practitioners
WordPress Deployment: Deploying WordPress with DeployBot
Using Custom Containers in DeployBot
New in DeployBot: Deploy Config Files Only
GitHub vs. Bitbucket
SRE vs. DevOps: What's the difference?
How Git Changed the History of Software Version Control
How to Migrate from GitHub to GitLab?
Ballerina: An API-First Programming Language
Continuous development
GitHub vs. GitLab
Devs are flooding to GitLab amidst GitHub Microsoft acquisition rumors
GitLab vs. GitHub: What’s the Right Hosting Platform for Your Workflow?
So what we did, was on the new projects we started using DeployBot, which was very nice especially for the development team. Then we started to see what can we do on the legacy projects and once we have more time from other projects we tackle one older project at a time where we automate at least parts of it.
It can be a very annoying process especially if you have people in your team who where used at a certain style of the process, but I think in the long run it was worth it.
But if this is something too much to do and will eventually harm the product since you said it its a two person team, then its probably best to let them know that you cannot offer that service but be ready to offer them some advice/recommendation, for example if you have a company in mind that could do the job.