Current release broken in multiple places for fresh install? (partly solved)

[GarryG]

Sorry, trying not to sound too bitchy, but after putting several hours into multiple attempts at install Supabase self-hosted, there seem to be multiple issues in the current release files that more or less prevent a working fresh install ... some of those seem to be:

• vector.yml is created as directory instead of a file (seems to have occurred as early as 2024)
• Kong has some restrictions on the password you use (special characters prevent the container to work)
• DB errors during initial setup ("psql:/docker-entrypoint-initdb.d/init-scripts/98-webhooks.sql: error: could not read from input file: Is a directory")
• _supabase DB isn't created/available (haven't located any reason for that yet)
  and possibly more that I just haven't gotten far enough to stumble over

In essence, what I'm wondering: Has anybody gotten Supabase working lately using the official setup docs and current docker images? It's at least somewhat frustrating to following the docs by the letter, and due to either changed requirements, missing hints as to what to watch out for, or just plain bugs in the setup processes to end up with problems that are partly know for quite some time ...

[GarryG]

OK, after having removed all the storage directories and setups multiple times, I - once again - did a complete REALLY fresh install - using the simpler passwords, most of the system now came up. I still see some problems (e.g. can't create users - the progress indicator just rotates for quite some time, user is never created; errors in different containers like supabase-rest, etc.), but the general Studio frontend appears to be working. Will need to see if it actually DOES work when accessing from other apps like N8N, but at least there's some progress