Rapid Application Deployment Engine

Updating

To update an already published app, you just have to follow the git workflow you’re probably already used to.

After your changes have been saved, you’ll have to commit them:

$ git add .
$ git commit -m "My lovely changeset"

And then, again:

$ webbynode push
Publishing myapp to Webbynode...
mkdir: created directory `myapp'
Counting objects: 86, done.
...

And that’s it. The same process will happen again.

However, we have a safety system in place. Let’s say you made a lot of changes but forgot to commit them using git. The Webbynode gem will give you a nice warning:

$ wn push
Cannot push because you have pending changes. Do a git commit or add
changes to .gitignore.

At this point you should choose what to do. Use git status to check pending changes:

$ git status
# On branch master
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working 
directory)
#
#       modified:   README
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#       temp/
no changes added to commit (use "git add" and/or "git commit -a")

In this case, we have two changes. I want to commit the README file, but not the temp/ folder. So I just add the folder to the .gitignore file:

$ echo "\ntemp/" >> .gitignore
$ git status
# On branch master
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working 
directory)
#
#       modified:   .gitignore
#       modified:   README
#
no changes added to commit (use "git add" and/or "git commit -a")

And now it looks good. So do a git commit and we’re ready to push again:

$ git commit -am "Fixed README and added temp to .gitignore" 
[master 7d63ae9] Fixed README and added temp to .gitignore
 2 files changed, 4 insertions(+), 1 deletions(-)
 
$ wn push
[imac] fcoury:~/Projects/sampleapp [git:master] → wn push
[Webbynode] Pushing sampleapp

(...)

----------------------------
  Webbynode git deployment 
----------------------------

Nginx+Passenger webserver detected...
Setting up DNS...

Deploying application sampleapp as sampleapp.webbyapp.com...

(...)

sampleapp deployed successfully.

Created http://sampleapp.webbyapp.com/

To git@67.23.79.32:sampleapp
   eeaa391..7d63ae9  master -> master

[Webbynode] Finished pushing sampleapp

This enforcement of a clean git repo before publishing can be overridden by the --dirty clause, like seen on push’s command help:

$ wn push --help
Sends pending changes on the current application to your Webby
Usage: webbynode push [options]
Options:
    --dirty             Allows pushing even if the current application
                        has git changes pending

Please note that if you force a dirty push, only changes made up to the last git commit will be pushed.

At this point you have finished the deployment lifecycle.

You can now:

check a suggested workflow for your deployments
check the troubleshooting information
learn how to delete a deployed app

And if you’re interested in more features, you can learn about:

the engines Rapp support
installing add-ons like MongoDB, or Beanstalkd
how to enable automated backups for your application code and database
interact with your Webby
and how to setup deployment hooks for your app

Comments