Skip to Content
Browse documentation

Deploy a Ruby Application in UAPP

Configure all Ruby deployment fields, choose an installed runtime and review the demo application environment behavior in UAPP.

Open Ruby → Deploy Ruby App. This requires the Ruby Apps feature, an eligible account-owned website and at least one configured installed Ruby version.

Deployment fields

FieldRequired selection or value
WebsiteAn owned website without existing Ruby sandbox configuration.
Ruby VersionA listed installed runtime; the configured default is selected when present in the list.
Startup ScriptInitially config.ru; a simple Rack filename with a letter/digit first, letters/digits/underscores/hyphens in its stem, and a .ru extension.
Public DirectoryInitially public; a relative directory beneath the website document root.
EnvironmentProduction initially, or Development, subject to the demo behavior below.
Demo ApplicationNo, I will upload the application initially, or Install a demo application.

The application type is Ruby on Rails; there is no separate framework selector. The document-root prefix updates for the selected website and is informational.

Public-directory validation allows 1–253 word characters, dots, slashes and hyphens, without a leading dot/slash or trailing dot/slash. Use a simple relative path without traversal components. Startup-script input does not accept paths or .rb filenames.

Demo deployment uses Development

Selecting a demo application forces the saved environment to Development, even if Production was selected. Review the resulting environment after deployment and configure the project appropriately before public use.

Start deployment

  1. Back up any existing website project.
  2. Select the website, runtime, startup file and public directory.
  3. Set the environment and demo choice.
  4. Select Deploy Ruby App.
  5. Review the website, runtime, application and environment in the deployment dialog.
  6. Confirm, read the result and open Ruby Applications.
  7. Wait for deployment work and test application startup and requests.

The server rejects an existing Ruby sandbox configuration or an active deployment. Disabling a sandbox does not make it eligible for another deployment.

Your application or sample files

Choose the upload option for an existing project. Supply its Rack entry point, dependencies, configuration and data connections. Creating a sandbox does not migrate an application.

The demo option requests sample application deployment. Do not use it over an existing project without preserving the files and understanding its changes.

Missing form or failure

The form is hidden when either eligible websites or installed runtimes are absent. Check both with the provider.

Refresh after a failure before retrying: settings may already have been recorded. Resolve the current task state before deleting a sandbox or starting another deployment.