-
Extra environment variables support simple templating. We purposely did not implement extended variable expansion like `${VAR:-default}` or shell expression `$(process)`. The template values are comin…
tiran updated
3 hours ago
-
We still have a problem with different parsing of env files in `docker compose` and `docker run`
Files:
`.env.test`
```bash
TEST_VAR='{"key": "value"}'
```
`test.Dockerfile`
```dockerfile…
-
The worker start script, once the server has started, should delete WORKER_SECRET from the env.
This ensures that once the worker instance has the secret in memory, any attacker on the server can …
-
.env.example is outdated components. Sync them with the env variables used in the project
Todos:
- [ ] api
- [ ] webapp
- [ ] manager
-
For best practice use a .env file for the development
-
### Bug Description
I start langflow like this:
python3 -m langflow run --env-file .langflow.env
it doesn't respect the env file.
Here is the env file I am using:
LANGFLOW_SUPERUSER=admin
LA…
-
There is an env var in .env file: NEXTAUTH_URL
By default, it's "http://localhost:3000", and the admin is supposed to change it to "https://myhoarder.myname.com".
This is not very friendly to re…
-
Please add the .env.sample file in the repository.
-
you dont have the .env-example file
-
Suggested fixes:
- read the API key from the `.env` using `dotenv` or similar
OR
- change the README to suggest exporting the key into the pipenv shell rather than using `.env`.