Skip to Content
Browse documentation

Manage Ruby Applications in UAPP

Review Ruby website sandboxes and change runtime, Rack startup file, public directory, environment and lifecycle settings.

Open Ruby → Ruby Applications. This page requires the Ruby selector feature.

Use the summary and searchable table to review website, Ruby version, startup script, public path, environment, deployment status, enabled state and actions. Ready/Deploying reflects a deployment marker, not website health.

Change the runtime

  1. Select the runtime edit action for the website.
  2. Review the website and current runtime.
  3. Choose an explicit installed Ruby version.
  4. Choose whether to reinstall packages.
  5. Read the destructive-operation warning and acknowledge your backup.
  6. Select Replace Runtime, wait for work and test the project.

The dialog includes Account default, but the current server validator accepts only explicit installed versions. Choose an installed version; ask the provider if you need inheritance.

The dialog warns that runtime replacement removes the environment and gems. The actual operation follows the reinstall choice: selecting it requests sandbox reinstallation; otherwise the panel records the version and requests a virtual-host rebuild. Do not assume the unchecked path rebuilds the environment or makes existing native extensions compatible.

Edit application settings

ControlAccepted value and scope
Startup scriptA Rack filename such as config.ru; begins with a letter or digit, followed by letters, digits, underscores or hyphens, ending in .ru. Directory paths and .rb files are not accepted here.
Public directoryRelative directory beneath the website document root, such as public; does not move that document root.
EnvironmentProduction or Development; requests an application service configuration rebuild.

Open the relevant edit action, verify the website and select Save Changes. The startup file must exist in the project.

Public-directory input allows 1–253 word characters, dots, slashes and hyphens, with no leading dot/slash or trailing dot/slash. Use a simple relative path without traversal components. Production selection does not replace Rails/application security configuration.

Enable or disable

Select the sandbox switch and confirm Enable Ruby Sandbox or Disable Ruby Sandbox. The switch retains its previous state while confirmation is pending. Disabling changes service configuration; it does not delete the environment.

Reinstall

Select Reinstall Ruby sandbox. Review the warning and acknowledge that you backed up the application and package list. Reinstallation rebuilds the environment using its current configured runtime and can remove installed gems. Save the dependency information first.

Delete

Select Delete Ruby sandbox and acknowledge the destructive operation. It removes the sandbox runtime and its gem environment and rebuilds service configuration. Website files are preserved, but the Ruby application stops running through that sandbox.

The panel removes Ruby application settings and resets the application/runtime selections to defaults. This is different from disabling.

Preserved files are not a running environment

Keep a verified project and data backup before deleting or reinstalling. Record dependencies and runtime requirements so the environment can be recreated.

Busy or failed actions

Changes check for deployment already in progress. Wait and refresh. Ask the provider to inspect a stuck task rather than repeatedly reinstalling.

If a rebuild fails, review current values before retrying because recorded settings may already have changed. Deletion is blocked in demo mode. Use Ruby Gems for dependency work.