deploy: Add concept of a MANIFEST to the deployment process #2052

Merged
merged 5 commits into from Jun 22, 2015

Projects

None yet

2 participants

@greezybacon
Member

This allows files which are edited on the fly during deployment to be tracked so that they are not unnecessarily deployed again in the next deployment run. It also allows for more creative deployment strategies using something like git ls-files -s

Additionally, the .MANIFEST file could be signed and verified with DNS, which, when combined with the unpack script could provide a chain of custody for the source code.

@greezybacon greezybacon added the review label May 27, 2015
greezybacon added some commits Dec 5, 2014
@greezybacon greezybacon deploy: Add concept of a MANIFEST to the deployment process
This allows files which are edited on the fly during deployment to be
tracked so that they are not unnecessarily deployed again in the next
deployment run. It also allows for more creative deployment strategies using
something like `git ls-files -s`
c12f06a
@greezybacon greezybacon deploy: Use `git ls-files` for deployment source
As an option, this will allow preventing deployment of files not tracked
with git. It's also about twice as fast as the PHP version.
8edd74c
@greezybacon greezybacon cli: Allow multiple short options like `-vt` 09753f6
@greezybacon
Member

I've updated this and it works on the first deployment now

@greezybacon
Member

@digitext I think you'll get more help if you post in #1419

@greezybacon greezybacon deploy: Put the MANIFEST in the include/ folder
This allows the MANIFEST to be hidden from HTTP requests since the entire
include/ folder is already denied for Apache.
9365243
@protich protich merged commit e91cff1 into osTicket:develop Jun 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment