dedicated todoapp repository

[dolanor]

I believe the todoapp repo is in this repository to keep it synchronized with the main code.
But for newcomer, wouldn't it be nice to have a dagger/todoapp-example repo so people could fork at will and have already a github actions set up for use?

Just change netlify creds var and you're good to go.

Also, new users might not be aware/proficient with CI, yet, and don't know how to configure github actions, CI env var. So by making it the easiest, it would be maybe a magical "AHA" moment.

[gerhard]

We used to have an examples repository, which in practice was hard to keep in sync with this repository given the volume of changes.

We expect to add more examples (we used to have 2 and now have 3), and everything that the Dagger developers need to get started, including the source of truth for the built-in packages, is right there, two dir levels up:

We also test the todoapp ourselves, and maybe could do a better job at tying this into todoapp.cue. That will be one welcome PR 😉

Given all the above, do you still think that we should have a separate repo for the todoapp?

[dolanor]

No, I was also weighing the pros of having a monorepo for better integration vs making the examples harder to try.
I guess it's more a documentation issue than a tooling one.

[dolanor]

Actually reopening and self assigning because that doc needs to exist

[dolanor]

closing by using a better described issue: #1916