packages - Version control and complicated applications that install files everywhere -


I have to work on a web application. Version controls have directories like such structures: 

 < Code> AppName / Connection Appname / www Epam / etc Apeman / Keys Epam / Lib ...

However, the application to work, currently needs to be in the system directory: 

  /etc/httpd/conf.d/ var / www / html / etc / appname / etc / pki / tls / / Usr / lib / perl5 / ... ...  < / Pre> 
 There is an RPM to take the VCED code and prepare that package. Confirms that puts code into the production location (ie / var / Www / html and others). There are no established instructions, I should use RPM and make improvements (ideally I know). 
 
 In this way, how everyone edits the app, maintains version control features (git diff etc ...), and can be quick to make changes in the application? The app is written in Perl, so there is no compilation. 
 
 The way I thought, it is: 
 
     
  •  VCED DIR (and work on code) 
    •  
  •  Work on code at the last position ( So code editing will work immediately, but you have to manually move the code back to VC'ed dirs) 
    •  
  •  Write a file system to see changes in the VCID DIR, and replace the changed files Establishes at its last place (maybe something like this?) 
    •  
  •  Some other obvious methodology i Mid is that no one can tell me: -) 
    •  
 
 Everyone handles how such cases?

I am working on code on some type of test server, but in the right places the code with. Version control is necessary so that they can pick up the necessary files from their respective location, but you are not deployed at the "last" location until you are ready (so basically "install" phase, as you put it).

Since changing things more sensible can not be an option for you directly, can you symink the VC directory from the system directory?


Comments

Post a Comment