Would love to have more of these! Unfortunately there isn't a lot of tutorials and resources around to get inte dagster as beginner. So thank you for making this!

Joining other comments, I'd love to see more step-by-step tutorials and use cases. It took a few videos to grasp the concepts, and this one is a good one to start with. Docs are good, but videos are even better. I would love to see more of duckdb / dagster and ingestion cases.

Thank you for this great tutorial on dagster. Will explore dagster.

Great example of how to actually do meaningful stuff with actual context (no pun intended) completely free from “foo=bar”. Love it!

Aha, I was wondering if we could use context with assets like that - the docs had examples for using context with ops but not assets. Good demo, thanks

fk the learning curve on this shit.

Thanks for the very interesting demo. I'm still struggling to grasp some concepts and how they apply to my use cases. Elaborating on your demo, my use case would have additional requirements - the data can't be fetched in its entirety on every run of the schedule, like if GitHub had a volume limitation on the amount of data you can fetch, or rate limiting so that you can't call their API for every day of data - some days, the API might not respond but we still want to retry to fill that in - I also want to run this pipeline for, say, multiple repos. All the logic is exactly the same, but the repo changes. I may have to tweak some extra info other than the name of the repo I've looked into the docs but I'm still confused whether partitioned assets, multi assets for example will allow me to run my use cases, in a way that will solve our problems and remain within the asset based paradigm of dagster. We've used DAGs, partitions and scheduling on a 0.* Version of dagster which worked but came with some issues (partitions growing too large). Now that dagster seems to be moving away from that approach, I'd like to realign our work with the paradigm of the tools we use to ensure we're not using soon to be deprecated features. Thanks a lot if you find the time to help out :)

can you make a video how to define sensors in your dagster project..

Good Demo. Actually I am running dbt jobs on dagster in k8s Where i have scheduled some dbt assets which runs fine when it is materialized manually but gets failed sometime when tried to run on scheduled time. Though Dagster daemon is also set up. Do you have any inputs on it ? Appreciate your help.

When i execute dagster project scaffold --name ....., in the created directory does not appear workspace.yaml, how can i fix that? Thank you in advance

Why was it decided to showcase this demo with "@repository" as opposed to "Definitions"?

I am trying to install it. It does not work. Had to spin up docker, still does not work. Whats wrong. Can I get an actual non buggy guideline?

Am I the only one finding it weird that you basically coding inside the _init__.py file?

I am disappointed with the content as it was rushed. As a beginner, I would have loved a more structured and detailed tutorial/ crash course.