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
This release makes it easier to get started with Bass.
You don't need to set up Buildkit anymore. Bass will start its own Buildkit in Docker instead, a technique yoinked from Dagger. If you already have Buildkit set up you can keep using it. This change just lowers the barrier to entry.
Also: bass --runner (used for Bass Loop) will now display the remote host key and prompt whether to save it instead of erroring out. Huzzah!
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
-
This release makes it easier to get started with Bass.
You don't need to set up Buildkit anymore. Bass will start its own Buildkit in Docker instead, a technique yoinked from Dagger. If you already have Buildkit set up you can keep using it. This change just lowers the barrier to entry.
Also:
bass --runner
(used for Bass Loop) will now display the remote host key and prompt whether to save it instead of erroring out. Huzzah!What's Changed
New Features ✨
buildkitd
in Docker if not configured by @vito in auto-startbuildkitd
in Docker if not configured #212--debug
flag, default log level to info by @vito in add--debug
flag, default log level to info #213bass --run
for running thunk JSON passed on stdin by @vito in addbass --run
for running thunk JSON passed on stdin #215bass --runner
prompts to add to known_hosts by @vito inbass --runner
prompts to add to known_hosts #216Fixed Bugs 🐛
Other Changes
New Contributors
Full Changelog: v0.7.0...v0.8.0
This discussion was created from the release v0.8.0: easier setup.
Beta Was this translation helpful? Give feedback.
All reactions