Env

In vite project I use only 2 files: .env.development .env.production The env auto match with your build process without extra manual modification. This post is imported from: https://thebrownbox.hashnode.dev/env-with-vite

I usually deploy my backend in railway. So I usually have only 2 env: local and prod. Create 2 env files: Copy file to .env file in deploy step in package.json Make sure in the PROD deployment we run the correct command (in this case is Railway) Make sure .env file is in .gitignore Note: Variables only load if you install @nestjs/config and import it from AppModule @Module({ imports: [ConfigModule.forRoot()], controllers: [AppController], providers: [AppService], }) export class AppModule {} This post is imported from: https://thebrownbox....

Managing environment variables in quasar quite simple. My use case only have 2 environments: local & production. So I have only 2 files: .env.dev : for local .env.prod: for production No need naming conventions when work with quasar: And access through process.env.name_of_var as normal This post is imported from: https://thebrownbox.hashnode.dev/env-files-in-quasar-vuejs