Version control of uploaded images to file system -
After reading
I think the file system is the correct place to store images. But I would like to know how do you upload backup / version control in your different environments (Dev / Stage / Prod) and for network load balancing?
These problems are very easy to make a database example to create backups from production environments and to restore DB in the development environment.
For example, what do you think about the use of GIT to handle the version control of uploaded files?
Production Environment:
- An image is uploaded to a shared folder on the web server.
- Meta data is stored in the database
- Image is automatically
Developer at work:
- Checks the source code.
- Runs a script to restore the database.
- Runs a script to get the latest pictures.
I think the above solution is very easy for the developer, the picture version will be under control and the environment can be separated from each other.
For us, version control is not as important as distribution. Meta data is added by the web administrator and the images are deleted on the admin server. Rundink scripts push those clusters that work on prod images. For Dev / test, we rsync back to the dev server from the Prod master server.
rsync is great for load balancing and distribution if you are in GIT sub for admin / master server, then you have a very good solution.
If you are OK with backup, then keep file history at backup time (as with each modification in contrast to version control), some of its customizations can help:.
Comments
Post a Comment