Mot
It would integrate. And think of more straightforward vault mechanisms to start: 1. Postgres 2. Redis 3. etc etc. Where a layer is placed on top of these for column/key...
Thanks @nikolay for reporting this. We have this on our TODOs.
Interesting, we're looking into this.
@chungweileong94 does Vite have a concept of public ENVs - simlar to `NEXT_PUBLIC_` or `REACT_APP_` ? At first look, it looks like Vercel Funtions permit public ENVs but not standard...
Can you try putting a public ENV (with Vite's mechanism to preface it) in your .env? I think Vercel's functions respect that at the moment - since functions are sort...
@chungweileong94 did that do the trick to unblock you?
Ok, a few things we've learned so far. Do these line up with what you are seeing: 1. In local development, ANY environment variable in your .env file is made...
I added a discussion here to ask Vercel. https://github.com/vercel/next.js/discussions/39705
Ok, I will personally try out remix and work on alternatives. In the meantime, keep using the deprecated Vercel integration. We will be keeping it around.
@chungweileong94 try the new Integrate Everywhere™ functionality with Vercel's functions. As long as Vercel allows you to package and read files with their functions then it should work. https://www.dotenv.org/docs/tutorials/integrations