RubyMine run configuration environment variables and SDK path not applied in production deployment

Question

Run configuration works in the IDE, fails in production

I have a Ruby application that runs correctly when launched through a RubyMine Run/Debug Configuration, but fails when started by the production deployment script. The configuration defines a custom working directory, several environment variables, and points at an rbenv-managed Ruby SDK selected in the project settings.

Where the divergence seems to come from

My understanding is that the working directory, environment variables, and even the interpreter choice stored in the run configuration are IDE-side concerns: they shape how RubyMine spawns the process locally, but nothing in the deployed artifact carries them over. The production host uses a different Ruby version via its own rbenv setup and starts the app from a systemd unit with no explicit environment file.

I am also unsure how much of the SDK resolution (gem paths, gemset selection) is baked in at edit time versus resolved at launch, and whether the shell profile scripts that set up rbenv in an interactive terminal are even read when the IDE or an init system spawns the process.

Questions

Which parts of a RubyMine run configuration (working directory, env vars, SDK) are guaranteed to be IDE-only, and is there a supported way to export or share them with external launchers?
When rbenv shims are involved, does RubyMine resolve the interpreter and gem paths at configuration time or at each run, and how should that be mirrored in production?
Is there a recommended pattern (e.g., dotenv file, shared env file) so local IDE runs and production starts read the same variable set without duplication?

Tasadduq Burney · Answer

The divergence between your local IDE and production environment occurs because RubyMine run configurations are IDE-specific metadata. When you launch a process through RubyMine, the IDE spawns a child process and injects the defined environment variables and SDK paths at runtime. These settings are not compiled into your code or exported to deployment-ready artifacts.

What is IDE-only?
p>The following elements in a RubyMine run configuration are strictly for local execution:

Working Directory: Tells the IDE where to execute the command locally.
  Environment Variables: Injected directly into the local process environment by the IDE's launcher.
  SDK/Interpreter Path: Points the IDE to a specific binary (e.g., an rbenv shim) to provide code completion and run the code locally.

There is no native mechanism to 'export' these configurations to a systemd unit or a shell script. You must manually replicate this logic in your production orchestration tools.

rbenv and Path Resolution
RubyMine generally resolves the interpreter and gem paths at each run. If you point to an rbenv-managed Ruby, the IDE calls the shim, which then relies on the environment's PATH to find the correct version. In production, systemd units run in a non-interactive shell, meaning they do not source your .bashrc or .zshrc where rbenv is typically initialized. Consequently, the production environment may default to the system Ruby or fail to find gems entirely unless the path is explicitly set.

Recommended Pattern for Consistency
To avoid duplication and environment drift, move away from using IDE-defined variables and adopt a file-based approach:

Use a .env file: Create a `.env` file in your project root. Use a gem like dotenv in your Ruby application to load these variables during both development and production. RubyMine can be configured (via plugins) to load this file during debug.
  Systemd EnvironmentFile: In your production systemd unit, use the EnvironmentFile=/path/to/your/.env directive to inject variables into the process.
  Wrapper Scripts: If you must rely on rbenv in production, use a wrapper script that explicitly initializes rbenv before starting the app:

#!/bin/bash
export RBENV_ROOT="$$HOME/.rbenv"
eval "$(rbenv init -)"
cd /path/to/app
bundle exec rails server

Diagnostic Question: To provide a more specific command, is your production deployment using a container (like Docker) or a bare-metal/VPS?

RubyMine run configuration environment variables and SDK path not applied in production deployment

Run configuration works in the IDE, fails in production

Where the divergence seems to come from

Questions

1 answer

The divergence between your local IDE and production environment occurs because RubyMine run configurations are IDE-specific metadata.

What is IDE-only?

rbenv and Path Resolution

Recommended Pattern for Consistency

Your perspective belongs here.

0 question comments