For 99% of my sites I use the recommended Aegir/Barracuda/Octopus workflow and prefer it. However, certain clients require the full codebase in a third party version control repo. I would like to git clone their repo into a custom platform. I've gotten this to work, however at some point a script runs and changes permissions and adds files. I can ignore the files, but is there anyway to prevent the hosting system from modifying the platform. A git reset hard will allow me to work and commit upstream until the automatic script runs again. I totally understand if this isn't supported, but was just curious as I prefer to develop on my Octopus server instead of locally on a completely different setup.
Comments
Comment #1
omega8cc commentedThere is a switch to disable this: https://github.com/omega8cc/boa/blob/master/docs/cnf/barracuda.cnf#L33
But it is global, of course. At least at the moment. We could probably use platform level INI file to override system level default.
Comment #2
brentratliff commentedThanks for the quick reply, you guys think of just about everything.
Comment #3
omega8cc commentedOK, let's make it a feature request then!
Comment #4
brentratliff commentedI love it. It makes developing with an iPad or Surface practical for these one off sites, while still allowing the permissions fix script to run on the other platforms. Thanks!
Comment #5
omega8cc commentedDone! Just minutes before the release :)
https://github.com/omega8cc/boa/commit/40f3864fc96696ca6c3ecb63513903e22...
Comment #6
brentratliff commentedAwesome, I see a new blog post in my future about why I don't develop locally. Thanks!
Comment #9
brentratliff commentedAt what point are the ini files created for the platform? I have the files for all my other custom and system platforms but not for the one I just verified.
Comment #10
omega8cc commentedDaily.
Comment #11
omega8cc commentedWe could add INI templates on platform verify, probably. Adding active INI files makes sense only when there are sites to check and adjust INI settings as needed. Defaults set in the global.inc are probably enough initially.
Comment #12
brentratliff commentedOk, thanks. I have one site on that platform. I will check in the morning. My concern is that, when the script runs and the file is added, the permissions will also be changed and a git reset will then delete the ini file.
Comment #13
omega8cc commentedThe logic behind permissions fix and INI files is not connected, so nothing to worry about, hopefully, but I would recommend to add all INI files (both template and active) to .gitignore to avoid problems.