64d5834b6a
- yarn classic workspaces already do what we need - The main benefit of turbo, the cache, is already disabled on dev builds. On production builds, turbo doesn't support `next build` (this is mentioned in Vercel's docs). - We're not using their remote cache - Maybe there is a monorepo size when the yarn workspace approach gets unwieldly, but I feel we're not near that point. Will bring it back if it gets missed. |
||
|---|---|---|
| .. | ||
| Dependencies.md | ||
| Dev.md | ||
| README.md | ||
Notes for maintainers
If you just want to run ente locally or develop on it, you can do
yarn
yarn dev:photos
The notes in this directory are for maintainers to note down more advanced or infrequently needed details.