HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
multiprocessio
datastation
TypeScript2021–2023
multiprocessio / datastation

datastation

App to easily query, script, and visualize data from every database, file, and API.

Developer ToolsData & DatabasesSystems & InfrastructureWeb DevelopmentObservability
Explore on GitHubRead Hacker News discussions
2Distinct people
44Mentions
0Explicit recommenders
3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

App to easily query, script, and visualize data from every database, file, and 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

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

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:58 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 month44 dated mentions

Observed mentions: 2021-06-12 11:55:28 UTC to 2023-03-08 21:42:53 UTC.

02462021-06-01 00:00:00 UTC to 2021-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 20212021-07-01 00:00:00 UTC to 2021-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-08-01 00:00:00 UTC to 2021-09-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-09-01 00:00:00 UTC to 2021-10-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-10-01 00:00:00 UTC to 2021-11-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-11-01 00:00:00 UTC to 2021-12-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2021-12-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2022-01-01 00:00:00 UTC to 2022-02-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-02-01 00:00:00 UTC to 2022-03-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-03-01 00:00:00 UTC to 2022-04-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2022-04-01 00:00:00 UTC to 2022-05-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 commentsApr 20222022-05-01 00:00:00 UTC to 2022-06-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2022-06-01 00:00:00 UTC to 2022-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-07-01 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 2023

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
Jun 20212021-06-01 00:00:00 UTC2021-07-01 00:00:00 UTC101
Jul 20212021-07-01 00:00:00 UTC2021-08-01 00:00:00 UTC000
Aug 20212021-08-01 00:00:00 UTC2021-09-01 00:00:00 UTC303
Sep 20212021-09-01 00:00:00 UTC2021-10-01 00:00:00 UTC303
Oct 20212021-10-01 00:00:00 UTC2021-11-01 00:00:00 UTC202
Nov 20212021-11-01 00:00:00 UTC2021-12-01 00:00:00 UTC404
Dec 20212021-12-01 00:00:00 UTC2022-01-01 00:00:00 UTC615
Jan 20222022-01-01 00:00:00 UTC2022-02-01 00:00:00 UTC404
Feb 20222022-02-01 00:00:00 UTC2022-03-01 00:00:00 UTC303
Mar 20222022-03-01 00:00:00 UTC2022-04-01 00:00:00 UTC707
Apr 20222022-04-01 00:00:00 UTC2022-05-01 00:00:00 UTC505
May 20222022-05-01 00:00:00 UTC2022-06-01 00:00:00 UTC413
Jun 20222022-06-01 00:00:00 UTC2022-07-01 00:00:00 UTC101
Jul 20222022-07-01 00:00:00 UTC2022-08-01 00:00:00 UTC000
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC000
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC000
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC000
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC000
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC000
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC000
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC101

What Hacker News says

2 sources
eatonphil·Oct 12, 2021
I'm building an open-core data IDE that runs as a desktop application or server. Since it's open source, all tests run on Github Actions for free. This includes basic e2e testing using Selenium on Windows, macOS, and Linux (e.g. [0]); and unit/integration tests. If it were a private repo I'd still shell out for Github Actions or Circle CI most likely. I'd also consider buying a chunky-enough minipc for ~$500 and an older mac mini and set up runners on them. For the moment private runners isn't a problem. But soon I'll need to start integration-testing proprietary code paths like querying Oracle or MS SQL Server. In that case I probably need to set up a dedicated box with all the right licenses so I can run CI jobs on it. [0] https://github.com/multiprocessio/datastation/blob/master/.g...
In Ask HN: Solo-preneurs, how do you DevOps to save time?
eatonphil·Oct 5, 2021
Contrary to some folks here I've had a pretty good experience learning Julia while adding support for it as an scripting language in an open-source data IDE I'm building [0]. It makes a lot more sense as a language to me than R (which is also a supported scripting language), but I'm slowly coming around to R too. I do agree that it is pretty slow to start, most other scripting languages I support finish much quicker on simple scripts. But I imagine the reason you use Julia over Ruby/Node.js is the libraries not just the startup time. But I really like that it has a builtin package manager unlike almost any other language (except R) which makes it very easy to install missing dependencies in a try-catch block. (Useful in my situation since its an IDE that runs on your computer using your existing python/ruby/julia install and only depends
Read the rest
on a single JSON library.) It's also neat that all hosted Github Actions images come with Julia built in so it's pretty easy to be working with it in automated environments as well. [0] https://github.com/multiprocessio/datastation
In New features coming in Julia 1.7

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.