• Dragan BabicDragan Babic, almost 7 years ago

    We usually use a staging server that they can access. Code is shared via git, through GitLab.

    3 points
    • Sander VisserSander Visser, almost 7 years ago

      Hard thing I encountered is the usage with two databases. Every time you want to do local development, you need to export the database of the staging server and import it into your local server.

      If changes in both staging server and local server are made on the same time, you need to manually make the changes on on the the servers (usually staging server) again. To prevent these conflicts I try to communicate with the client when they are allowed to make changes in the CMS and tell them when they can not.

      If there's a better workaround for this I would be glad to hear it.

      0 points
  • Mark HegganMark Heggan, almost 7 years ago

    For meeting/presentation purposes in the past I have used Finch with success. I'd recommend a staging server though.

    0 points
  • Magnus SkareMagnus Skare, almost 7 years ago

    This really depends on your CMS.

    For WordPress, which is fairly common, I stage on a DigitalOcean server (unless they have their own) before pushing new features live. Code is shared through Bitbucket if we several people working on the project, and the database is like a game of tennis with WP Migrate DB Pro.

    0 points