Fix for Issue 8701

[StormNinja17]

We added some basic code that checks if a Twenty user exists in the Postgre database. If the user doesn't exist, we create it and try to give it necessary permissions. If we are unable to give it the necessary permissions, we log that issue to the console and redirect users to the Twenty documentation. We updated the documentation with a command users can run to manually grant permissions to the new Twenty user.

Close #8701

[greptile-apps]

PR Summary

This PR adds functionality to create and manage a 'twenty' PostgreSQL user during Docker setup, along with corresponding documentation updates for manual permission management.

• Critical security issue: Hardcoded password 'twenty' in /packages/twenty-docker/twenty/entrypoint.sh needs to be replaced with environment variable
• Syntax error in user existence check: if [ ${PGPASS} psql...] in /packages/twenty-docker/twenty/entrypoint.sh is malformed
• Incorrect variable usage: TWENTYPASS should be PGPASSWORD in /packages/twenty-docker/twenty/entrypoint.sh
• Typo in success message: "Successfuly" should be "Successfully" in /packages/twenty-docker/twenty/entrypoint.sh

_{💡 (4/5) You can add custom instructions or style guidelines for the bot here!}

_{2 file(s) reviewed, 4 comment(s)
Edit PR Review Bot Settings | Greptile}

[prastoin]

Hey @StormNinja17 and all ! Hope you're doing great
Unless I'm mistaken as it is script have several bugs ( also checking ci status )

Overall regarding the entrypoint.sh updates, I don't think they can work at all.
In the first place if the user does not exist we won't be able to connect to the database the setup it. As by default the setup authentication is postgres:postgres the user we wanna create here.

We should be logging recommendation related to suggested added documentation

[StormNinja17]

@prastoin Thank you for the feedback!

I switched all references of a "twenty" user to "postgres". Instead of attempting to grant all privileges, I modified the script to attempt to make a superuser instead. I also consolidated the troubleshooting documentation like you requested.

[prastoin]

Hello @StormNinja17, unfortunately as said above i don't think this can work.
The postgres user does not exist occurs because that's the docker-compose.yml default database credentials. This means that we could transpile your code as:

PGPASSWORD=postgres psql -h whatever -p 5432 -U postgres -d postgres -tc "SELECT 1 FROM pg_roles WHERE rolname='postgres'"

Is paradoxical

What we should do is trying to perform a very basic query using the provided credentials, such as a SELECT 1. And log if we couldn't telling the user that the provided creds are wrong

[prastoin]

Rebased on lastest entrypoint.sh