HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
foreversd
forever
JavaScript2012–2021
foreversd / forever

forever

A simple CLI tool for ensuring that a given script runs continuously (i.e. forever)

Command Line
Explore on GitHubRead Hacker News discussions
10Distinct people
10Mentions
0Explicit recommenders
13.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A simple CLI tool for ensuring that a given script runs continuously (i.e. forever)

GitHub

Where it is used

No documented product use was verified in the last source check.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 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 year10 dated mentions

Observed mentions: 2012-01-09 04:12:38 UTC to 2021-05-27 19:17:24 UTC.

0122012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2021

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
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC211
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC110
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC211

What Hacker News says

10 sources
gus_massa·May 27, 2021
There is no accountability. From the license (MIT) https://github.com/foreversd/forever/blob/master/LICENSE#L13... > THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, [...] You can fork it, if you wish. You can maintain a public fork and even accept patches from the community, or not accept patches, or only maintain a private fork and not share it with anyone. Also, it looks like it's in a semi-zombie state. They even encourage to use other programs: > A simple CLI tool for ensuring that a given script runs continuously (i.e. forever). Note that this project currently fully depends on the community for implementing fixes and new features. For new installations we encourage you to use pm2 or nodemon
In Open Source Accountability
NoInkling·Apr 20, 2017
Promises and now async/await go a long way to remedy the discrepancy between synchronous exceptions and asynchronous errors, by helping ensure that they both end up as promise rejections (as long as promises/async functions are your de facto async abstraction) while also being handleable with try/catch. The Koa framework (and in the future Express I believe) is designed around this concept, so middleware-level promise rejections can be handled in a single place, and by default simply produce an HTTP error response. It is a shame that it's going to take a while for the Node stdlib to catch up, however. Also I thought something like PM2 (https://github.com/Unitech/pm2) or Forever (https://github.com/foreverjs/forever) was pretty much standard for production Node apps?
In Hard-won lessons: Five years with Node.js
sippndipp·Jan 9, 2012Submission

Node PR, you can do better

Today I've read this article http://venturebeat.com/2012/01/07/building-consumer-apps-with-node/ and i find it a little disturbing. Node.js is a totally cool piece of technology and I'm loving it, but in this article node is embraced for the wrong reasons - let me be the advocatus diaboli: It’s JavaScript! Yes it's JavaScript, and as he said every developer knows a little JavaScript. But JavaScript has some bad parts http://www.youtube.com/watch?v=hQVTIJBZook and as a newbie JavaScript developer you can easily shoot yourself in the foot http://wtfjs.com/ Code re-use at every level: browser, back end & database We at 9elements dream of all tier code re-usages for several years https://github.com/janv/kupo but in the wild I actually don't see it. Also, do you really want your super secret business logic shared with the client? Code re-use a
Read the rest
in't easy, but someone has to do it. There are some great concepts like http://nowjs.com/ but I guess the status quo of JavaScript is not there yet. We need ES5+ in the browser to do the really good stuff. Strong, responsive and enthusiastic community Big part of the community is great! Some really brilliant minds out there! But there is also a part of not so skilled dudes who hated rails and now just hopping on the node bandwagon for the wrong reasons (and leaving behind a trail of unmaintained github repos w/o tests). Large productivity gains in HTML & CSS using Jade & Stylus Well, switching from HTML/CSS to HAML/SASS was a large productivity gain. Switching to Jade and Stylus was just felt "ok". The real performance boost at SASS dev came from Compass, which didn't existed for Stylus for a long time. Now there is Nib http://visionmedia.github.com/nib/ but it's still a pretty young project compared to Compass. Btw: For those who do a lot of Rails + Node.js development check out https://github.com/9elements/haml-coffee it's HAML married with CoffeeScript. Performance and scalability I buy the performance, kudos to the V8 team and @ryah. But scalability does not come from using a certain tech (unless it embraces scalability per default). Scalability comes from crafting a system that has no single point of failure (http://en.wikipedia.org/wiki/Single_Point_of_Failure). So please don't compare apples to pines. Wealth of hosting options: No.de, Joyent’s SmartMachine, Heroku, Nodejitsu True, I would just add homebrew hosting and deployment with capistrano and forever: https://github.com/nodejitsu/forever Make your developers famous Don't be foolish. Doing Open Source (right) is one of the hardest disciplines out there. Just releasing some written code into a new ecosystem does not automatically uplift you to the rockstar developer olymp. You have to maintain your code, deal with issues, deliver support etc... Doing Open Source work is very important. You take - you give - but more important you'll learn. But you don't need node for that there is plenty of room in this Internetz thingy, look at https://github.com/codejoust/session.js Developer happiness I know the feeling: Staying on the bleeding edge looking into the space where no man has gone before feels great. But be carefull, if things don't go well they can easily switch to developer tears. It almost took the node ecosystem a year to mimic typical "getting things done modules" like EveryAuth https://github.com/bnoguchi/everyauth which derives from https://github.com/intridea/omniauth/ in the rails world. OH: If you seeking for something like rails in the node.js world... then just use rails. Bottom Line When you read this you may get the feeling that I don't like node - I'm loving node http://node.9elements.com/ and it definitely has it's use cases: - if you do something in realtime - if you are developing an API - if you need high performance but for other use cases I wouldn't bet my life on it... yet. If you're interested in node, then go for it, play with it, never stop exploring - start small and grow with the ecosystem. One day it may replaces technology X with framework Y, but until then I would lower my expectations a little. So... enough ranting, let's engage the discussion - I hope you enjoyed this article: http://twitter.com/sippndipp
4 points · Open discussion

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.