Hopefully I'm missing something in my searches. I see a Free Individual Plan, paid team for up to 10 users, but what if I'm running an Open Source project on a github org. What are my options for using Dagger Cloud with a project like that? We have around 100 contributors, I'd say around 30 or so are active on any given month. Are there options for us?
#Dagger Cloud Plan for Open Source projects?
1 messages · Page 1 of 1 (latest)
Hey! We got you. https://dagger.io/blog/public-traces
Can you share the project? And also if you’re hoping for people to just have access to view traces or if you would like people to be able to send their own traces? (I.e from a fork or local machine)
we have options for all of these use cases, excited to hear more.
Thanks. https://github.com/gnolang/gno This is our primary repo. As for sending traces from forks, I'm open to ideas there. We current running GH workflows on PRs from forked repos.
Thanks for sharing! If you’re running forked PR workflows then those traces would still be sent from your main org and contributors will be able to see it.
Is the built in feature that Marcos shared sufficient for you, or are you hoping to have some other capabilities as well?
That would be a very familiar workflow and one we'd be comfortable with.
Ok great! Are you already using dagger or just thinking about it? I poked around in the repo and did not see any obvious dagger things yet.
no, we've had internal discussions, and I was trying to get my ducks in a row before we started really digging in.
Ok sounds great!
Just to summarize: single user free plan + public traces should address your immediate use case.
If you discover things that are missing, just reach out to me directly and I am happy to help figure something out that makes senes.
--
Outside of this, it would be really great to learn more about how you heard of Dagger and what you are hoping to achieve with it.
so how do we deal with organizational management? I guess we have to have a single user's api key become the "blessed" admin?
There is an API token DAGGER_CLOUD_TOKEN that is used to send traces to dagger cloud, this token belongs to the org and not a user, so you would use that token inside of GitHub Actions which would then send the traces during the CI run.
Dagger cloud uses existing git metadata to show you things like the commit author and stuff that triggers the trace.
cool. So, I'm not trying to be dense, but I see my org is named my github username and that I have an org ID. but I'm not sure how to make an org for gnolang
ah, this is because I signed up with github. if I use our work email signup, I can actually name my org, it seems.
yeah... this is where I'm trying to wrap my head around management here. So if I spin up an org and we want more than one person to be able to manage it, we have a hard cap at 10 folks and that's a flat $50/month? and its all or nothing, we either trust an individual to manage this, or we subscribe for cloud?