tomo deploy allow user to deploy with just one command. Tomo will do both setup and deploy processes. Tomo deploy will allow Heroku alike features to be install onto your own server
tomo setup command it will:
# run "rails:db_create"
tomo deploy command it will:
of course we can secify our own task in these processes by adding plugin to it. eg:
def check_files remote.chdir(paths.release) do remote.run('yarn', 'install', '--check-files') end end
then we can add
run 'yarn:check_files' to our process.
This is the part that I love about tomo deploy.
git:create_release source: tomo-deploy.com
Fetches the latest commits from git_branch (or git_ref) and creates a release by copying the contents of that branch of repository into a new release inside the releases_path. Releases are numbered based on the timestamp of when the deploy takes place.
git:create_release is intended for use as a deploy task.
TOP 3 TOMO COMMANDS
There are tons of goodness when it comes to tomo commands. We browse all commands through
tomo tasks command.
- To see running log on remote deploy server, we can use this command:
To access remote server data-via-activerecord we can always use our handy
rails consolebut to do it remotely with tomo, we can use
Do not use
set env_varsto update your
PATH. We cannot use like
export "PATH=$PATH:/our/bin"in env_vars, as it will break our path. I have break it once and I suggest other people to do it on to the remote(deploy server) shell it self.
To allow message encryptor to work properly, we need to make sure:
a. master.key content from our local machine are the same RAILS_MASTER_KEY that we enter onto the remote server via
b. we add and commit+push our local
thank you for reading.
Top comments (0)