Current deployment process is tightly coupled with render.com blueprints.
Most environment variables are sane, but some of the secrets cannot be published in repository (e.g. database passwords).
To run new deployment, first create environment groups for secrets: backend/mainnet/secret, backend/testnet/secret, backend/secret/secret and add missing environment keys.
For every backend there should be keys:
NEAR_READ_ONLY_INDEXER_DATABASE_HOST
NEAR_READ_ONLY_INDEXER_DATABASE_NAME
NEAR_READ_ONLY_INDEXER_DATABASE_USERNAME
NEAR_READ_ONLY_INDEXER_DATABASE_PASSWORD
NEAR_READ_ONLY_ANALYTICS_DATABASE_HOST
NEAR_READ_ONLY_ANALYTICS_DATABASE_NAME
NEAR_READ_ONLY_ANALYTICS_DATABASE_USERNAME
NEAR_READ_ONLY_ANALYTICS_DATABASE_PASSWORD
NEAR_READ_ONLY_TELEMETRY_DATABASE_HOST
NEAR_READ_ONLY_TELEMETRY_DATABASE_NAME
NEAR_READ_ONLY_TELEMETRY_DATABASE_USERNAME
NEAR_READ_ONLY_TELEMETRY_DATABASE_PASSWORD
In case backend should expect node telemetry, there should be keys as well:
NEAR_WRITE_ONLY_TELEMETRY_DATABASE_HOST
NEAR_WRITE_ONLY_TELEMETRY_DATABASE_NAME
NEAR_WRITE_ONLY_TELEMETRY_DATABASE_USERNAME
NEAR_WRITE_ONLY_TELEMETRY_DATABASE_PASSWORD
The easiset way to deploy Explorer is to create new blueprint instance in your workspace and select this repository (or your fork, containing render.yaml).
To deploy Explorer on another hosting platform, please refer to render.com blueprint specification and actual Explorer blueprint.