README

These documentation is the guide to painlessly setup an automated deploy on the Hypernode platform. The repository contains:

Configuration objects
Deploy configuration templates
CI configuration templates
Documentation

Whats inside?

Deployer configuration hosts / tasks
Hypernode server setup
Email / New Relic notification
Cloudflare flush

Configuration

Composer require hypernode/deploy-configuration --dev package. Only needed when you want to have autocomplete in your deploy.php file.
Copy a deploy.php template inside the root of your project as deploy.php. You can find the template in templates/deploy.php. As you can see a $configuration variable is assigned an instance of a Configuration class. This configuration object contains the whole deploy configuration and can be altered to your needs using getters/setters. Change configuration matching you use case, and refer to the documentation for other build in configurations and tasks.
Setup your CI server
1. GitLab CI templates/.gitlab-ci.yml.
2. Bitbucket templates/bitbucket-pipelines.yml.
3. Github Actions templates/github-actions.yml.
For Magento 2 your first build will fail due to missing configuration. Login to the server and depending on your project file edit the app/etc/env.php or app/etc/local.xml. You will find these files in ~/apps/<domain>/shared/.

Build steps

1. Build

Builds the application to prepare to run in a production environment.

You can define commands which needs to be executed during the build stage as follows:

$configuration->addBuildTask('deploy:vendors');

This command will execute a composer install in your project folder install all project dependencies.

All possible commands can be found in the Hypernode\DeployConfiguration\Command\Build namespace. Refer to the API docs for usage and options.

This repository contains a few application templates which specifies the common tasks and their order to get the application build correctly. See application templates for more information.

2. Deploy

Deploys the application which was build in the build stage to a given set of hosts.

First you need to define your environments / infrastructure.

$stageAcceptance = $configuration->addStage('acceptance', 'acceptance.mydomain.com');
$stageAcceptance->addServer('appname.hypernode.io');

To set extra SSH options (https://www.ssh.com/academy/ssh/config) for your server you can also provide these. For example:

$stage->addServer('appname.hypernode.io', [], [], ['LogLevel' => 'verbose']);

You can define tasks which needs to be executed during the deploy stage as follows:

use function Deployer\{run, task};

...

task('magento:cache:flush', static function () {
    run('{{bin/php}} {{release_or_current_path}}/bin/magento cache:flush');
});

$configuration->addDeployTask('magento:cache:flush');

All possible commands can be found in the Hypernode\DeployConfiguration\Command\Deploy namespace. Refer to the API docs for usage and options.

3. Provision Platform services / configurations

Optionally you can have some services and application configurations setup automatically from your git repository to the Hypernode platform

For example you could maintain your cron configuration in your GIT repository and have it automatically deployed to particular servers.

$configuration->addPlatformConfiguration(
    (new PlatformConfiguration\CronConfiguration())->setStage('production')
);

Or setup a varnish instance

$configuration->addPlatformService(new \Hypernode\DeployConfiguration\PlatformService\VarnishService());

For all possible tasks and configuration please refer to the API docs.

4. AfterDeploy tasks

After deploy tasks are triggered after a successful deployment. For example notifications are available.

Usage:

$configuration->addAfterDeployTask(new \Hypernode\DeployConfiguration\AfterDeployTask\SlackWebhook());

5. Brancher servers for acceptance/integration testing

Usage:

$stage = $configuration->addStage('test', 'test.domain.com');
$stage->addBrancherServer('appname');

Application template

We provide a few application template which define the common set of tasks to be executed for a specific application type. You could use those so you don't have to specify each task manually.

Available templates:

Example usage: $configuration = new ApplicationTemplate\Magento2(['nl_NL']);

Environment variables

Some specific environment variables are required to allow the deploy image access to the git repository or to be able to send out notifications.

Required

SSH_PRIVATE_KEY Unencrypted SSH key. The key needs to have access to the remote server(s). May be base64 encoded like this:
```
cat ~/.ssh/deploy_key | base64
```

Optional

DEPLOY_COMPOSER_AUTH Composer auth.json contents. This file is required if you require access to specific Composer repositories like Magento's, 3rd party vendors, or even your own private Composer package repository. If this environment variable does not exist, no auth.json will be written, so it is optional. The auth.json must be base64 encoded like this:
```
cat auth.json | base64
```
HYPERNODE_API_TOKEN The Hypernode API token to be used for the project. Request one at support@hypernode.com.

Testing

To test your build & deploy, you can run hypernode-deploy locally.

First make sure you have all the required env variables setup using.

export SSH_PRIVATE_KEY=***
export DEPLOY_COMPOSER_AUTH=***
export HYPERNODE_API_TOKEN=***
.... etc

Then start your build / deployment run command from root of the project.

repeat -e for all env vars that are present during build

docker run -it \
    -e SSH_PRIVATE_KEY -e DEPLOY_COMPOSER_AUTH -e HYPERNODE_API_TOKEN \
    -v `pwd`:/build hypernode/deploy \
    hypernode-deploy build -vvv
docker run -it \
    -e SSH_PRIVATE_KEY -e DEPLOY_COMPOSER_AUTH -e HYPERNODE_API_TOKEN \
    -v `pwd`:/build hypernode/deploy \
    hypernode-deploy deploy acceptance -vvv

hypernode / deploy-configuration

Maintainers

Details