svn - How to decrease time for project env setup? -
We have lots of application logs (sometimes useful) in our project We have directories of components in this folder, such as: Problem: The folder of the new component arises over time - each of these folders is writable. So every developer takes time to chmod each folder in their local environment, it takes time to mislead those folders in production. How can this problem be solved? How can this process be automated (Apache ant task, SVN properties, script of application - to be responsible for the task)? Environment: Development Environment - Ubuntu, Windows; Production - FreeBSD I used to have some quick and dirty methods used in most companies: And any other command that you think you think is add. This approach Discipline is there. Keep you maintain discipline in the run time Instead of manually change your computer - you have the discipline to update the tmp > Are) I code> folder .
setup_permissions.sh which updates all local environment content, can include permissions, or Whatever you need to run svn update , which update the file, and also setup_permissions.sh . setup_permissions.sh . for contents of contents_permissions.sh , something like this might happen:
# / bin / sh tmp = / tmp mkdir $ tmp / api mkdir $ tmp / email2sms mkdir $ tmp / Anusucit_sending mkdir $ tmp / billing chmod 777-R $ TMP / API $ TMP / email 2 SMS $ TMP / scheduled $ Sdianding $ TMP / billing < / Pre>
(Oh, and do not use the chmod 777 ... The key is a terrible idea. Just see it as an example.) setup_permissions.sh update to its local environment must trust your programmers. Anyone who updates the production system also goes for that too. setup_permissions with any changes made to the directory structure should be, and his permission change required should be, and leaving him (and he changes also for all other developers who directory structure.)
Comments
Post a Comment