npm init directus-project - Postgresql install error

[TargaTeam]

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

npm init directus-project myproject

installs, then asks database type;

postgresql

then asks server, port, database user etc...

this results in an error:

Something went wrong while seeding the database:

[42P07] create table "directus_collections" ("collection" varchar(64), "icon" varchar(30), "note" text, "display_template" varchar(255), "hidden" boolean not null default '0', "singleton" boolean not null default '0', "translations" json, "archive_field" varchar(64), "archive_app_filter" boolean not null default '1', "archive_value" varchar(255), "unarchive_value" varchar(255), "sort_field" varchar(64)) - relation "directus_collections" already exists

The database is empty and just created before installation.

A week or two ago i've done exactly the same and it worked fine. As plenty of times before.

To Reproduce

npm init directus-project myproject

What version of Directus are you using?

latest (?)

What version of Node.js are you using?

v10.19.0

What database are you using?

postgres 12

What browser are you using?

---

What operating system are you using?

ubuntu

How are you deploying Directus?

ubuntu server, locally

[azrikahar]

Hmm that's odd. Unfortunately can't seem to reproduce this on my end.

Would you mind upgrading to Node.js v.12.20 and try again? Since that is the minimum Node version currently supported by Directus.

If the project directory is created and there's a package.json file, can you share the content of the dependencies field?

Can you also verify the database is empty right before you press Enter for the final prompt in the CLI? just so we can be sure we're targeting the correct empty database.

[TargaTeam]

Thanks for the quick reply… I just managed to do a successful install. Somehow the database had the tables already, only visible by postgres user (superadmin). I don’t know how, but I removed the tables and after that everything worked fine. Sorry to bother you! My version of node was 14+ by the way, sorry. Met vriendelijke groet, Alex Völker Targa Web en Print Molenwerf 30 1911 DB Uitgeest T 0251 - 700 222 E ***@***.*** I www.targateam.nl AVG: TargaTeam gaat zorgvuldig om met uw gegevens. Meer hier over op: https://targateam.nl/privacyreglement <https://targateam.nl/privacyreglement>

…

Op 12 okt. 2021, om 11:12 heeft Azri Kahar ***@***.***> het volgende geschreven: Hmm that's odd. Unfortunately can't seem to reproduce this on my end. Would you mind upgrading to Node.js v.12.20 and try again? Since that is the minimum Node version currently supported by Directus. If the project directory is created and there's a package.json file, can you share the content of the dependencies field? Can you also verify the database is empty right before you press Enter for the final prompt in the CLI? just so we can be sure we're targeting the correct empty database. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8708 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG2XSK22VTSUX5UN53LE6GTUGP3YPANCNFSM5FZ67WDQ>.

[azrikahar]

No worries, glad it's resolved!