STORAGE_LOCAL_PATH relative, why?
Why is storage set relative to process.cwd?
https://github.com/twentyhq/twenty/blob/8abd5be4b5f174e02be5b35141c5490ddc51ee20/packages/twenty-server/src/integrations/file-storage/file-storage.module-factory.ts#L26
GitHub
twenty/packages/twenty-server/src/integrations/file-storage/file-st...
Building a modern alternative to Salesforce, powered by the community. - twentyhq/twenty
3 Replies
Hi @π
Ήπ
°ππ
±π
΄π
΄, what would you expect? Would you want to be able to override it?
Note: This is currently mainly designed for non-production environment (vs S3 storage driver which is designed for production use cases) but there is actually no reason not using it for production in a stateful architecture
The behavior I expected was that it's a absolute directory meaning STORAGE_LOCAL_PATH=/data is actually stored in /data not $(pwd)/data which it ends up being.
we could maybe support both:
./folder would be relative to process.cwd() and /folder would be absolute
Could you open an issue on Github, I think this could be tackle by the community!