10 comments

  • Kyle ConradKyle Conrad, 7 months ago

    It would be interesting to read more about how they handled the local/production dev environment and database situation - was recently working on a project, had a terrific local install and database set up, and could not solve how to deploy it. Ended up having to manually install Craft on the server, rebuild the plugins and structure, and then manually copy and paste all of the content over. Without doing this (and this was only a single dev contributing), the production install failed every time, or had database issues, or whatever - it just wouldn't work at all. It seems like it's the one thing that other CMS's have solved (whether built in or through plugins) that Craft just doesn't have a solution for (or a plugin that does it).

    4 points
    • Roel van HintumRoel van Hintum, 7 months ago

      Since Craft 3.1 they have a project config (useProjectConfigFile) available solving the migration issue. There are also plugins, but this is the nicest solution. https://docs.craftcms.com/v3/config/config-settings.html#useprojectconfigfile

      1 point
      • Kyle ConradKyle Conrad, 7 months ago

        I believe I tried doing this (it might've been on the version right before 3.1, this was about a month and a half ago), but the system kept telling me my project.yaml didn't match and then the database didn't match.

        0 points
        • Brandon KellyBrandon Kelly, 7 months ago

          Hey Kyle, the process for getting project.yaml working properly is documented here.

          If you don’t follow that carefully, then there’s a good chance things aren’t going to work as expected. Luckily you can re-perform those steps at any time if you want to give it a fresh start.

          2 points
    • Mike Cassie, 7 months ago

      Can't speak too specifically to your experience Kyle but we've built a fair number of Craft sites over the last 3 or 4 years and never had issues keeping different environments in sync. Doing multi environment configs is pretty easy imo and we've always found it easy to manage and deploy from one repo. Of course, DB syncs are another matter but I'm not aware of any CMS that has a magic bullet for that problem.

      0 points
      • Kyle ConradKyle Conrad, 6 months ago

        Yeah, the DB syncs seemed to be the big failing on Craft for us. We're used to WordPress for a lot of client stuff, and a plugin like WP Sync DB really solves any DB issues for us (in terms of syncing, backing up, pushing, pulling) so it would be nice to see a one click solution like this built for Craft.

        0 points
    • Todd Padwick, 7 months ago

      We've been using Craft CMS for a while now and we used to use Architect plugin to manage migrating the CMS settings. However we've now started using into https://plugins.craftcms.com/migrationassistant which may be better considering it stores the migration data in a way which can be passed through a version control system like git.

      0 points
  • Mike BeersMike Beers, 7 months ago

    Thanks for sharing

    0 points
  • Luis Muñoz, 7 months ago

    Have you considered Processwire? https://processwire.com/

    0 points