I'm a noob when it comes to devops, so you might not want to do it my way.
I keep it super simple. I have a git repo where I directly commit into master. When I want to take the changes live I ssh onto my VPS, I git pull the changes and restart the website service.
I use an SQLite DB that I automatically copy (backup) to my local machine daily via the Windows equivalent of a cron job. Once it's on my local machine it's also backed up to other places as part of my local backup process.
I run my tests manually when I think I've made significant changes.
Otherwise I just react to errors ASAP (I get an email notification from sentry when a new error occurs)
A lot of this doesnt work with a bigger team of course.
It's a balance between risk and time investment. The simpler your dev ops stuff, the higher your risk of introducing bugs into production. But it saves you a lot of time not dealing with that stuff.
I keep it super simple. I have a git repo where I directly commit into master. When I want to take the changes live I ssh onto my VPS, I git pull the changes and restart the website service.
I use an SQLite DB that I automatically copy (backup) to my local machine daily via the Windows equivalent of a cron job. Once it's on my local machine it's also backed up to other places as part of my local backup process.
I run my tests manually when I think I've made significant changes.
Otherwise I just react to errors ASAP (I get an email notification from sentry when a new error occurs)
A lot of this doesnt work with a bigger team of course.
It's a balance between risk and time investment. The simpler your dev ops stuff, the higher your risk of introducing bugs into production. But it saves you a lot of time not dealing with that stuff.