HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
splice
indaba-naught
JavaScript2012–2012
splice / indaba-naught · Archived

indaba-naught

zero downtime deployment for your node.js server using native cluster api

2Distinct people
2Mentions
0Explicit recommenders
18GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

zero downtime deployment for your node.js server using native cluster api

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2012-09-25 14:50:13 UTC to 2012-09-25 15:17:01 UTC.

012012-09-25 14:00:00 UTC to 2012-09-25 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsSep 25, 14:002012-09-25 15:00:00 UTC to 2012-09-25 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 25, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 25, 14:002012-09-25 14:00:00 UTC2012-09-25 15:00:00 UTC110
Sep 25, 15:002012-09-25 15:00:00 UTC2012-09-25 16:00:00 UTC101

What Hacker News says

2 sources
I've never been interested in hot code-swapping; I find it's sufficient to just take that resource out of the pool, give it the new goodies and then boot it up again. I know the Erlang runtime can do this, but I've yet to find a good use case. As far as std{err,out} redirection, does Node.js have no Unicorn equivalent? Daemonization (and respawning) should be handled by a process supervisor, like supervisord/Upstart/Monit or whatever. They can do more than just 'this process died, restart it.' Also, most of this logging code didn't need to be written: https://github.com/indabamusic/naught/blob/master/src/log.co Just use logrotate.
In Naught.js: zero downtime deployment for node.js

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.