Skip to Content
Browse documentation

Ruby Selector

Assign an installed Ruby runtime to a domain or inherit the server default, then verify generated configuration and application behavior.

Open Runtimes → Ruby → Ruby Selector.

Read the domain table

The table displays Domain, Owner, saved Ruby runtime, account Status and Action. It uses hosting-domain metadata, not a scan of running Rails applications.

Active means the account is not marked suspended; it is not a service health result. Suspended rows do not expose the runtime-change control. Ordinary domain links open the website; wildcard domains do not receive a normal website link.

Search, sort and paginate to find the intended domain. The initial page size is 25; 10, 50, 100 and All are available.

Change a runtime

  1. Record the current selection.
  2. Click the domain's change-runtime control.
  3. Review the domain and select an installed runtime, or default to inherit.
  4. Click Change Runtime.
  5. Read the result and verify the generated configuration and site.

The request carries domain and owner values, each required and limited to 200 characters, plus a required runtime limited to 20 characters. Use the choices supplied from the installed inventory.

Application effects

The helper writes the domain's Ruby selection and invokes the shared virtual-host builder. That builder can regenerate the domain's configured web stack, so review other pending configuration changes before using the action.

The selector helper does not explicitly restart a Ruby application process. Verify the application's effective runtime and use the appropriate lifecycle workflow when required.

Inspect partial failures

The domain metadata is written before building. A builder failure can therefore leave the saved selection changed even though the operation reports failure. Check saved values, generated configuration and logs before retrying.

Troubleshooting

If a version is unavailable, select a listed installed runtime. For missing domain data, ownership problems or I/O/build errors, investigate the intended account configuration; do not substitute another account's values.

Test required gems and native extensions with the application's actual runtime and launch path. A successful panel response does not prove application compatibility.

Demo sessions cannot change runtime selections. See Ruby Settings for the separate server default action.