@h1alexbel
First of all we should use up.sh. This script starts a new version of the app on "green" port, so we can test this version using prefix /api-test/..., which was configured in default-*.conf file.
Then after testing we can replace our stable "blue" version with the "green" one using swap.sh. This script will switch prefixes and stop the "blue" container.

@hizmailovich I got the idea why do we need those scripts. But my original claim was "where" those scripts are used, I don't see them in .rultor.yml to be executed on deployment

@h1alexbel release section, here

@hizmailovich here you described how to release a new version to the server, should we pass only one script to execute blue-green deployment?

Also, let's move "How to Contribute" section to the bottom of the README

@hizmailovich let's make sure release happens in just one command (tests and swap should be executed internally). Since rultor release... makes a GitHub release with immutable tag we can't release the same version twice. Besides that it would be much more convenient to do that seamless deployment in just one command. WDYT?

@rultor merge

@rultor merge

@h1alexbel Thanks for your request; @hizmailovich please confirm this.

@rultor merge

@rultor merge

@hizmailovich Can't merge this pull requests, because the file .rultor.yml was modified. This is a security threat. Make a separate pull request with the modification of this particular file and ask project architect to merge it manually.