Ruby Versions
Ruby Versions
The platform supports the latest major Ruby releases and regularly updates the corresponding application-server stacks. You can select the required Ruby version during environment creation and switch to another supported release later by redeploying the container.
Available Ruby Versions
The documented Ruby releases currently available on the platform are:
| Ruby Version | How It Can Be Selected |
|---|---|
| 3.2.10 | During environment creation or through container redeployment. |
| 3.3.10 | During environment creation or through container redeployment. |
| 3.4.8 | During environment creation or through container redeployment. |
| 4.0.1 | During environment creation or through container redeployment. |
Versions are updated regularly
The official Software Stack Versions document is updated weekly. Check it before creating or redeploying a production environment.
Create a Ruby Environment
Open the environment wizard
Click New Environment at the top of the platform dashboard.
Select the Ruby application server
Switch to the Ruby tab and choose the required application server: Apache or NGINX.
Select the engine version
Use the engine-version drop-down list in the central part of the topology wizard to choose the required Ruby release.
Complete the environment configuration
Configure the Cloudlet limit, public IP, region, and other required options, then click Create.
Change the Ruby Version
For an existing environment, change the Ruby version by redeploying its container or container layer.
Open the container update dialog
Use either of the following methods:
- Click Change Environment Topology, then click the current stack or tag version.
- Click Redeploy Container(s) beside the required node or layer.
Configure redeployment
Adjust the required settings in the redeployment dialog:
- Tag: Select the required Ruby version.
- Keep volumes data: Preserve data stored in mounted volumes.
- Simultaneous deployment: Redeploy all containers in the layer at the same time.
- Sequential deployment with delay: Redeploy scaled containers one by one to reduce downtime.
Scaled environments
Use sequential deployment when updating a multi-node Ruby layer to reduce application downtime.
Confirm the version change
Click Redeploy and confirm the operation in the pop-up window.
After the redeployment finishes, the selected Ruby version is applied to the node or all nodes in the selected layer.
Expected Result
A new Ruby environment is created with the selected application server and engine version, or an existing environment is redeployed to another supported Ruby release while preserving the selected volume data.
Important Notes
- Check the current Software Stack Versions document before production deployment.
- Verify application and gem compatibility before changing the Ruby version.
- Enable Keep volumes data when persistent volume data must be preserved.
- A simultaneous redeployment can interrupt all nodes in a scaled layer.
- Use sequential deployment to reduce downtime in multi-node environments.
- Review deployment and application logs after the update.
Common Issues and Solutions
| Issue | Solution |
|---|---|
| Required Ruby version is not listed | Check the weekly Software Stack Versions document and confirm that the release is supported by the selected Apache or NGINX Ruby stack. |
| Application fails after redeployment | Review Ruby compatibility, Gemfile requirements, native extensions, startup configuration, and application logs. |
| Persistent files are missing | Restore from backup and use the Keep volumes data option during future redeployment. |
| All scaled nodes become unavailable | Use sequential deployment with delay instead of simultaneous redeployment. |
| Redeployment option is unavailable | Wait for other environment operations to finish and verify that the selected layer supports redeployment. |