cloudquery VS foam

Check out CloudQuery - https://github.com/cloudquery/cloudquery for an easy cloud asset inventory.

There both do something like what you're looking for.... https://github.com/cloudquery/cloudquery https://github.com/openraven/magpie

Unified API is a holly grail but as many said quite difficult to abstract every use case in a scalable way that won't break. At CloudQuery (https://github.com/cloudquery/cloudquery) we focus solely on the ELT use-case(Founder/Maintainer here).

Congrats!! How does it compare to the ELT space and the modern data stack where you have ingestion/storage/visualization layers decoupled?

Asking as the founder of CloudQuery (https://github.com/cloudquery/cloudquery), Saw Datasette quite a few times around data exploration but curious to hear about the most popular use-cases of Datasette!

Congrats!! We also focus on performance at CloudQuery (https://github.com/cloudquery/cloudquery) by using Golang, gRPC and still trying to be abstract enough to support different databases :)

In any case good luck!

CloudQuery for ETL

Another ELT framework that's an alternative to Airbyte

Another alternate ELT

Check out CloudQuery, we have PostgreSQL source connectors and S3 destination that supports parquet (Disclaimer: Maintainer and founder here)

Hello! Im Yevgeny, Founder & maintainer at CloudQuery . We've built CloudQuery as an open source high performance ELT framework so you should get pretty good results syncing all your cloud assets from high number of accounts (we have users syncing more than 10K Azure subscription and thousands of AWS accounts concurrently).

Source: (1) A personal knowledge management and sharing system for VSCode - Foam. https://foambubble.github.io/foam/. (2) A personal knowledge management and sharing system for VSCode. https://github.com/foambubble/foam. (3) Loam - Visual Studio Marketplace. https://marketplace.visualstudio.com/items?itemName=ciceroisback.loam.

You should have a look at Foam: https://github.com/foambubble/foam

I started using Foam[0] a few years ago, but the more I used it, the more I dropped all the tedious bits, and it became nothing more than a big, evolving markdown repo.

When I switched from vscode (back) to vim, it has worked as well or better than it did before. I follow my own rules. I like the Zettelkasten idea of one idea per card, but if I put more related things in the same .md file, that's OK. I didn't like the flat directory structure, and so I have dirs organized by category. My /bar directory is inside my /cooking directory, and for whatever reason, that makes sense to me. Ripgrep doesn't care, and I always find what I'm looking for.

This markdown hierarchy, that still lives in a repo called "foam", has become indispensable to me.

[0] https://github.com/foambubble/foam

Probably use foam https://github.com/foambubble/foam

So I switched to FOAM and it's just clean & organized markdown files in a git repo. Self host a code server instance and I can reference it without installing something to the work machine.

Recently I started to configure my digital garden. Foam is a good option, Hugo Doks, No Style Please, Git-Wiki, Researcher, Thinkspace, and other themes are good for zetteltasken pages.

I use foam and VSCode and regularly am wow'd with what I am having it do next. I feel I am still just getting started too.

I've wondered about using obsidian with foam as a web editing fallback.

Since the data store is markdown and can be synced with Git, you can already work with an Obsidian vault using Foam in VSCode. I do.

You do need to align some options in each, such as file naming, a header, a particular style of links, and ensure frontmatter behavior. All necessary settings exist.

https://foambubble.github.io/foam/

https://github.com/foambubble/foam/issues/46

This supports basic static file and links functionality, not extended data tools etc., of course.