I've started with Craft developing all locally. The struggle for me when working locally was synchronizing the database and the backend assets with coworkers on the same project.

In the last project we tried a different approach, where we have the db, the assets and the CP on a server. So all devs involved in the project had the same backend.

What we still had locally were our templates and frontend stuff. The db.php pointed to the remote db. The basepath pointed to our local root so it would load the local templates.

I'm actually pretty happy with that solution the only problem I haven't figured out yet is using image transforms. Since I'm using locale templates (and a locale craft installation for templating ), the transforms tries to generate the images locally which doesn't seem to work. Maybe my configuration is off since I don't have to much experience with transforms and the configuration with this setup can get a little confusing as well :)

How does your setup look while working in a team?

And any suggestions for the my problem with transform?

4 Answers 4


That's the setup we use here. It's ok, but local development runs slowly because the database is off-site - we'll be moving to an internal database server in the new year because of that.

Image transforms we just deal with by manually syncing the folders every now and then. I believe Andrew Welch has a script to help manage that - I've not tried it https://github.com/nystudio107/craft-scripts

But I wish there was a way to tell Craft, in dev mode, that a missing image file is not a "stop everything" error.

  • Thanks for sharing your setup! I agree it's very slow but for me it still outweighs working locally. Internal db-server sounds like a good solution. The craft-scripts seem really worth checking out. I've not given enough love to backups yet and it's seems the craft-scripts could help me change that. ( backup_assets.sh, backup_db.sh) Commented Nov 15, 2017 at 14:30
  • We work kind of the same here. Only thing we do different I guess is even though we work "local" all our projects are on our own parts of our server. Also use the same DB and sync via gitlab on a daily basis. Commented Nov 15, 2017 at 15:33
  • Using Amazon S3 and – ideally – image transforming via services like Imgix makes local development tons more fun. Plugins like Imager and Image Optimize support the latter out of the box. Commented Nov 16, 2017 at 0:30

Matt Wilcox alluded to it in his original comment, but something like Craft-Scripts will really help out with this workflow. You can read more here: Database & Asset Syncing Between Environments in Craft CMS


I'd recommend you take a look at the excellent existing threads on this:

  1. Git Workflow and Multi Environment - how to approach
  2. What's the best practice for handling data migration and organization across development environments?

as well as the official documentation on Multi-Environment Configs

Source: Correct way to set up development and production environments for Craft?


Maybe this is a stupid idea (correct me if so) but why don't you use a shared folder through Dropbox, Spideroak or Tresorit to synch the assets?

  • I've found a solution I'm happy with :) With imager it's possible to transform remote images and since I upload backend assets on a development server, are me and my co-workers able to transform the images in the local templates. Commented Jan 23, 2018 at 10:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.