🐳 docker image and deploy script #84
Conversation
| @@ -1,6 +1,4 @@ | |||
| # For more options, see http://capistranorb.com/documentation/getting-started/configuration/# | |||
| # config valid only for current version of Capistrano | |||
| lock '3.3.5' | |||
There was a problem hiding this comment.
was this getting in the way? Seems like removing it opens up a new risk of incompatibility between the Capistrano version and our config
There was a problem hiding this comment.
This was added with e75758b
Upgrades to ruby3.2, capistrano 3.18
Seems to be working fine with the upgraded capistrano version, so I'm fine continuing with the latest for now, until it becomes a problem, when we can lock it.
| click.echo(f"Branch: { branch }") | ||
| cmd = f"""docker run -it -v {realpath('')}:/root/ {DOCKER_IMAGE}""" | ||
|
|
||
| sub_run(cmd, stdin=PIPE, stdout=PIPE, stderr=STDOUT) |
There was a problem hiding this comment.
@mrharpo how does context and branch inform the docker run command?
There was a problem hiding this comment.
I forgot about this file. This was a secondary attempt after the ./deploy script, which is what I've been using to deploy things.
Not sure why I would prefer this over the env var approach. We can probably delete this file, since the regular bash version is sufficient.
Docker
Added dockerfile, based on
ruby:3.1bundle InstallCMD:bundle exec cap aws deploy./deployDocker based shortcut script
Usage
./deploy COMMAND [ARGS]Requires local vars to be exported in the current session, e.g:
export BRANCH=42-fixes-all-bugsAlso requires the
SSH_KEYto be available somewhere within$PWD, so it can be mounted into the container.Commands
buildBuild the docker image
deployRun the deployer
ENV_VARSto docker for:BRANCHAPP_NAMEREPO_URLSSH_HOSTSSH_KEYENV_VARScan be overwritten on the command line:BRANCH=my-fancy-branch ./deploy deployOther usage
Enter the deployer into a bash session:
./deploy deploy bash