Services and databases
Attach a managed service to one project, connect it through a secret environment value, and manage its lifecycle without exposing it to the public internet.
Add a service
Available types are PostgreSQL, MySQL, MariaDB, MongoDB, Redis, Valkey, Meilisearch, ClickHouse, OpenSearch, and Kafka.
Open the form
Open Services and select Add service.
Choose the owner
Use Select project… to attach the service to the app that needs it.
Choose the type
Use Select type…, enter a short service name, and review any type-specific requirements.
Choose connection injection
For a type with a suggested connection string, enter the environment variable your app expects, such as
DATABASE_URLorREDIS_URL. This optional field saves the connection string as a secret project environment value. Leave it blank if you will add the value yourself.Create and save credentials
Select Create. Save the generated credentials shown after creation; they are displayed once in this response. Start the service if its status is stopped, and wait until it is running before connecting the app.
Connect the app
Injected connection strings are saved as secret project environment values. If you skipped injection, add the connection string under the project’s Environment variables using the internal hostname and credentials shown for the service. Run a new deployment after adding or changing a connection value.
Select Credentials to retrieve stored values later. This action requires privileged confirmation. The hostname follows nexus-<project-slug>-<service-name>; use the hostname and port shown in your own service details rather than guessing them.
Operate a service
- Start brings a stopped service online.
- Stop takes it offline without deleting its stored record.
- Logs opens recent service output.
- Import accepts a
.sqlor.sql.gzupload for a running PostgreSQL, MySQL, MariaDB, or MongoDB service. Use a dump format supported by the selected database.
Delete a service
Select Delete, confirm the named service, and complete privileged confirmation. Its data volume is preserved by default; deletion does not erase that volume.
What success looks like
Troubleshooting
The service is stopped or unhealthy
Select Logs before restarting it. Check storage, credentials, and the first error. Use Start after the cause is resolved.
The app cannot connect
Confirm the service belongs to the same project, the internal hostname and port are current, and the environment value name matches the app. Deploy again after changing environment values.
Credentials are unavailable
Complete privileged confirmation, then try Credentials again. If access is still denied, contact DeployGrove support without including any secret.