Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are implementing Git at our company and coming from SVN, I have a few architectural questions.
For our designers, how can they manage project assets? Documents, PDFs, PSDs, graphics? In SVN we could just make a folder called ‘assets’, detached from the code.
How can you do the same for a db snapshot?
I want to keep code seperate from digital assets without creating more overhead or making it complicated for our designers to version control their work.
As I understand your question, previously the assets were part of your subversion repository and designers only checked out the
assetsdirectory because they did not need the source code. The exactly same approach does not work in git because git does not support partial checkouts, so designers would have to bother checking out the source code as well, and you would like to avoid this. Right?The best approximation of your old scheme would be to put the assets in a separate git repository and include this separate repository as a module in your source repository. Developers would have everything in one place, and designers could check out the assets only.