chore(dev): add connection with local directus instance

[Thechi2000]

Allow to use a local Directus instance for development. It uses two environment variables, set in the Dockerfile(.dev) files: DIRECTUS_URL and NEXT_PUBLIC_DIRECTUS_URL.

Provides a script to populate the database locally, as well as save its content.

The permissions for all the collections required by the website are set to read for the Public role, in order to get rid of the authentication token (only for dev).

[NoeTerrier]

Nice works ! Maybe the documentation on how to setup things should be clear that we need to populate directus. Why not having a setup command to do everything in a row?

I spotted some small bugs, and I don't know it it's a good thing that we need to specify all access policy for each table at hand.

It don't see any partner on the homepage despite we have some in directus, with valid times, can't find why.

[Thechi2000]

Thanks for the review ! I've added the missing entries in the sample data to correctly display the partners on the home page.

[Thechi2000]

Ok I just had a crazy idea: what if we were to put the Directus config into a dedicated repository, along with all the scripts and data ? This way, we could easily share those among repositories (website, infra, clicketing). We could have symbolic links for typescript declarations, which should work even through git.

I've got a working prototype on the branch 50-directus-development-environment-2, which uses a repo on my personal account, if you want to try it out (the doc is not updated yet).

What do you think ? @SidonieBouthors @NoeTerrier

[SidonieBouthors]

Honestly that sounds like a good idea

[NoeTerrier]

Not a bad idea, it should work. But the merging workflow should be ensured: website and directus repo should always be synched. But it will be better for other services too.
I'm down for it if both of you think it's better like that!

[Thechi2000]

I've migrated the config to the directus-config repo, don't hesitate to check that it's correct too :)

I'll start working on a PR for the infra repo to use this new workflow.

[NoeTerrier]

Nice, looks good, but I still have this problem with date-created.

[NoeTerrier]

So we don't use directus token anymore ? How does the website have permission to access data on directus ?
If not then we need to set permissions for collections for public user, wich is a bit annoying:

[Thechi2000]

Everything is public now (in dev only), this simplifies the setup since we do not need to generate an admin token and give it to Directus. I don't think having to set everything public is much of an inconvenience, it is quick and we won't do it very often.

[NoeTerrier]

Nice !
Well done, I think it is a great upgrade for the infra and the website development.