RVM VS Ruby on Rails

After googling it seems this is what I can find on GitHub issues which appears to be the most recent thread on the issue, or a similar issue.

rvm (probably the most used manager)

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.

If you're using rvm, then the rvm repository.

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. =================================================================================

For my local machine, I use RVM (head). Other options are rbenv and asdf.

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

[!] There was an error parsing \Gemfile`: No such file or directory @ rbsysopen - /Users/transformhub/Desktop/rnapp/.ruby-version. Bundler cannot continue. # from /Users/transformhub/Desktop/rnapp/Gemfile:4 # ------------------------------------------- # # You may use http://rbenv.org/ or https://rvm.io/ to install and use this version > ruby File.read(File.join(dir_, '.ruby-version')).strip # # -------------------------------------------`

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/

[0] is a my favorite demonstration of it.

[0]: https://github.com/rails/rails/commit/b83965785db1eec019edf1...

Here's a real life example: Imagine a Ruby on Rails app on which a team of developers are working. The code is hosted on GitLab and all the work is coordinated using GitLab issues. In other words: For every commit, there's an associated issue and the issue number acts as a sort of primary key for documentation, time reporting and so forth. This convention has a few advantages, most notably the ability to easily learn more about how, when and by whom features were implemented as well as how this implementation came to be.

Ruby on Rails is regarded as one of the best ruby frameworks. It was the primary language in developing big projects such as Twitter and helped the language boost the community. Often referred to as “Rails,” Ruby on Rails is a web development framework with an MVC control structure and currently running its 6.1 version. The 16-year-old language has dramatically influenced the web development structures and managing databases, web pages, and other components on a web application.

In Rails 7.1, a new option _instance_methods is introduced, allowing developers to opt-out of the automatic generation of instance methods for enums. When enum is defined with _instance_methods: false, Rails will no longer generate methods like pending?, processed?, etc.

Rails isn't super opinionated about database writes, its mostly left up to developers to discover that for relational DBs you do not want to be doing a bunch of small writes all at once.

That said it specifically has tools to address this that started appearing a few years ago https://github.com/rails/rails/pull/35077

The way my team handles it is to stick Kafka in between whats generating the records (for us, a bunch of web scraping workers) and and a consumer that pulls off the Kafka queue and runs an insert when its internal buffer reaches around 50k rows.

Rails is also looking to add some more direct background type work with https://github.com/basecamp/solid_queue but this is still very new - most larger Rails shops are going to be running a second system and a gem called Sidekiq that pulls jobs out of Redis.

I'm looking forward to see what extractions from this will land on rails. For example: https://github.com/rails/rails/issues/50454

Here is what strict_loading does (source):

Kamal is a wonderfully simple way to deploy your applications anywhere. It will also be included by default in Rails 8. Kamal is trivial, but I don’t recommend using it on your development machine.

Here's the GitHub milestone I've based this article on — https://github.com/rails/rails/milestone/87