Every two weeks we spread the word of Node.js and the cool and incredible things it can do. We do that by profiling creative, interesting and fun uses of Node.js in various products and projects. We call it “In the Loop.”
First released in September 2012, turtle.io gives programmers the ability to store files created with Node.js within a folder and access those files through the Internet. The files are compiled and results are sent to the user via Turtle. And if you have a hostname? You are fully supported and the content can be accessed quite simply. Turtle is compatible with Windows, Linux, Mac OS, BSD and Solaris platforms. You’ll need Node.js 0.8 or higher.
We talked about turtle.io with Jason Mulligan. Our chat included his background, getting started with node.js, the process of creation, and the imbalance between ideas and time.
Jason, before we dig into turtle.io, can you tell us a little bit about yourself?
Turtle.io is a web server for Node.js. Did you start this project wanting to build a web server, or specifically a server for Node.js?
Jason Mulligan: I started with the intention of creating a web server for node.js that didn’t require the end user to write more code to serve static web sites.
What made you decide to create this using Node.js? What’s your background with Node.js?
Jason Mulligan: I’ve used Apache since the mid 90s, and a few months ago I decided I wanted to remove it from the stack. I finally had a reason to make something in Node.js! I’ve been aware of Node.js since ’09, but I was focused on common Server side languages at my job (ASP/.Net/PHP), so I had little motivation to experiment with it in my free time; abaaso was eating that up.
Where there any particular challenges using Node.js, for this site or in general?
Jason: I’ve found Node.js to be intuitive and easy to use, just like StrongOps (formerly NodeFly)! Getting started with Node.js was very easy thanks to the amazing community on Twitter, IRC & the web.
Can you tell us a bit more about the experiences with the community?
Jason Mulligan: I can’t really speak much on the community beyond what it generates; I don’t really have time for active participation, but I do read whatever comes across my Twitter searches. There’s an interesting range of experiences being documented in blogs & video.
Have you gotten any feedback from people using turtle.io for sites? Any fun examples of a site using it?
Jason Mulligan: I’ve had some good feedback for turtle.io. No one’s sent me a links to their sites running on it yet, but like any proud parent, I look forward to that day. I use it for a few products at FileTrek, so it’s also landing in the enterprise space very soon. It’s also serving its own web site
Anything else cooking for turtle.io, or for avoidwork in the Node.js realm?
Jason Mulligan: Yes! I’ve got more ideas than time! I want to make customizing a site easier, by implementing something like an “.htaccess” file. I think turtle.io will be evolving for a while. I want it to become the alternative to Apache when Node.js is present, because it’s resource footprint is absolutely tiny in comparison.
Thanks for your time, Jason – and good luck with those projects!
- What’s in the upcoming Node v0.12 release? Six new features, plus new and breaking APIs.
- Ready to develop APIs in Node.js and get them connected to your data? Check out the Node.js LoopBack framework. We’ve made it easy to get started either locally or on your favorite cloud, with a simple npm install.
- Need for Node? Learn more about both the private and open options StrongLoop offers.