RVM
asdf
Our great sponsors
RVM | asdf | |
---|---|---|
42 | 339 | |
5,046 | 20,215 | |
0.4% | 3.0% | |
7.2 | 7.9 | |
8 days ago | 11 days ago | |
Shell | Shell | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
RVM
-
Ruby version
rvm (probably the most used manager)
-
Problems starting msfdb init
One suggestion would be to setup your install based on a development environment using git and a Ruby version manager like rvm or rbenv to allows you to setup a user controlled gemset and execution path.
-
Where is the best place to get specific help with errors during a Ruby install?
If you're using rvm, then the rvm repository.
-
Codespaces .devcontainer fails for Android SDK
2023-04-30 03:17:03.814Z: #20 55.72 #20 55.72 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. #20 55.72 #20 55.84 #20 55.84 Warning: PATH set to RVM ruby but GEM_HOME and/or GEM_PATH not set, see: #20 55.84 https://github.com/rvm/rvm/issues/3212 #20 55.84 2023-04-30 03:17:05.920Z: #20 57.89 ./install.sh: 32: Syntax error: "(" unexpected #20 57.89 ERROR: Feature "Android SDK" (ghcr.io/jarrodcolburn/features/android-sdk) failed to install! 2023-04-30 03:17:06.624Z: #20 ERROR: executor failed running [/bin/sh -c cp -ar /tmp/build-features-src/android-sdk_5 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/android-sdk_5 && cd /tmp/dev-container-features/android-sdk_5 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/android-sdk_5]: exit code: 2 2023-04-30 03:17:06.630Z: ------ > [dev_containers_target_stage 8/9] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=android-sdk_5,target=/tmp/build-features-src/android-sdk_5 cp -ar /tmp/build-features-src/android-sdk_5 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/android-sdk_5 && cd /tmp/dev-container-features/android-sdk_5 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/android-sdk_5: #20 55.60 done. #20 55.72 #20 55.72 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. #20 55.72 #20 55.84 #20 55.84 Warning: PATH set to RVM ruby but GEM_HOME and/or GEM_PATH not set, see: #20 55.84 https://github.com/rvm/rvm/issues/3212 #20 55.84 #20 57.89 ./install.sh: 32: Syntax error: "(" unexpected #20 57.89 ERROR: Feature "Android SDK" (ghcr.io/jarrodcolburn/features/android-sdk) failed to install! ------ 2023-04-30 03:17:06.633Z: ERROR: failed to solve: executor failed running [/bin/sh -c cp -ar /tmp/build-features-src/android-sdk_5 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/android-sdk_5 && cd /tmp/dev-container-features/android-sdk_5 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/android-sdk_5]: exit code: 2 2023-04-30 03:17:06.659Z: Stop: Run: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder 2023-04-30 03:17:06.664Z: {"outcome":"error","message":"Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder","description":"An error occurred setting up the container."} 2023-04-30 03:17:06.671Z: Error: Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder 2023-04-30 03:17:06.675Z: at wse (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1916:3264) 2023-04-30 03:17:06.677Z: at K7 (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1916:3200) 2023-04-30 03:17:06.679Z: at processTicksAndRejections (internal/process/task_queues.js:95:5) 2023-04-30 03:17:06.680Z: at async Hse (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1931:2626) 2023-04-30 03:17:06.695Z: at async Ch (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1931:3741) 2023-04-30 03:17:06.706Z: at async cae (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2059:17376) 2023-04-30 03:17:06.715Z: at async uae (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2059:17117) 2023-04-30 03:17:06.717Z: devcontainer process exited with exit code 1 ====================================== ERROR ==================================== 2023-04-30 03:17:06.724Z: Failed to create container. ================================================================================= 2023-04-30 03:17:06.726Z: Error: Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder 2023-04-30 03:17:06.729Z: Error Code: 1302 ====================================== ERROR ==================================== 2023-04-30 03:17:06.731Z: Container creation failed. ================================================================================= 2023-04-30 03:17:06.741Z: ===================================== WARNING =================================== 2023-04-30 03:17:06.758Z: Creating recovery container. =================================================================================
-
Is there any reason to use Ruby 2.7 over Ruby 3.x?
For my local machine, I use RVM (head). Other options are rbenv and asdf.
- I'm at the end of my rope with my MacBook reverting to referencing some Ruby 2.6 version I can't remove because it seems to be built into my operating system...
-
Help in learning Sinatra (Ruby)
You can use tools like rbenv(https://github.com/rbenv/rbenv) and rvm(https://rvm.io/) to be able install and easily switch between different ruby versions
-
.Net dev using rails for side hustle
It depends how you install it. If you install it globally then it will work for all your projects. Are you using rvm for ruby version and gemset management? https://rvm.io/
-
react-native init - failed to build gem native extension - desperately need help
source 'https://rubygems.org'# You may use http://rbenv.org/ or https://rvm.io/ to install and use this versionruby '2.7.5'gem 'cocoapods', '~> 1.11', '>= 1.11.2'
-
Any suggestions on environment options to be able run old Ruby version required by an old app?
So, I try to `rvm install 2.6.1` however i run into this compilation issue for which a correct solution hasn't yet been found, only workarounds, the most hopeful one for me seems to be this one where people report downgrading xcode to v13.6 enables Ruby 2.6 to work. However my OS reports that it's incompatible with the earlier xcode 13.6 version, so I'm now stuck. I'm not prepared to downgrade OS to try to workaround this issue due to other potential conflict and compatibility issues.
asdf
-
Volta – Fastest Node version manager in Rust
Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions
-
Pyenv – lets you easily switch between multiple versions of Python
https://asdf-vm.com/ ASDF is better because it works with many more languages, other than only Python, like Rust, Go, Node, etc, and other tools, such as AWS/Google/Firebase/Azure CLIs.
Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?
These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…
We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.
-
A Journey to Find an Ultimate Development Environment
The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).
-
Beginners Intro to Trunk Based Development
Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).
-
Practical Guide to Trunk Based Development
There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:
-
Criando seu ambiente com ASDF
git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.13.1
-
Kotlin version manager
I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.
-
How do i keep my "devops tool" always up to date in a smart way ?
I use the asdf version manager.
What are some alternatives?
SDKMan - The SDKMAN! Command Line Interface
pyenv - Simple Python version management
rbenv - Manage your app's Ruby environment
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
volta - Volta: JS Toolchains as Code. ⚡
HomeBrew - 🍺 The missing package manager for macOS (or Linux)
mise - dev tools, env vars, task runner
jenv - Manage your Java environment
nvm for Windows - A node.js version management utility for Windows. Ironically written in Go.
fnm - 🚀 Fast and simple Node.js version manager, built in Rust
nix - Nix, the purely functional package manager