This forum has moved to a new location and is in read-only mode. Please visit talk.octobercms.com to access the new location.

g.frenken54258
g.frenken54258

Hi guys,

On websites where the client is hands-off, we can make changes locally, push them to GitHub and deploy them to production, this is not a big deal.

But what if you have a client that creates blog posts, content pages and uploads media on the production website? How could we go about handling version control? Obviously we can't just make changes and deploy them as they would overwrite our client's changes and our clients are non-technical so they can't possibly use a code editor or GitHub.

How do you guys handle these situations? No version control at all, or is there another option I should be aware of?

adaroberts67076
adaroberts67076

If you're using an atomic deployment strategy you should have your storage folder in a shared location across all deployments so that it's not overwritten on deployments, and you should also use the database templates feature that was designed for this use case: https://octobercms.com/docs/cms/themes#database-driven-themes

1-2 of 2

You cannot edit posts or make replies: the forum has moved to talk.octobercms.com.