Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions .babelrc

This file was deleted.

4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,9 @@ $ npx veritas-env decrypt --input=./path/to/encrypted.json --output=.env

- ### Vercel

While I love Vercel and use it for numerous projects, it has the unfortunate limit of only allowing a total of `4KB` for environment variables. Use something like a credentials JSON file to work with Google libraries, and you've pretty much blown your entire budget.
While I love Vercel and use it for numerous projects, it previously had the unfortunate limit of only allowing a total of `4KB` for environment variables. Use something like a credentials JSON file to work with Google libraries, and you've pretty much blown your entire budget. This limit has been raised to `64KB` but middleware and edge functions are still confined to `5KB`.

Additionally, managing your secrets along side the rest of your source code has the added benefit of tracking changes over time and ensuring secret updates are deployed correctly.

Here's how you can configure your `next.config.js` to work with Veritas.

Expand Down
Loading