Set up the explicitly selected Rails development project for the Conductor app. Frontmatter tool/context hints are host specific, not authorization to delegate, alter secrets or broaden permissions. Review existing scripts and lockfiles before running installs; preserve unrelated settings. When to Use You need to configure a Rails project so it runs correctly inside Conductor workspaces. The project should support parallel coding agents with isolated ports, Redis settings, and shared secrets. You want the standard conductor.json , bin/conductor setup , and script/server scaffolding for a Rails repo. What to Create 1. conductor.json (project root) Create conductor.json in the project root if it doesn't already exist: 2. bin/conductor setup (executable) Create bin/conductor setup if it doesn't already exist: Make it executable with chmod +x bin/conductor setup . 3. script/server (executable) Create the script directory if needed, then create script/server if it doesn't already exist: Make it executable with chmod +x script/server . 4. Update Rails Config Files For each of the following files, if they exist and contain Redis configuration, update them to use ENV.fetch('REDIS URL', ...) or ENV['REDIS URL'] with a fallback: config/initializers/sidekiq.rb If this file exists and configures Redis, update it to use: config/cable.yml If this file exists, update the development adapter to use: config/environments/development.rb If this file configures Redis for caching, update to use: config/initializers/rack attack.rb If this file exists and configures a Redis cache store, update to use: Implementation Notes Don't overwrite existing files : Check if conductor.json, bin/conductor setup, and script/server exist before creating them. If they exist, skip creation and inform the user. Rails config updates : Only modify Redis related configuration. If a file doesn't exist or doesn't use Redis, skip it gracefully. Create directories as needed : Create script/ directory if it doesn't exist. Verification After creating the files: 1. Confirm all Conductor files exist and scripts are executable 2. Validate script syntax first, then start the owned development server with a bounded observation window and a defined shutdown method; verify actual port/Redis separation across workspaces 3. Check that Rails configs properly reference ENV['REDIS URL'] or ENV.fetch('REDIS URL', ...) Limitations Secret symlinks share the same sensitive values across workspaces; use only approved development credentials, preserve owner only source permissions, exclude secrets from Git and do not imply worktrees are a secret sandbox. Sharing one Redis URL across Sidekiq, Cable and cache may still need service namespaces; dedicated instances or explicitly assigned namespaces are safer than modulo hashes. Never flush shared Redis as cleanup. npm/Gem installation and bin/dev execute project dependencies/scripts. Review them first; explicitly required lifecycle steps should be run individually after approval, not re enabled silently. Do not treat the output as a substitute for environment specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

conductor-setup