[davismwfl]

Keep it simple, if it is only you making changes and your primary business is selling on the site and not the software then just use something like rsync or ssh/scp etc and script it. At most use something like ansible, chef or puppet.

If your primary thing is the software and you are deploying many times a week, then it can make more sense to have more sophisticated controls, but even then as one person a few scripts is usually plenty good enough.

If your primary business is the products you sell and not the software, I would be curious why you chose to build a shopping cart/e-commerce solution. There are so many good solutions out there it is usually just a distraction to build your own unless you have hit a large scale or are in just such a custom niche that nothing works for your product/service unless you write it.

[rbarnes01]

Primary business is selling products, and we have been building off an existing solution because of regulatory requirements.

Fortunately when everything is complete we would only need to focus on upkeep and maintenance, but it would be nice if we set a system in place now to avoid pain down the road.

[davismwfl]

Cool, yea regulatory is one of those niche things that can require a custom solution for sure.

I personally like Ansible especially when going from manual to automated as you can incrementally add to it but get using it quickly. Overall Ansible is pretty simple and it is super flexible without adding unnecessary complications. You can have it run your tests and make sure they all are passing before it moves the new software as live.

Plenty of consultants are available and can set it up for you if you need it done fast or it really isn't hard to learn if you have a little time.