Back
Best practice for AppWrite functions and version control?
I'm transferring from Firebase and I'm used to being able to put multiple exports in my single node project and firebase would see them all as different functions. What's the best practice for AppWrite regarding having a single git reop? I originally thought I could have one root folder as my functions project, then mutliple sub-folders representing each function but obviously the function won't be able to see the package.json file when it goes to build which there are hacks around this but it sees very fiddly and was wondering if there is a better practice for this?
TL;DR
Developers transferring from Firebase to AppWrite are questioning the best practice for functions and version control. They are used to being able to put multiple exports in a single node project with Firebase. They want to know if it's possible to have one root folder as their functions project with multiple sub-folders for each function. This setup may create issues with package.json file visibility. A cleaner solution may be to have separate repositories for each AppWrite function to avoid complex hacks.