File tree 3 files changed +4
-4
lines changed
3 files changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -29,9 +29,9 @@ def cli(pytest_args):
29
29
# pytest_args.append("-W")
30
30
# pytest_args.append("error::DeprecationWarning")
31
31
32
- os .environ .setdefault ("APP_ENV " , "test" )
32
+ os .environ .setdefault ("BOLT_ENV " , "test" )
33
33
34
- click .secho (f"Running pytest with APP_ENV ={ os .environ ['APP_ENV ' ]} " , bold = True )
34
+ click .secho (f"Running pytest with BOLT_ENV ={ os .environ ['BOLT_ENV ' ]} " , bold = True )
35
35
36
36
result = subprocess .run (
37
37
[
Original file line number Diff line number Diff line change @@ -32,7 +32,7 @@ The `.env` should then be in your `.gitignore`!
32
32
33
33
It would seem like ` .env.dev ` would be a good idea,
34
34
but there's a chicken-and-egg problem with that.
35
- You would then have to prefix most (or all) of your local commands with ` APP_ENV =dev` or otherwise configure your environment to do that for you.
35
+ You would then have to prefix most (or all) of your local commands with ` BOLT_ENV =dev` or otherwise configure your environment to do that for you.
36
36
Generally speaking,
37
37
a production ` .env ` shouldn't be committed in your repo anyway,
38
38
so using ` .env ` for local development is ok.
Original file line number Diff line number Diff line change @@ -43,7 +43,7 @@ def setup():
43
43
sys .path .insert (0 , APP_PATH .as_posix ())
44
44
45
45
# Load .env files automatically before settings
46
- if app_env := environ .get ("APP_ENV " , "" ):
46
+ if app_env := environ .get ("BOLT_ENV " , "" ):
47
47
load_dotenv (f".env.{ app_env } " )
48
48
else :
49
49
load_dotenv (".env" )
You can’t perform that action at this time.
0 commit comments