Closed robertmassaioli closed 11 years ago
If you'd like to submit a PR for this I would like it, but this is a general deployment configuration step to do more than it really is an issue for this project.
Hmm, it is an issue of the project that it is more difficult than it needs to be in order to manage it's deployment successfully. But I guess this is a matter of opinion.
I'm not against the idea, but I'm not going to be spending time on it as it's a deployment configuration.
If you could please submit a pull request making the desired change I will look into it then.
Okay sweet, that is no problem, I was not arguing for you (or anybody) to do it right now but rather that it was important. It is not my highest priority right now either but when I get to it on my backlog then you will get a pull request.
I made the mistake of forgetting to add ckeditor_assets to the list of shared directories in Capistrano between deployments and, as a result, some of our images went missing after I performed a deployment thanks to the fact that they did not exist in the new directory.
My proposed solution is that the ckeditor_assets directory be created under public/spree, or maybe even public/spree/editor so that we can clearly place it in a known location and people that already save the 'spree' directory into the shared directory with capistrano do not forget to include this one too.
Solving this issue in a nice way should avoid deployment pain for many users.