datastation VS Dokku

There was a technique that existed already where you could use `go test -cover` and the `-o` flag to produce a binary from `go test` rather than actually running tests. So you could build a binary that had coverage enabled. Then when you ran

Here's an example: https://github.com/multiprocessio/datastation/blob/main/runn....

I can't remember where I found this technique but it's been around for a while.

This new option is the same thing but a way to `go build` with `-cover` instead of `go test -cover -o $out`? Do I have that right?

If my employer doesn't consider paying for dbt cloud, I will use u/eatonphil 's datastation, run the queries on a dev database then put them in dbt.

I build a somewhat similar app, DataStation [0], that is in JavaScript and Go. It supports scripting in Python, Julia, R, JavaScript, Ruby, etc.

The server version of it exists and I run it myself but that process is not documented yet. (Most people use it as a desktop app today.)

[0] https://github.com/multiprocessio/datastation

My biggest issue with Pyodide is the long wait times. I haven't figured out a way around a ~5 second load time where the entire UI hangs every single time you load the page.

My app (similar to Simon's, a lite mode of a data IDE): https://app.datastation.multiprocess.io.

My code: https://github.com/multiprocessio/datastation/blob/main/shar....

I use Go heavily cross-platform developing DataStation [0] and dsq [1]. I am not an expert. And I don't have proof for it but on some rudimentary benchmarks the Linux-specific file idioms in the Go standard library definitely don't seem to translate well to even macOS let alone Windows. For example some good streaming techniques for reading large files on Linux that work really well there seemed to be pretty bad on macOS.

I think Amos has presented more proof than I can on the topic of just how Linux-influenced Go is. And I think it is fine for the majority of Go users because the majority users of Go are building server apps or Linux CLIs.

Amos has spent some time building cross-platform desktop systems with Go for itch.io and I think I'm seeing some of the same things they are in that scenario.

I think this is a reasonable article. If Amos gets flame-y at any point I think it's worth ignoring because there does seem to be something up with Go in cross-platform applications.

I like Go a lot and for most things I'd keep using it still. Just sharing some observations.

[0] https://github.com/multiprocessio/datastation

[1] https://github.com/multiprocessio/dsq

I keep a page of good first projects for two big projects I work on. The only expectation is that you know Go. I've had a couple of people who've never contributed to OSS come in and get some meaningful features merged.

I've got some good first projects if you're interested in OSS data tools and have some Go experience.

Check out: https://github.com/multiprocessio/datastation/blob/main/GOOD...

Some example projects: DataStation (desktop GUI for querying every kind of database, scripting and graphing the results) and dsq (a CLI companion for running SQL queries on many kinds of files), and go-json (a library for fast JSON encoding of arrays of large objects).

I'm building a desktop-first (SaaS-eventual) data IDE for developers [0]. Making a living? Not yet.

It being desktop-first makes it as easy to try out in a corporate environment as Sublime. The data never leaves your machine. Desktop-first is a big deal in devtools for this reason.

[0] https://github.com/multiprocessio/datastation

I run all my projects on Dokku. It’s a sweet spot for me between a barebones VPS with Docker Compose and something a lot more complicated like k8s. Dokku comes with a bunch of solid plugins for databases that handle backups and such. Zero downtime deploys, TLS cert management, reverse proxies, all out of the box. It’s simple enough to understand in a weekend and has been quietly maintained for many years. The only downside is it’s meant mostly for single server deployments, but I’ve never needed another server so far.

https://dokku.com/

Yeah there are a bunch of selfhostable things:

Caprover (https://caprover.com/)

Dokku (https://github.com/dokku/dokku)

But people still choose Netlify and Vercel for ease of use I think.

Maybe we need something that's just Netlify. The closest I've seen to the "right" UX is Ness:

https://ness.sh

The modern iteration of these tools has taken the developer experience learnings from the Platform as a Service (PaaS) category, and will bring them to your own VM, giving you your own personal PaaS. Example of this include Dokku, Coolify, Caprover, Cloud66 and many more!

Based on the fact that your ideal is to have a similar experience to heroku than managing your own server setting up reverse proxies take a look at these options:

1) https://dokku.com - lets you turn your light sail instance basically into heroku

2) https://render.com

3) https://fly.io

4) If you have aws credits this is their heroku equivalent: https://aws.amazon.com/elasticbeanstalk

above is not what I do but would be the options I would pursue if I understand your preference and requirement correctly.

All in all, I really recommend trying out Dokku if you are a developer interested in hosting your own projects. It makes it super easy to get everything you need to get up and running without having to worry about the specifics. And the price is impossible to beat!

The installation instructions are on the frontpage of our site. Thats basically all you need to do to install Dokku. As far as using it, we have a simplified tutorial here.

Dokku is a lightweight and open-source PaaS platform that simplifies application deployment by leveraging Docker. With Dokku, developers can easily push their applications using Git, allowing Dokku to build and run them in isolated containers. Its CLI-only approach and plugin architecture make it highly extensible. Dokku's modular plugins enable features like database integration, Let's Encrypt SSL certificates, and automated Slack notifications, giving developers flexibility and control over their PaaS environment.

Also https://dokku.com/