Rapid Application Deployment Engine
Publishing
When publishing your application, Rapp will transfer all your application code to your Webby, set up the database, the DNS entries (if applicable), configure the Web Server (Apache2 or nginx) and setup additional features (like backup or add-ons) that we’ll see later.
Let’s deploy our application with the push command:
$ webbynode push [Webbynode] Pushing sampleapp mkdir: created directory `sampleapp' Counting objects: 88, done. Delta compression using up to 2 threads. Compressing objects: 100% (73/73), done. Writing objects: 100% (88/88), 80.80 KiB, done. Total 88 (delta 11), reused 0 (delta 0) Checked out master branch ---------------------------- Webbynode git deployment ---------------------------- Nginx+Passenger webserver detected... Setting up DNS... Deploying application sampleapp as sampleapp.webbyapp.com... Configuring Rails application... => Configuring nginx vHost... => Configuring database... => Configuring database.yml... => Installing missing gems... => Migrating database... /var/rails/sampleapp/.git Restarting nginx sampleapp deployed successfully. Created http://sampleapp.webbyapp.com/ To git@67.23.79.32:sampleapp * [new branch] master -> master [Webbynode] Finished pushing sampleapp
As you can see, this is the typical output you’ll get when deploying a Rails application. If you’re using a different engine, such as Django, Rack, PHP or even Rails 3, your mileage may vary. You can learn more about engines in the Supported Engine sections.
Now that your app is available at the indicated address – http://sample.webbyapp.com – you can use the open command to open it in your default Web Browser:
$ wn open
Basic Topics
Advanced Topics