HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Taymindis
nginx-link-function
C2018–2018
Taymindis / nginx-link-function

nginx-link-function

It is a NGINX module that provides dynamic linking to your application in server context and call the function of your application in location directive

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

What to know before exploring

What it is

It is a NGINX module that provides dynamic linking to your application in server context and call the function of your application in location directive

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, 12:54:37 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: 2018-10-14 05:16:02 UTC to 2018-10-15 04:17:19 UTC.

012018-10-14 05:00:00 UTC to 2018-10-14 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 14, 05:002018-10-14 06:00:00 UTC to 2018-10-14 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 07:00:00 UTC to 2018-10-14 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 08:00:00 UTC to 2018-10-14 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 09:00:00 UTC to 2018-10-14 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 10:00:00 UTC to 2018-10-14 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 11:00:00 UTC to 2018-10-14 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 12:00:00 UTC to 2018-10-14 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 13:00:00 UTC to 2018-10-14 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 14:00:00 UTC to 2018-10-14 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 15:00:00 UTC to 2018-10-14 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 16:00:00 UTC to 2018-10-14 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 14, 16:002018-10-14 17:00:00 UTC to 2018-10-14 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 18:00:00 UTC to 2018-10-14 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 19:00:00 UTC to 2018-10-14 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 20:00:00 UTC to 2018-10-14 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 21:00:00 UTC to 2018-10-14 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 22:00:00 UTC to 2018-10-14 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-14 23:00:00 UTC to 2018-10-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-15 00:00:00 UTC to 2018-10-15 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-15 01:00:00 UTC to 2018-10-15 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-15 02:00:00 UTC to 2018-10-15 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-15 03:00:00 UTC to 2018-10-15 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-15 04:00:00 UTC to 2018-10-15 05:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 15, 04: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
Oct 14, 05:002018-10-14 05:00:00 UTC2018-10-14 06:00:00 UTC101
Oct 14, 06:002018-10-14 06:00:00 UTC2018-10-14 07:00:00 UTC000
Oct 14, 07:002018-10-14 07:00:00 UTC2018-10-14 08:00:00 UTC000
Oct 14, 08:002018-10-14 08:00:00 UTC2018-10-14 09:00:00 UTC000
Oct 14, 09:002018-10-14 09:00:00 UTC2018-10-14 10:00:00 UTC000
Oct 14, 10:002018-10-14 10:00:00 UTC2018-10-14 11:00:00 UTC000
Oct 14, 11:002018-10-14 11:00:00 UTC2018-10-14 12:00:00 UTC000
Oct 14, 12:002018-10-14 12:00:00 UTC2018-10-14 13:00:00 UTC000
Oct 14, 13:002018-10-14 13:00:00 UTC2018-10-14 14:00:00 UTC000
Oct 14, 14:002018-10-14 14:00:00 UTC2018-10-14 15:00:00 UTC000
Oct 14, 15:002018-10-14 15:00:00 UTC2018-10-14 16:00:00 UTC000
Oct 14, 16:002018-10-14 16:00:00 UTC2018-10-14 17:00:00 UTC000
Oct 14, 17:002018-10-14 17:00:00 UTC2018-10-14 18:00:00 UTC000
Oct 14, 18:002018-10-14 18:00:00 UTC2018-10-14 19:00:00 UTC000
Oct 14, 19:002018-10-14 19:00:00 UTC2018-10-14 20:00:00 UTC000
Oct 14, 20:002018-10-14 20:00:00 UTC2018-10-14 21:00:00 UTC000
Oct 14, 21:002018-10-14 21:00:00 UTC2018-10-14 22:00:00 UTC000
Oct 14, 22:002018-10-14 22:00:00 UTC2018-10-14 23:00:00 UTC000
Oct 14, 23:002018-10-14 23:00:00 UTC2018-10-15 00:00:00 UTC000
Oct 15, 00:002018-10-15 00:00:00 UTC2018-10-15 01:00:00 UTC000
Oct 15, 01:002018-10-15 01:00:00 UTC2018-10-15 02:00:00 UTC000
Oct 15, 02:002018-10-15 02:00:00 UTC2018-10-15 03:00:00 UTC000
Oct 15, 03:002018-10-15 03:00:00 UTC2018-10-15 04:00:00 UTC000
Oct 15, 04:002018-10-15 04:00:00 UTC2018-10-15 05:00:00 UTC101

What Hacker News says

2 sources
It works with nginx threads using aio. It's in one of the issues there if you look deep enough. https://github.com/Taymindis/nginx-c-function/issues/2 I haven't figured out how to get rid of the drop in performance though. Lets say you just return a 200 from the nginx location like so: location /a { return 200 "{\"result\": \"Hello World!\"}"; } vs location / { ngx_http_c_func_call 'getRoute'; } The requests per second will drop by about 40% of what you'd otherwise get. This is with 4 workers, the worker_rlimit_nofile set to 262144 etc, etc. I'm not sure what I'm doing wrong. It is pretty nice given that you also get all of the other options like upstream handling and reverse proxying and pretty damned good speed. The flexibility this adds is beyond awesome. But if I only need max speed for an api th
Read the rest
at only talks to postgres, redis, and a few other things, I'd just use H2o.
In Nginx C function

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.