Skip to content
Permalink
Browse files

check deploy key on CI side

  • Loading branch information...
captn3m0 committed Aug 22, 2015
1 parent 656224e commit cd728146e435e03f5ef85ac9ec3241f9f470c34c
Showing with 7 additions and 8 deletions.
  1. +7 −8 config/deploy.rb
@@ -24,21 +24,20 @@

# This task is the environment that is loaded for most commands, such as
# `mina deploy` or `mina rake`.
# Make sure that the deploy key is available
if ENV['CI'] === 'true'
`openssl aes-256-cbc -K $encrypted_82a37ece568a_key -iv $encrypted_82a37ece568a_iv -in deploy-rsa -out lightsaber-deploy -d`
`chmod 600 lightsaber-deploy`
end

task :environment do
# If you're using rbenv, use this to load the rbenv environment.
# Be sure to commit your .ruby-version or .rbenv-version to your repository.
invoke :'rvm:use[default]'

# Make sure that the ssh key is available
if ENV['CI'] === 'true'
queue "openssl aes-256-cbc -K $encrypted_82a37ece568a_key -iv $encrypted_82a37ece568a_iv -in deploy-rsa -out lightsaber-deploy -d"
queue "chmod 600 lightsaber-deploy"
end
end

# Put any custom mkdir's in here for when `mina setup` is ran.
# For Rails apps, we'll make some of the shared paths that are shared between
# all releases.
desc "Starts the current release"
task :setup => :environment do
queue "cd ~/lightsaber/current"
queue "bundle exec thin -C config.yml start"

0 comments on commit cd72814

Please sign in to comment.
You can’t perform that action at this time.