search

tracehubpm / pmo

Project registry, facilities and its home
MIT License
4 stars 0 forks source link

Deploy and release scripts #79

Open dukris opened 8 months ago

dukris commented 8 months ago

@h1alexbel take a look, please

Closes #6 Closes #81

PR-Codex overview

The focus of this PR is to update deployment and release configurations for the project.

Detailed summary

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

dukris commented 8 months ago

@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.

h1alexbel commented 8 months ago

@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

dukris commented 8 months ago

@h1alexbel release section, here

h1alexbel commented 8 months ago

@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

h1alexbel commented 8 months ago

@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?

h1alexbel commented 8 months ago

@rultor merge

rultor commented 8 months ago

@rultor merge

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

dukris commented 6 months ago

@rultor merge

rultor commented 6 months ago

@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.