#Example codebase of a large directus project with many extensions?

1 messages · Page 1 of 1 (latest)

lyric mirage
#

I'm looking for examples on how best to structure a large directus project with many extensions. The docs fall short a little on this and I can't seem to find any after a quick search

#

My initial thoughts are something along the lines of a monorepo with each extension as a separate package 🤔 This way we can have shared entities, services etc.. then having a single app that packages them all together.

ancient grotto
#

I am quite curious too on that topic.
The way I have organized my own work is I think what you are suggesting. By having the directus extension folders inside my directus root folder. As I show here https://rphl.dev/blog/building-saas-with-directus-and-stripe-part4#layout-of-the-directus-extensions. In this example I only have 2 extensions, but in practice I have 3 plus a folder with my email templates.

Having them all at the same place seems the more convenient to me. But having to "build", then copy past the index.js file created in the proper extension folder for directus to use it is not optimal.

Adventures of a CTO
Building a SaaS with Directus and Stripe: Part 4, Stripe Webhooks.

Let's build the Stripe Webhooks endpoint used for a SaaS, built with Directus and Stripe Billing.