datasette.io VS org-roam-server

Opened an issue exploring alternatives here: https://github.com/simonw/datasette.io/issues/109

I decided to just drop "any size" but keep "any shape".

Here's an example from one of my projects: https://github.com/simonw/datasette.io/blob/main/.github/workflows/deploy.yml

I've come around to almost the opposite approach.

I pull all of the data I can get my hands on (from Twitter, GitHub, Swarm, Apple Health, Pocket, Apple Photos and more) into SQLite database tables that match the schema of the system that they are imported from.

For my own personal Dogsheep (https://simonwillison.net/2020/Nov/14/personal-data-warehous...) that's 119 tables right now.

Then I use SQL queries against those tables to extract and combine data in ways that are useful to me.

If the schema of the systems I am importing from changes, I can update my queries to compensate for the change.

This protects me from having to solve for a standard schema up front - I take whatever those systems give me. But it lets me combine and search across all of the data from disparate systems essentially at runtime.

I even have a search engine for this, which is populated by SQL queries against the different source tables. You can see an example of how that works at https://github.com/simonw/datasette.io/blob/main/templates/d... - which powers the search interface at https://datasette.io/-/beta

I've been exploring this technique more over the past year and I really like it - https://datasette.io (code at https://github.com/simonw/datasette.io ) is a more recent and much more complicated example.

Extracting links from markdown and using them to populate some additional columns or tables at build time would be pretty straight forward.

I run SQLite in serverless environments (Cloud Run, Vercel, Heroku) for dozens of projects... but the trick is that they all treat the database as a read-only asset.

If I want to deploy updated data, I build a brand new image and deploy the application bundled with the data. I tend to run the deploys for these (including the database build) in GitHub Actions workflows.

This works really well, but only for applications that don't need to apply constant updates more than a few times an hour! If you have a constant stream of updates I still think you're better off using a hosted database like Heroku PostgreSQL or Google Cloud SQL.

One example of a site I deploy like that is https://datasette.io/ - it's built and deployed by this GitHub Actions workflow here: https://github.com/simonw/datasette.io/blob/main/.github/wor...

Hi! I upgraded to org-roam v2 about two months ago after using v1 for a few months before that. I felt org-roam-server quite useful primarily for visualizing which ideas link to which others. However, I haven't felt the same intuitiveness with org-roam-ui (the server counterpart for v2). And the graph always seems too cluttered and rather difficult to use for purposes of idea-link visualization. Has anyone else felt this? Is it just a matter of getting used to?

We and u/kirillrogovoy and u/smallstepman on Github have started to work on a new version of org-roam-server which is compatible with org-roam-v2. This is just a teaser and we will be releasing a v1 soonishTM, keep a look out for [this GitHub issue](https://github.com/org-roam/org-roam-server/issues/161) for some status updates!

https://github.com/org-roam/org-roam-server can show such thing.

All my entries live inside a single file. I was able to set up org roam server successfully, but my roam server only shows me a single link (the file itself). (3 in the screenshot because I was trying something)

Yes, see https://github.com/org-roam/org-roam-server