It acts as a user shell and knows only two commands test and deploy. For example, a command
ssh deployuser@mega-server test myproject tag.0.0.123
will download and deploy to the test environment release.zip with tag.0.0.123
- Basic auth
- It gets first asset from assets array. (some logic should be added here, may be filename in config or something, e.g: 'release-file-name':'release.zip')
- per project exclusion list in config
- per project after installation tasks (e.g.: forever restart, etc...)
- check tag. Now, if tag is not found, script will fail with ugly html output.
- There is only organization based multiproject support.
deploy-cfg.json should be in same directory
{
"credentials" : "someuser:somepassword",
"github_org" : "github_organization_name",
"projects" : "project1 project2 site-v2",
"projects_home" : "/tmp/home"
}- Create deploy user by running something like this (should work on most linux systems)
adduser --home /home/deploy --shell /home/someone/deploy.sh deploy- Put
deploy.shanddeploy-cfg.jsoninto the/home/deployand run:
chmod +x /home/deploy/deploy.sh
- create projects home and ensure that it's writable for deploy user. e.g.:
mkdir /opt/wwwhome
chown deploy /opt/wwwhome
- Edit
deploy-cfg.json
Command test
ssh deploy@your_server test project_name tag_name
It will do following stuff:
- get list of GitHub releases from
api.github.com/repos/{repo_name}/releases
{repo_name}could begithub_org/projector justprojectifgithub_orgfield is empty in config - get first url from asset with
tag_name - download and unpack it to
{project_name}/rc - rsync it to
PROJECTS_HOME/{project_name}-test/
Command deploy
- sync
PROJECTS_HOME/{project_name}-test/withPROJECTS_HOME/{project_name}-prod/
Just add a name to projects list. And upload release.zip to the github.