environment-variables

问题 I want to use separate .env files for each mode (development, production, etc...). When working on my vue.js projects, I can use files like .env.development or .env.production to get different values for the same env key. (example: in .env.development: FOO=BAR and in .env.production: FOO=BAZ, in development mode process.env.FOO would be BAR, in production i'd be BAZ). I'm working on an Express server and want to use these same kinds of .env files to store the port, db uri, user, pwd... I know

问题 I am using AWS SSM Run Command with the AWS-RunShellScript document to run a script on an AWS Linux 1 instance. Part of the script includes using an environment variable. When I run the script myself, everything is fine. But when I run the script with SSM, it can't see the environment variable. This variable needs to be passed to a Python script. I had originally been trying os.environ['VARIABLE'] to no effect. I know that AWS SSM uses root privileges and so I have put a line exporting the

问题 I am making a react app with firebase and I want to use environment variables for the firebase config. this is the firebase config in my react apps src folder import firebase from "firebase" import "firebase/auth" console.log(process.env) const config = { //private stuff }; // Initialize Firebase firebase.initializeApp(config); firebase.analytics(); export default firebase the issue is with that console log, I am using that for debugging, it is logging NODE_ENV: "production" PUBLIC_URL: ""

问题 In my project I use the built-in python virtual env ( python -m venv ). To set environment variables I add multiple export VAR1=VALUE1 to the end of the venv/bin/activate . Obviously, when I delete the venv and create a new one, for example with the new python version all my env variables get lost. So, is there a way to preserve them? May be it is possible to define env variables when creating the venv? 回答1: instead of adding to activate export VAR1=VALUE1 consider writing them into their own

问题 I use dotenv for read environment variable. like this: let dotenv = require('dotenv').config({ path: '../../.env' }); console.log(process.env.DB_HOST); Now I wanna to save changes in .env file. I can't find any way to save variable in .env file. What should I do? process.env.DB_HOST = '192.168.1.62'; 回答1: .env file VAR1=var1Value VAR_2=var2Value index.js file const fs = require('fs') const envfile = require('envfile') const sourcePath = '.env' console.log(envfile.parseFileSync(sourcePath))

问题 I use dotenv for read environment variable. like this: let dotenv = require('dotenv').config({ path: '../../.env' }); console.log(process.env.DB_HOST); Now I wanna to save changes in .env file. I can't find any way to save variable in .env file. What should I do? process.env.DB_HOST = '192.168.1.62'; 回答1: .env file VAR1=var1Value VAR_2=var2Value index.js file const fs = require('fs') const envfile = require('envfile') const sourcePath = '.env' console.log(envfile.parseFileSync(sourcePath))

问题 I am running a spring boot dockerized application with embedded tomcat. I have a properties file called myconfig.properties under resources folder myconfig.properties myvariable=${ENV_MYVARIABLE} This file content is required during startup of app.The file is consumed by a library which is accessed during startup. Spring boot is replacing the envioronment variables under application.properties file but this env variable in myconfig.properties file is not replaced. The file is no where

问题 I am running a spring boot dockerized application with embedded tomcat. I have a properties file called myconfig.properties under resources folder myconfig.properties myvariable=${ENV_MYVARIABLE} This file content is required during startup of app.The file is consumed by a library which is accessed during startup. Spring boot is replacing the envioronment variables under application.properties file but this env variable in myconfig.properties file is not replaced. The file is no where

问题 I don't wan't to put sensitive Credentials (Like API-Keys, passwords...) into my branch. For this, GitLab (and other CI/CD-Services) are able to set Enviroment-Variables. They will be injected on deployment-process into the Script. I know about two ways for GitLab to set them: Via UI (Project ⇒ Settings ⇒ CI/CD ⇒ Variables) Via .gitlab-ci.yml As in my opinion the first way is the secure one, because none files with credentials are saved in the git-repo, it's also the more complecated way...

问题 I want to work with environment variables. Unfortunately, I am an inexperienced developer and decided very late to implement such a solution in my project. I'm trying to inject environment variables, located in .env file, to all JS files (not all of them using environment variables, but I thought it would be faster and easier). Currently, I'm using dotenv package but it is obviously working in one file at once. Should I use dotenv the standard way? Maybe there's a vulnerability I don't know