Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add edgedb configuration #2058

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jere-co
Copy link
Contributor

@jere-co jere-co commented Apr 23, 2024

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:

# - EDGEDB_SERVER_TLS_CERT_FILE= 
# - EDGEDB_SERVER_TLS_KEY_FILE=

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:

Connecting to EdgeDB instance 'example-instance-name' at exampledomain.com:5656...
edgedb error: ClientConnectionFailedError: invalid peer certificate: BadSignature

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.?

edgedb.svg includes EdgeDB logo and add edgedb.yaml the
configuration for edgedb and postgres services. Commit includes setting
environment variables, volumes, health checks, and ports.
@jere-co jere-co changed the title Feature add edgedb configuration feat: add edgedb configuration Apr 23, 2024
@Xhoni96
Copy link

Xhoni96 commented May 22, 2024

@andrasbacsai Any chance you could have a look at this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants