{"id":249348,"date":"2016-12-29T06:37:08","date_gmt":"2016-12-29T13:37:08","guid":{"rendered":"http:\/\/css-tricks.com\/?p=249348"},"modified":"2016-12-29T06:37:08","modified_gmt":"2016-12-29T13:37:08","slug":"develop-locally-use-images-production","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/develop-locally-use-images-production\/","title":{"rendered":"Develop Locally, Use Images from Production"},"content":{"rendered":"

Working on your website locally means having the files that make your website tick right there on your computer. It’s common those files live in a version control repository. You work on them, and push them up to the repo when you are ready. Other people work too, and you pull their changes back down. <\/p>\n

What might not<\/em> be in that repo, are images files from the CMS. WordPress is a classic example of this. When you upload an image in WordPress, it does a whole song and dance. It gets uploaded to the `uploads` folder, multiple versions are created, even the database is updated and attachment meta data happens. What doesn’t<\/em> happen is that a version control commit happens with all those files.<\/p>\n

<\/p>\n

There are ways to make sure you have those files. You could write a script to pull them down. You could manually FTP it once in a while. In WordPress land, there are plugins that help, like WP DB Migrate Pro<\/a>, which not only does the database but can move images as well. <\/p>\n

But you might not even want<\/em> to deal with images. Perhaps:<\/p>\n