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
Read a list of (lang, version) from either local ./runme.yaml or from $RUNME_CONFIG ( global on host).
Then feed those to the language package managers like rustup, or nvm, ruby-env or alternatives. There's also mise which would let you just iterate over (lang, version) and feed it into a file on the container and let it manage the rest:
[tools]
node = '22'python = '3'ruby = 'latest'
That being said I recommend devbox
because apart from languages, it would also allow for any binary that you could run locally and it works on CI out of the box .
seivan
changed the title
Use language package managers instead upstream languages for the dockerfile.
Use language package managers instead of os package manager for the dockerfile.
Feb 21, 2025
Read a list of
(lang, version)
from either local./runme.yaml
or from$RUNME_CONFIG
( global on host).Then feed those to the language package managers like rustup, or
nvm
,ruby-env
or alternatives. There's alsomise
which would let you just iterate over(lang, version)
and feed it into a file on the container and let it manage the rest:That being said I recommend devbox
because apart from languages, it would also allow for any binary that you could run locally and it works on CI out of the box .
instead of this
The benefit of using individual language manager is that it's easier to switch them out.
The text was updated successfully, but these errors were encountered: