You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default database connection string provided in the .env file for the twenty repository appears to be incorrect. Specifically, the connection string causes authentication failures when attempting to connect to PostgreSQL.
Steps to Reproduce:
Clone the repository and set up the environment using the provided .env file.
Run the application or attempt a database connection.
Observe authentication failure due to an incorrect connection string format or credentials.
Expected Behavior:
The application should connect successfully to the PostgreSQL database using the provided .env configuration.
Suggested Fix:
Verify and update the default connection string in the .env file to ensure it follows the correct format: postgres:https://<username>:<password>@<host>:<port>/<database>
if possible i can work in this issue
The text was updated successfully, but these errors were encountered:
Good point, it's because docker's default is postgres:twenty (we use the Postgres super user), but the local setup (brew, wsl, etc.) defaults to using postgres:postgres ; we should probably just use postgres:postgres everywhere remove drop the instrusctions in the doc to create a twenty user (since it's a local setup anyway)
The default database connection string provided in the .env file for the twenty repository appears to be incorrect. Specifically, the connection string causes authentication failures when attempting to connect to PostgreSQL.
Steps to Reproduce:
Clone the repository and set up the environment using the provided .env file.
Run the application or attempt a database connection.
Observe authentication failure due to an incorrect connection string format or credentials.
Expected Behavior:
The application should connect successfully to the PostgreSQL database using the provided .env configuration.
Suggested Fix:
Verify and update the default connection string in the .env file to ensure it follows the correct format:
postgres:https://<username>:<password>@<host>:<port>/<database>
if possible i can work in this issue
The text was updated successfully, but these errors were encountered: