Framework support

Dotvault for Ruby on Rails

Dotvault for Ruby on Rails apps.

Rails has its own encrypted credentials system, but most real-world projects still lean on .env files for local development, CI, and Docker deploys. Dotvault gives you a proper editor for those files, detects Rails projects automatically, and plays nicely with dotenv-rails.

What you get

  • →Detects Rails via Gemfile.
  • →Recognises common Rails env vars: DATABASE_URL, RAILS_ENV, SECRET_KEY_BASE.
  • →Snapshot history and diff between environments.

Known environment variables

Dotvault recognises these variables when you open a Ruby on Rails project and surfaces helpful descriptions and warnings in the editor. Ruby on Rails is detected via rails in Gemfile.

  • RAILS_ENV

    Rails environment (development/production/test)

  • RACK_ENV

    Rack environment (mirrors RAILS_ENV)

  • SECRET_KEY_BASERequired

    Secret key for session cookies and encryption

  • DATABASE_URL

    Database connection URL

  • REDIS_URL

    Redis connection URL

  • RAILS_LOG_LEVEL

    Log level (debug/info/warn/error)

  • RAILS_SERVE_STATIC_FILES

    Serve static files from /public

  • RAILS_LOG_TO_STDOUT

    Log to stdout instead of file

  • RAILS_MASTER_KEY

    Master key for credentials encryption

  • RAILS_MAX_THREADS

    Puma max threads

  • WEB_CONCURRENCY

    Puma worker count

  • PORT

    Server listen port

  • BINDING

    Server bind address (0.0.0.0 for Docker)

  • PIDFILE

    Path to Puma PID file

  • LANG

    System locale for encoding

  • BUNDLE_WITHOUT

    Bundler groups to exclude

  • ACTIVE_STORAGE_SERVICE

    Active Storage service name

  • ACTION_CABLE_ADAPTER

    Action Cable adapter (redis/async/postgresql)

  • SOLID_QUEUE_IN_PUMA

    Run Solid Queue inside Puma process

  • RAILS_INBOUND_EMAIL_PASSWORD

    Password for Action Mailbox ingress

Official Ruby on Rails docs: guides.rubyonrails.org