You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have observed 2 distinct patterns for how to use Dagger in combination with an application repository:
Embedded. Sometimes one wants to embed a Dagger workflow directly in an application repository, in the same way one might embed a Dockerfile or docker-compose.yaml.
Standalone. Sometimes one wants to develop a Dagger workflow separately, from any application repository.
How Dagger supports these two patterns, and how to make sure each user follows the correct pattern for their needs, is an important UX question with many ramifications. This thread is a request for comment on this topic :)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have observed 2 distinct patterns for how to use Dagger in combination with an application repository:
Embedded. Sometimes one wants to embed a Dagger workflow directly in an application repository, in the same way one might embed a Dockerfile or docker-compose.yaml.
Standalone. Sometimes one wants to develop a Dagger workflow separately, from any application repository.
How Dagger supports these two patterns, and how to make sure each user follows the correct pattern for their needs, is an important UX question with many ramifications. This thread is a request for comment on this topic :)
Beta Was this translation helpful? Give feedback.
All reactions