Download the PHP package aoepeople/magento-deployscripts without Composer
On this page you can find all versions of the php package aoepeople/magento-deployscripts. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 magento-deployscripts
Magento Deployment Scripts
Author: Fabrizio Branca
This is a collection of scripts used to build/package, deploy and install Magento projects.
Import note: Never use the master branch in your build jobs. Instead clone a specific tag:
Since these scripts might change significantly and your deployment process might fail otherwise.
Overview
- build.sh
- deploy.sh
- install.sh
Usage
Add the magento-deployment scripts to your project using Composer. Checkout composer.json example file below.
Introduction
build vs. provisioning vs. deployment vs. installation
Checkout http://www.slideshare.net/aoepeople/rock-solid-magento/91 (and the next slides after that)
TODO: add more information here
build.sh
Generated files
- projectName.tar.gz
- projectName.extra.tar.gz
- MD5SUMS
Base package vs extra package
Checkout http://www.slideshare.net/aoepeople/rock-solid-magento/55 (and the next slides after that)
Example Configuration/tar_excludes.txt content
Expected project files/directories
- composer.json
- tools/composer.phar (This should be part of your project repo. Obviously this can't be pulled in via Composer. Chicken and egg, problem... :)
- tools/modman (This is part of https://github.com/AOEpeople/magento-deployscripts which is being pulled in via composer)
- htdocs/index.php
- .modman directory: The modules located here can be directly committed to the main project repository (e.g. if they're project specific) or they can be pulled in via Composer)
- .modman/ProjectName_Base: There's no exclipict check for this base module to be present, but this is a recommendation. Add the basic project setup (local.xml, htaccess,...) to this base module.
- .modman/.basedir
- Configuration/tar_excludes.txt (this file controls what goes in the base package and what goes in the extra package. See below)
Additionally install.sh expects/checks these files:
- tools/systemstorage_import.sh (This is part of https://github.com/AOEpeople/magento-deployscripts which is being pulled in via composer)
- tools/apply (This is part of https://github.com/AOEpeople/EnvSettingsTool which is being pulled in via composer)
- tools/n98-magerun.phar (This is part of https://github.com/AOEpeople/magento-deployscripts which is being pulled in via composer)
- Configuration/settings.csv (This is being used by EnvSettingsTool to apply all environment specific settings during the installation process)
- Configuration/mastersystem.txt (Defines which system is the master system. E.g. "production". This is required to determine if the systemstorage backup needs to be imported during the installation process.)
- Configuration/project.txt (project name. E.g. "acme")
These files and folders can easily be constructud by using following composer.json as a basis for your project
Auto-generated meta files
Following files will be stored inside the base package
- build.txt
- htdocs/version.txt (will be accessible from the web)
