Public and private data.
Store data in local filesystem or on Amazon S3.
User identity through Twitter.
The back-end of an open source blogging system, with MyWord Editor as the front-end.
Here's quick guide to setting up a NodeStorage server on Ubuntu, but probably works on many other Unix systems. It doesn't assume you have Node.js installed or a Git client. It shows you how to set up a connection with Twitter. It stores user data, both public and private, in the filesystem of the Ubuntu machine.
It's a good guide for installing on any Unix system, but has been tested on Ubuntu.
I wrote a backgrounder that explains the philosophy of NodeStorage, what it can be used for and where it's likely to go as it evolves.
A blog post provides another perspective.
Andrew Shell wrote a guide to setting up a new nodeStorage server.
Marco Fabbri wrote a howto for Heroku server setup.
It's fully open source, MIT License.
The back-end is NodeStorage.
You can also access it in api.nodestorage.io and include it from apps if you want.
Added a call to ping the "community server" when the RSS feed updates in addition to the rssCloud server. See lib/rss.js for details.
Sorry for the lack of update notes. What's been going on has been the development of nodeStorage as a server for 1999.io.
At this point the server should be as easy to install as it was previously, after some docs are written, and from here-out I plan to keeop the update notes current with the development work.
In the new chat functionality, when we return from a longpoll, we used to send back the entire chatlog. This is not very efficient, esp over a mobile connection. Now we only send back the new item that caused us to return. See postChatMessage for the change.
New routines support a basic chat capability.
Slack-compatible incoming and outgoing webhooks.
Can be configured to watch for a change to the mod date of storage.js, which causes it to quit (presumably to be relaunched by the OS or forever). Makes installing updates automatic.
By default, longpolls timeout after 60 seconds, previously it was 20 seconds.
The everyMinute script now runs at the top of the minute. Previously it was a function of when the app was launched. It also announces itself with the current time and the version of nodeStorage.
We can now store user data in the local file system. Previous versions could only store data in Amazon S3. The changes are documented in this post.
New functionality to support named outlines.
Fixed an error in the way whitelists are specified.
A new way to configure nodeStorage, with a config.json file.
The /getfilelist endpoint now returns an array of objects, one for each file, as before. The objects contain three values, path, whenLastChange and ctChars.
Previously we were returning the array that S3 returns to us. The file paths it returns are not easily used by a client.
There is a possibility of breakage if you had built on this endpoint, but given its previous state, it's hard to imagine anyone doing that. ;-)
New stats for longpolling, in serverStats.json. Example. Gives us a way to see how many people are watching resources managed by a nodeStorage server.
Added a readout of free memory as the second item in the server log.
In this screen shot the arrow points to the free memory readout.
Please post a note on the server-snacks mail list.