---
name: bluedrop-cloud
description: Prepare an existing Drupal or Symfony repository for Blue Drop Cloud hosting with a project .conductor/config.yml, build commands, startup hooks, cron, and portable settings. Use when deploying or migrating a project to Blue Drop Cloud.
---

# Prepare a project for Blue Drop Cloud

Inspect the repository before changing it. Read its agent instructions, composer.json/lock, package.json files, document root, settings, exported configuration, and existing .conductor files. Preserve unrelated changes. The directory is `.conductor`, not `.coductor`.

Read https://agents.bluedropcloud.com/bluedrop-cloud/references/project-contract.md for the supported manifest and runtime contract. Use that URL if this reference is not installed locally. The human guide is https://concourse.bluedropcloud.com/help.

1. Identify Drupal or Symfony, the real document root, Composer PHP constraints, runtime dependencies, and asset build location. Check the PHP version selected for the target environment; never upgrade the framework or dependency lockfile merely to prepare hosting.
2. Create or refine `.conductor/config.yml`. Use argument arrays for commands. Add scripts only when the application needs them. Do not overwrite working settings, existing hooks, or scheduled jobs wholesale.
3. Distinguish an existing installed database from a fresh installation. An existing site should import its database before normal startup commands. Do not automatically install Drupal, overwrite a database, or import configuration without confirming the intended workflow. Report when the database is required rather than swallowing failed commands.
4. Make settings portable. Blue Drop Cloud supplies database credentials and Drupal's persistent files mount. Inspect Pantheon-specific includes, Redis, Solr, trusted hosts/proxies, and URL assumptions. Remove dependency on unavailable Pantheon services only with an equivalent configuration or an explicit explanation. Secrets Manager runtime calls may need conversion to getenv; do not assume copying a secret makes Pantheon APIs available.
5. Keep credentials out of Git and builds. Use the platform Variables interface for runtime secrets. Do not commit dumps, archives, `.env.local`, auth.json, tokens, host configuration, or `.conductor/secrets`.
6. Validate YAML, paths, executable scripts, PHP compatibility, and command behavior using the project's documented local runner. Do not invoke production hooks locally, install unknown tools, deploy, or mutate remote data merely to validate the manifest. Give the user a concise list of changes, checks, unresolved dependencies, and import/deployment order.

When migrating from Pantheon, preserve its live site and domains. The Blue Drop Cloud import flow creates backups of a chosen source environment and copies code, database and files into a new destination. Review environment variables; never reuse Pantheon's database, Redis or provider connection credentials as Blue Drop Cloud platform settings.