Skip to Content
Browse documentation

Manage Ruby Gems and Gemfile Downloads in UAPP

Install, update and remove sandbox Ruby gems and understand version-specific rows, default gems and generated Gemfile downloads in UAPP.

Open a website from Ruby → Ruby Gems, or use its gem-management action in Ruby Applications. The website must belong to your account and the Ruby Apps feature must be enabled.

Install gems

  1. Enter gem names in the package field, separated by newlines or commas.
  2. Select Install Gems.
  3. Review the website, names and count.
  4. Confirm, wait for processing and refresh installed versions.

Examples accepted by the panel's validator:

rails
rake:13.2.1

Names begin with a letter or digit and may continue with letters, digits, underscores, dots and hyphens. An optional colon introduces a version expression containing letters, digits, dots, asterisks, comparison symbols, tildes, plus signs or hyphens.

This is a restricted entry field. Do not paste Gemfile declarations, shell commands, URLs, spaces or command-line options. Entries are trimmed, deduplicated and sorted before task submission. Passing validation does not guarantee the package/version exists or works with the selected Ruby version.

Installed versions and default gems

The table can show multiple rows for a gem with multiple installed versions. Rows identified as default gems have no update/remove actions and cannot be selected for those operations.

Use names and versions to identify the intended row. Search and sorting help locate gems.

Update gems

Use an individual update action or select rows and choose Update Selected. Review the names and confirm. Version suffixes are stripped for update submission, so updating a version row targets the gem name rather than preserving that row's pinned version.

Inspect resulting versions and test the application afterward. An operation-started message is not proof of successful completion.

Remove gems

Use an individual remove action or Remove Selected. Review the website and selected entries and acknowledge that removal can stop the application before confirming.

Removal can break dependent code

The package operation can force removal without protecting dependent gems. Check the project requirements, preserve dependency files and keep a recovery path before confirming.

Removal is explicitly blocked in demo mode. Installation and updates do not share that explicit check in the reviewed handlers.

Download Gemfile

Select Download Gemfile. The filename contains the website name. The generated file declares RubyGems as its source and emits one exact version per gem, selecting the first available non-empty version that is not labelled default.

It does not export every installed version, default gems, the original project's groups, source declarations, platform rules or Gemfile.lock. Review it before using it elsewhere. Keep the project's original dependency files; this download is an inventory aid rather than a complete Bundler reproduction.

Busy or failed operations

Gem actions check for a deployment in progress. Wait and refresh instead of resubmitting. If versions do not change or the project fails to start, ask the provider to inspect package output and verify runtime compatibility.