Fork me on GitHub

Migrating from dev to prod  Bottom

  • Hi, Zikula Community. I am considering Zikula as an alternative to a CMS I am currently running. I will frequently need to work in a development environment and push my changes out to a production instance of Zikula. Is there anyone already doing this and if so, what is your experience with this? Is there a best way? Also, any tips/tricks/lessons learned would be great. Thank you!
  • I think that is more a question of management and tools than which CMS is used. for example, if you use an IDE than can automatically copy files out to a server then you could do that in any project.

    Zikula is well constructed, though, to allow customizations without affecting the core product. there are many ways this can be done - module creation, theme creation, template/stylesheet override, even class overrides. In version 1.3 there will be even more ways (using events) to customize without ever touching the core.

    welcome to Zikula!
  • Thank you for the reply. I wasn't clear on what type of "work" I would be doing. I wouldn't be making code changes...strictly content updates and maybe some templating changes, etc., or installing a new module, for example. Ideally, I'd want to do this offline but then push those changes to the live site. I was thinking of just doing a database export/import but didn't know if that was the best way or had any pitfalls. Wanted to see what others do if anyone has a similar process.
  • I work on content on the live site and just don't push it to published until I'm ready.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • HalbrookTech

    I work on content on the live site and just don't push it to published until I'm ready.

    +1

    --
    Harness Technology
  • Let me expand a little on what HalbrookTech said. Zikula has a News module where you can write very robust articles on whatever content that you want. When you are ready to publish, you just change the status from pending to published and it then becomes visible.

    For my work, I do the content directly on line. However, if I am writing a module or doing theme work, that I test offline and push it online by replacing the relevant files on my production server. Actually, having a staging area would be a very cool thing for my Book module.
  • The easiest way to run a test- and a production install is to simply create a folder /test (or a test.mydomain.com subdomain) und put a duplicate there. Also duplicate your database, simply use a different prefix (e.g. "test") for the tables of the test install.

    That way you can work directly on the test site, and ensure it will look and work exactly the same later on on your production site, as the unlying hard- and software is identical. It additionally enables you to let other people review and test at the test site, without breaking the production site. Specially when planning bigger upgrades, this is the way to go, anyway.

    All other workflows lack the "identical hard and software" issue, because almost none of our users will have a commercial hosting server at home/his office.

    Greetings,
    Chris



    Edited by slam on Jul 10, 2010 - 09:10 AM.

    --
    an operating system must operate
    development is life
    my repo
  • +1

    pheski

    --
    Peace
    ______________________________________
    The commonest cause of problems is solutions.
  • 0 users

This list is based on users active over the last 60 minutes.