HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
fmeringdal
nettu-scheduler
Rust2021–2021
fmeringdal / nettu-scheduler

nettu-scheduler

A self-hosted calendar and scheduler server.

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

What to know before exploring

What it is

A self-hosted calendar and scheduler server.

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, 5:04:57 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 hour3 dated mentions

Observed mentions: 2021-03-29 12:47:54 UTC to 2021-03-30 07:27:32 UTC.

012021-03-29 12:00:00 UTC to 2021-03-29 13:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 29, 12:002021-03-29 13:00:00 UTC to 2021-03-29 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-29 14:00:00 UTC to 2021-03-29 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-03-29 15:00:00 UTC to 2021-03-29 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-29 16:00:00 UTC to 2021-03-29 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-29 17:00:00 UTC to 2021-03-29 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-29 18:00:00 UTC to 2021-03-29 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-29 19:00:00 UTC to 2021-03-29 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-29 20:00:00 UTC to 2021-03-29 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-29 21:00:00 UTC to 2021-03-29 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 29, 21:002021-03-29 22:00:00 UTC to 2021-03-29 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-29 23:00:00 UTC to 2021-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-30 00:00:00 UTC to 2021-03-30 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-30 01:00:00 UTC to 2021-03-30 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-30 02:00:00 UTC to 2021-03-30 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-30 03:00:00 UTC to 2021-03-30 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-30 04:00:00 UTC to 2021-03-30 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-30 05:00:00 UTC to 2021-03-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-30 06:00:00 UTC to 2021-03-30 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-30 07:00:00 UTC to 2021-03-30 08:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 30, 07: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
Mar 29, 12:002021-03-29 12:00:00 UTC2021-03-29 13:00:00 UTC110
Mar 29, 13:002021-03-29 13:00:00 UTC2021-03-29 14:00:00 UTC000
Mar 29, 14:002021-03-29 14:00:00 UTC2021-03-29 15:00:00 UTC101
Mar 29, 15:002021-03-29 15:00:00 UTC2021-03-29 16:00:00 UTC000
Mar 29, 16:002021-03-29 16:00:00 UTC2021-03-29 17:00:00 UTC000
Mar 29, 17:002021-03-29 17:00:00 UTC2021-03-29 18:00:00 UTC000
Mar 29, 18:002021-03-29 18:00:00 UTC2021-03-29 19:00:00 UTC000
Mar 29, 19:002021-03-29 19:00:00 UTC2021-03-29 20:00:00 UTC000
Mar 29, 20:002021-03-29 20:00:00 UTC2021-03-29 21:00:00 UTC000
Mar 29, 21:002021-03-29 21:00:00 UTC2021-03-29 22:00:00 UTC000
Mar 29, 22:002021-03-29 22:00:00 UTC2021-03-29 23:00:00 UTC000
Mar 29, 23:002021-03-29 23:00:00 UTC2021-03-30 00:00:00 UTC000
Mar 30, 00:002021-03-30 00:00:00 UTC2021-03-30 01:00:00 UTC000
Mar 30, 01:002021-03-30 01:00:00 UTC2021-03-30 02:00:00 UTC000
Mar 30, 02:002021-03-30 02:00:00 UTC2021-03-30 03:00:00 UTC000
Mar 30, 03:002021-03-30 03:00:00 UTC2021-03-30 04:00:00 UTC000
Mar 30, 04:002021-03-30 04:00:00 UTC2021-03-30 05:00:00 UTC000
Mar 30, 05:002021-03-30 05:00:00 UTC2021-03-30 06:00:00 UTC000
Mar 30, 06:002021-03-30 06:00:00 UTC2021-03-30 07:00:00 UTC000
Mar 30, 07:002021-03-30 07:00:00 UTC2021-03-30 08:00:00 UTC101

What Hacker News says

3 sources
May I ask you why you would want to store booking slots? I think the right approach is to recalculate available booking slots everytime (via the nettu-scheduler api) a customer asks for it. And then also store the confirmed booking timespan as a calendar event in nettu-scheduler so that the instructor will not be bookable again during that time. You can have a look at this example: https://github.com/fmeringdal/nettu-scheduler/blob/master/ex...
In Show HN: Nettu Scheduler – A self-hosted calendar and scheduler server
From my experience it is a common mistake to do overlap comparisons of intervals this way. https://github.com/fmeringdal/nettu-scheduler/blob/df737e128... IMO start time should be treated as inclusive, and end time as exclusive. E.g. an event from 1pm-2pm does not overlap with an event starting at 2pm because it's end-time is defined as exclusive. Therefore you need to replace one of you greater/lower-than's with a normal greater/lower comparison operator.
In Show HN: Nettu Scheduler – A self-hosted calendar and scheduler 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.