github-starred/awesome-compose
2
0
Fork 0
mirror of https://github.com/docker/awesome-compose.git synced 2026-03-09 06:52:08 -05:00
Code Issues 627 Packages Projects Releases Wiki Activity

Remove "environs" requirement from Django? #119

New Issue
Open
opened 2025-11-06 14:19:09 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 14:19:09 -06:00
Owner
Copy Link

Originally created by @weslord on GitHub (Dec 22, 2024).

Instances of env() can be replaced with os.environ.get().

load_dotenv(find_dotenv()) can be removed entirely.

The sample project does not include a .env file, and if it did, wouldn't it make more sense to handle that in compose.yaml with env_file: .env?

Originally created by @weslord on GitHub (Dec 22, 2024). Instances of `env()` can be replaced with `os.environ.get()`. `load_dotenv(find_dotenv())` can be removed entirely. The sample project does not include a `.env` file, and if it did, wouldn't it make more sense to handle that in `compose.yaml` with `env_file: .env`?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
proposal
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#119
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?