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
Hey it's super exciting to see whalebrew! I've been working on a similar concept that also uses labels to augment runtime and a /woirkdir concept, and think it would be cool to make my project compatible with whalebrew images. In a perfect world we (the community) could create, publish, and pull from eachothers images.
Admittedly dex hardly has a community outside my workplace ATM. It also suffers documentation clarity issues and the runtime is a work-in-progress(I kind of stalled on darwin/MacOS X11 and am worried about over/under architecting some labels) -- but I wanted to reach out nonetheless! :) Do you think sharing thought-space solving these issues (e.g. label names and behaviors, mount points, &c) worth pursuing?
The text was updated successfully, but these errors were encountered:
These were my ideas around providing convenience around common behavior (e.g. toggling X11 support) as well as providing flexibility for customizations (exposing devices and volumes). Not sure what is/is not needed (it's a work in progress) but thought it would be cool to come up with a standard.
Hey it's super exciting to see whalebrew! I've been working on a similar concept that also uses labels to augment runtime and a /woirkdir concept, and think it would be cool to make my project compatible with whalebrew images. In a perfect world we (the community) could create, publish, and pull from eachothers images.
Admittedly dex hardly has a community outside my workplace ATM. It also suffers documentation clarity issues and the runtime is a work-in-progress(I kind of stalled on darwin/MacOS X11 and am worried about over/under architecting some labels) -- but I wanted to reach out nonetheless! :) Do you think sharing thought-space solving these issues (e.g. label names and behaviors, mount points, &c) worth pursuing?
The text was updated successfully, but these errors were encountered: