We’re working on a site with several pages, one of which has to be a blog, and we’re wondering what’s the best approach to this.
- It should be possible to create/update an article ASAP without involving the developers.
- It should run on Amazon Elastic Beanstalk since we already use it and we need all of its features.
- The developers should be able to easily merge the site content locally so they can work on the site.
Since Kirby is file based, we can’t easily download any changed files on the live Amazon EB instance. I also don’t know if those changed files play well with the Amazon CDN. That’s why at the moment, our content folder is in a separate repo and we have a staging server with Kirby AutoGit installed. Editors change content on staging, we pull it, merge it, and create an Amazon EB deploy with the new content. This whole process takes too long for goal #1.
Do you have any ideas how we could make that work?
We’re thinking of using Kirby 3’s new database functionality for the blog and managing the rest of the content as we currently do. We have an idea of how to edit the site so that it uses a database, but we have issues figuring out all the rest - how we should configure it with Amazon, how we would push/pull changes, how we could roll back EB deploys and sync the database…