HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ollym
nitrode
HISTORICAL RECORD2010–2010
ollym / nitrode · Not publicly available

nitrode

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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, 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 6-hour interval2 dated mentions

Observed mentions: 2010-08-16 15:49:29 UTC to 2010-08-22 12:03:47 UTC.

012010-08-16 12:00:00 UTC to 2010-08-16 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 16, 12:002010-08-16 18:00:00 UTC to 2010-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-17 00:00:00 UTC to 2010-08-17 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-17 06:00:00 UTC to 2010-08-17 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-17 12:00:00 UTC to 2010-08-17 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-17 18:00:00 UTC to 2010-08-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-18 00:00:00 UTC to 2010-08-18 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-18 06:00:00 UTC to 2010-08-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-18 12:00:00 UTC to 2010-08-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-18 18:00:00 UTC to 2010-08-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-19 00:00:00 UTC to 2010-08-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-19 06:00:00 UTC to 2010-08-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-19 12:00:00 UTC to 2010-08-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 19, 12:002010-08-19 18:00:00 UTC to 2010-08-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-20 00:00:00 UTC to 2010-08-20 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-20 06:00:00 UTC to 2010-08-20 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-20 12:00:00 UTC to 2010-08-20 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-20 18:00:00 UTC to 2010-08-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-21 00:00:00 UTC to 2010-08-21 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-21 06:00:00 UTC to 2010-08-21 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-21 12:00:00 UTC to 2010-08-21 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-21 18:00:00 UTC to 2010-08-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-22 00:00:00 UTC to 2010-08-22 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-22 06:00:00 UTC to 2010-08-22 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-22 12:00:00 UTC to 2010-08-22 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 22, 12: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
Aug 16, 12:002010-08-16 12:00:00 UTC2010-08-16 18:00:00 UTC110
Aug 16, 18:002010-08-16 18:00:00 UTC2010-08-17 00:00:00 UTC000
Aug 17, 00:002010-08-17 00:00:00 UTC2010-08-17 06:00:00 UTC000
Aug 17, 06:002010-08-17 06:00:00 UTC2010-08-17 12:00:00 UTC000
Aug 17, 12:002010-08-17 12:00:00 UTC2010-08-17 18:00:00 UTC000
Aug 17, 18:002010-08-17 18:00:00 UTC2010-08-18 00:00:00 UTC000
Aug 18, 00:002010-08-18 00:00:00 UTC2010-08-18 06:00:00 UTC000
Aug 18, 06:002010-08-18 06:00:00 UTC2010-08-18 12:00:00 UTC000
Aug 18, 12:002010-08-18 12:00:00 UTC2010-08-18 18:00:00 UTC000
Aug 18, 18:002010-08-18 18:00:00 UTC2010-08-19 00:00:00 UTC000
Aug 19, 00:002010-08-19 00:00:00 UTC2010-08-19 06:00:00 UTC000
Aug 19, 06:002010-08-19 06:00:00 UTC2010-08-19 12:00:00 UTC000
Aug 19, 12:002010-08-19 12:00:00 UTC2010-08-19 18:00:00 UTC000
Aug 19, 18:002010-08-19 18:00:00 UTC2010-08-20 00:00:00 UTC000
Aug 20, 00:002010-08-20 00:00:00 UTC2010-08-20 06:00:00 UTC000
Aug 20, 06:002010-08-20 06:00:00 UTC2010-08-20 12:00:00 UTC000
Aug 20, 12:002010-08-20 12:00:00 UTC2010-08-20 18:00:00 UTC000
Aug 20, 18:002010-08-20 18:00:00 UTC2010-08-21 00:00:00 UTC000
Aug 21, 00:002010-08-21 00:00:00 UTC2010-08-21 06:00:00 UTC000
Aug 21, 06:002010-08-21 06:00:00 UTC2010-08-21 12:00:00 UTC000
Aug 21, 12:002010-08-21 12:00:00 UTC2010-08-21 18:00:00 UTC000
Aug 21, 18:002010-08-21 18:00:00 UTC2010-08-22 00:00:00 UTC000
Aug 22, 00:002010-08-22 00:00:00 UTC2010-08-22 06:00:00 UTC000
Aug 22, 06:002010-08-22 06:00:00 UTC2010-08-22 12:00:00 UTC000
Aug 22, 12:002010-08-22 12:00:00 UTC2010-08-22 18:00:00 UTC101

What Hacker News says

2 sources
"Oliver Morgan Hi All, Welcome to my introduction to Nitrode. http://github.com/ollym/nitrode The Problem... Node.JS has no FastCGI module or alike that allows it to connect to an existing HTTP server like NGINX. The Solution... Nitrode is aimed to bridge that gap by providing a fast and versatile HTTP server, built on top of Node.JS. It aims to support many of the mainstream features NGINX does, but has the added advantage of being written in Javascript and exposing an API to allow existing applications to fully control it without leaving the current process. Great! How do i use it? You can find the repository here: http://github.com/ollym/nitrode I have included an example.js file, which will utilise all the current feature of Nitrode which are: 1. HTTP Basic Authentication 2. ETag and If-Modified-Since Support
Read the rest
3. Public directory / Static file support 4. SSL Support 5. Fully configurable 6. Vitual Host support 7. Redirect support 8. And much much more... Unlike Connect, it aims to be purely an HTTP server, and focusses entirely on that function. To run the example: 1. Clone the repository 2. cd to the repository directory 3. Run the command: "sudo node example.js" 4. Open up a browser, and type in: "localhost:80" 5. Authenticate yourself by using using username: 'admin', password: 'admin' 6. You should now see a page titled: "Welcome to Nitrode!" Make sure you also read through example.js to see what it's doing! So whats the catch? Nitrode is very young, i've only been working on it for the past week or so and so as such there are a number of things i still have to do: 1. Split index.js into smaller libraries 2. Add authentication digest support 3. Add SSL certificate authentication support 4. Write unit tests 5. Improve sys.pump performance 6. Write benchmarks 7. Write documentation If anyone is interested to help me out with this list, then please do! Regards, Olly"
In Introducing Nitrode - A dedicated HTTP server

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.