Fast, flexible, clean deployment tool
DeployMaster is written in node.js, you should have latest stable version of node.
You can install DeployMaster with npm (as root)
npm install -g deploymaster
..and you can run it!
You can install DeployMaster with git, following commands:
git clone DeployMastercd DeployMaster && npm install
Usage: deploymaster <command> [options..]commandinit-host Create new hosting repostart-host Start server for host repoinit-development Initialize DeployMaster development repo on this directoryconfig Set repo configrm-repo Remove repo for this directoryrepo-info Show repository information for this directorytrack Track for allstatus Show track status for allpush Push new/modified files to host repoproduction Set production repopassword Set password for host repopublish Publish from connected host repo to deployment repoconnect Connect this development repo to main repository
deploymaster <command> --help
sudo deploymaster install-service
You can remove systemd service with;
sudo deploymaster remove-service
..or you can install/remove for specific port;
sudo deploymaster install-service --port 5053sudo deploymaster remove-service --port 5053
mkdir /path/to/project_hostcd /path/to/project_hostdeploymaster init-host
If you did created a systemd service with "install-service" option, you should enter host directory before set it.
It is like this;
"install-service" option creates host directories like
deploymaster password --set NEWPASSWORD
deploymaster config --key host.tls.use_tls --value true
deploymaster config --key host.tls.use_tls --value false
Set RSA Private Key file
deploymaster config --key host.tls.key_file --value "/path/to/private.key"
Set RSA Public Key (Cert) file
deploymaster config --key host.tls.cert_file --value "/path/to/public.crt"
If you don't use systemd service, you can start hosting for any directory.
deploymaster start-host --workdir /path/to/project_host
mkdir /path/to/project_devcd /path/to/project_devdeploymaster init-development
deploymaster config --help
deploymaster connect --host 127.0.0.1:5053
deploymaster config --key remote.tls.use_tls --value true
deploymaster config --key remote.tls.use_tls --value false
Create production directory
Add production repo to developmen repo
deploymaster production --set production --dir /path/to/production
Set owner and group for production files (for POSIX)
deploymaster production --set production --dir /path/to/production --owner username --group groupname
touch testecho "test file" >> testdeploymaster status --repo production
If you are using TLS, you'll see this
Certificate fingerprint: 69:5B:97:20:D3:7B:56:08:8C:80:36:FE:6A:41:6F:A5:36:08:4B:E2Do you trust it ?(y)es (n)o (p)ermanently:
If its ok, type "y" or "p" and press enter else type "n" and press enter
If you have new files;
deploymaster push --repo production
deploymaster publish --repo production
(New and modified files should be pushed.)
New and modified files come from pushed files to host directory.
If you have some changes and 100 new/modified files and pushed it.
When you did;
deploymaster push --repo productiondeploymaster publish --production testing
and after testing.. when you did;
deploymaster publish --production production
New/modified 100 files come from host directory.
Testing - Production approach.
.ignorelist.deploymaster file in
development repo and
It is like this
The main approach is two same ignorelists at development and production directories both.
But you might be want some specific ignored items for
In development or production sides, DeployMaster will track files in all directories and sub-directories if they are not included in ignorelist.
If you are using only ignorelist in development or production side, DeployMaster will look for all files in other side..
If you think you can contribute to DeployMaster, clone, code, commit and create a pull request!