29 8 / 2012
Special Thanks to Nodesters!
When I set out to start the Nodester open source PaaS project 1.5 years ago, I had no intention of building and running a 24x7 Node.JS PaaS. I simply wanted to learn Node.JS and the nuances of hosting Node.JS apps in a public and private cloud environment.
With the help of the open source community (specifically @DavGlass and @DanBUK), I learned about Linux chroot sandbox securing of apps. I would also like to thank the following developers who have contributing to the Nodester project over the years: @_Alejandromg @Eschoff @Marcosvm @Abraham @MichealBenedict, @Crp_underground @AdamKumpf @Krwindham @Akavlie @eldios @Tenzer @Eocampospy @Fgnass @JP_pinilla Yawnt @WeAreFractal MintPlant Ckknight @Arvidhahldev @stephanepericat and @Kev_nz. As of late, @_AlejandroMG has been my wingman on this rocketship ride and has proven himself to be an amazing Node.JS developer, thoughtleader, and most patient support engineer. I would work with any of you again in a heartbeat!
I would also like to give a shoutout to @Tropo @VoxeoLabs and @IrisCouch for their hosting sponsorships which have allowed us to offer our hosting services to the Node.JS community for free since day one!
I am proud to say that Nodester was the first 100% open source Node.JS PaaS solution available for developers and it’s still one of the few Node.JS platforms that supports native WebSockets! The Nodester community is passionate about open source public, private, and hybrid cloud PaaS services and has proven that open source projects can become viable businesses.
Upon accepting a new career opportunity with Bechtel, it became clear to me that I could no longer support the growing demands of our susccessful open source project and free hosting service. I looked at the various leading PaaS providers out there and it became clear that the only one with our vision and mission was AppFog. They, too, were very excited about taking over the Nodester project and ultimately adding our realtime websocket technology into their CloudFoundry platform.
This partnership between AppFog and Nodester will give our Node.JS developers the very best public and private PaaS hosting solution as Node.JS continues to grow and extend into the enterprise. I am very proud of our accomplishments and have made many new friends throughout this endeavor. With that, I have one last thing to say…..Hack the planet! \m/
Links to the press coverage at the time of this post:
Permalink 5 notes
30 6 / 2012
Nodester CLI Reaches 1.0 Status!
We are happy to announce that the Nodester CLI (command line interface) has officially reached 1.0 status! At the time of this article, we are actually on v1.0.2 which now supports Node.JS version 0.8.1 by default!
Here is a list of the updates:
- nodester app delete -> nodester app destroy (Because delete is reserved word in js) Almost every delete action is now destroy.
- nodester app list: Alias to nodester apps (or viceverza)
- nodester authors: Show the contributors for this tool.
- Shorthands: e.g nodester app l maps to nodester app logs.
- Better help with headers and stuff.
- JSHint code lint (All code is valid js)
- Use of “use strict”
- Partial node-0.8.1
- Travis support
- Bump to 1.0.0.
- New “Hello World” app
- More useful nodester app init command. Now it let you to choose between hello world or autoudpate remote (default to nodester)
- Also no more “You need to restart your app” after npm installs
- New Api nodester client with this command you are now able to interact with your personal instance easily. Running just nodester client set <endpoint> <brand> will setup your instance. Really useful.
The new CLI also walks you through deploying your app from scratch or as an existing application. See below:
$ nodester app create 081
nodester info creating app: 081 server.js
nodester info successfully created app 081 to will run on port 19144 from server.js
nodester info run nodester app init 081 to setup this app.
nodester info ok!
$ nodester app init 081
nodester info What do you want to do:
(1) Setup a new app from scratch?
(2) You just want to setup your existent app?
note: if you choose 2 be sure that you are into your app’s dir
nodester info initializing git repo for 081 into folder 081
nodester warn this will take a second or two
nodester info cloning your new app in 081
nodester info clone complete
nodester info writing the default configuration
nodester info processing the initial commit
nodester info Nodester!
remote: _ _
remote: _ __ ___ __| | ___ ___| |_ ___ _ __
remote: | ‘_ \ / _ \ / _ |/ _ \ __| __/ _ \ ‘__|
remote: | | | | (_) | (_| | __\__ \ |_ __/ |
remote: |_| |_|\___/ \__,_|\___|___/\__\___|_|
remote: Open Source Node.js Hosting Platform
remote: Syncing repo with chroot
remote: From /node/git/topher/10991-985dc656de547235fe586e3debb0ce6b
remote: * [new branch] master -> origin/master
remote: Attempting to restart your app: 10991-985dc656de547235fe586e3debb0ce6b
remote: App restarted..
remote: \m/ Nodester out \m/
* [new branch] master -> master
nodester info 081 started.
nodester info Some helpful app commands:
nodester app info
nodester app logs
nodester app stop|start|restart
nodester info ok!
Permalink 2 notes
24 5 / 2011
Tropo Sponsors Nodester!
We are proud to announce today that the super smart cloud communications geeks at Tropo have offered to sponsor our open source Node.JS hosting project!
What does this mean for Nodester? It means that our open source project just got even better! Tropo is now paying for the hosting of our free Node.JS hosting services running on http://nodester.com and has offered to help us hire a few Node.JS developers to extend the platform!
If you or anyone you know is interested in getting paid to develop on our open source Node.JS hosting platform, please send job inquires to firstname.lastname@example.org.
Permalink 6 notes