feat: add edgedb configuration #2058
Open
+48
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EdgeDB has a launch week and it's reaching 5.0, so it feels like a good time to add it (back) to Coolify.
This PR includes EdgeDB logo and adds the edgedb.yaml, which includes setting environment the variables, volumes, health checks, ports, and some of the Coolify magic.
Caveats
TLS:
EdgeDB would ideally have its own certificates generated with files. These could be set via the following environment variables:
These are included in the PR's
edgedb.yaml
, but commented out as above.Currently each time the service is restarted, EdgeDB client starts warning:
Considerations
With External Database
EdgeDB can also be used with an external Postgres DB, which could be the way to go when in Coolify to leverage the backups etc.?