Posted: Oct 14, 2010
in webbynode
By Carlos Taborda
Dallas Network Maintenance – Sun Oct 24 ’10
To ensure the most reliable service, we are planning a maintenance window which may temporarily affect your services. Improvements made in a controllable and pro-active fashion will significantly reduce the risk of unplanned incidents. We appreciate your patience as we make these pro-active changes.
Window Start Date & Time (24h CST/CDT): Sunday Oct 24, 2010 00:01
Window End Date & Time (24h CST/CDT): Sunday Oct 24, 2010 05:00
Our Network Engineers will be upgrading the firmware and rebooting the routers in one of our Rack environments to improve reliability and scalability.
Servers and services downstream from the routers may experience an interruption in network traffic during the code upgrade process. This service interruption should be less than 10 minutes.
Note: Only the Dallas, TX Location is Affected. Miami, FL customers are not affected by this maintenance.
Posted: Oct 11, 2010
in webbynode
By Felipe Coury
Ubuntu 10.10 available
Yesterday, 10/10/10, was a huge day for Ubuntu community. Ubuntu 10.10 was released!
We’re excited to say that the Maverick Meerkat is available now both in 32 and 64-bits. The support for this version is of 18 months and, for that reason, our ReadyStacks will continue to be based on Ubuntu 10.04 (LTS), which has 5 years of support.
Have fun!
Posted: Oct 8, 2010
in general
By Carlos Taborda
Screencast: our take on node.js deployment
We have been working for a while on our node.js rapid deployment engine and we just made it widely available. It’s still considered beta, because it’s only supported in servers running Rapp with nginx, but that will change soon. Update: We now support Apache as well and we’re moving out of beta real soon.
Our approach is to use git to transfer and manage the application files, along with a few more things. When you first push a node.js application to your server, we install and configure node.js and its dependencies, along with monit and npm (node.js package manager).
We then setup an upstart script, making sure your app is started when you reboot. This script also allows you to stop and start your application at will.
Another optional thing we do is configure nginx to proxy your requests. This way you can serve multiple node.js applications on port 80, while the real server is running on an alternate port like 8080, 8081, etc.
All this enables you to deploy, manage and delete all your node.js applications and its dependencies from the command line.
Below is a screencast that walks you through the process of deploying a simple node.js application. The documentation is available in our Webbynode Guides, here.
