Download the PHP package onedesign/atomic-deploy without Composer
On this page you can find all versions of the php package onedesign/atomic-deploy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download onedesign/atomic-deploy
More information about onedesign/atomic-deploy
Files in onedesign/atomic-deploy
Package atomic-deploy
Short Description A script to easily handle atomic deployments in a Linux environment.
License Unlicense
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package atomic-deploy
Atomic Deployments
This project is based on the concepts presented in Buddy Atomic Deployments. It provides functionality to handle shared files and directories across deployments. While this was built for use with Buddy, it will work in any standard *nix environment.
Dependencies
- PHP 5.5+
- curl
File Structure
deploy-cache/- the location where all files are uploaded to the serverrevisions/- a directory containing all revisionscurrent- a symbolic link to the current revisionshared/- a directory containing files that should be shared across all deploys
Usage
Buddy + Craft 2 Example
Add the following in the "SSH Commands" section after your file upload action in your pipeline:
Options
--revision(required) accepts a string ID for this revision--deploy-diraccepts a base directory for deployments (default: current working directory)--deploy-cache-diraccepts a target cache directory (default:deploy-cachewithin deploy-dir)--revisions-to-keepnumber of old revisions to keep in addition to the current revision (default:20)--symlinksa JSON hash of symbolic links to be created in the revision directory (default:{})--helpprints help and usage instructions--ansiforces ANSI color output--no-ansidisables ANSI color output--quietsupresses unimportant messages--protectPassword protect sites at .oneis.us (default:true)
Symlinks
Symlinks are specified as {"target":"linkname"} and use the native ln utility to create links.
targetis relative to the--deploy-dirpathlinknameis relative to the revision path
For example, specifying this option:
will create symlinks the same way as:
Note: Files and directories that exist where the symlinks are being created will be overwritten. For example, using the above example, this is actually what is happening:
Password Protection
By default, the deployment will password protect any site that is served from a *.oneis.us domain name. This works by prepending the contents of the templates/htaccess-auth.txt file to any existing .htaccess file found in the current/web directory. If an .htaccess file does not exist within that directory, one will be generated using the templates/htaccess.txt file.
