Skip to content

Commit 5af3181

Browse files
authored
add support for .pumaenv file (#251)
* add support for .pumaenv file Since using `.powenv` feels wrong, since this is not pow, and `.env` conflicts with Docker's default `.env` loading (Docker only supports plain variable assignments), I figured it might be good to have a Puma-named env file. * Update README.md
1 parent e264766 commit 5af3181

File tree

2 files changed

+5
-0
lines changed

2 files changed

+5
-0
lines changed

README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -181,6 +181,7 @@ Puma-dev supports loading environment variables before puma starts. It checks fo
181181
* `.env`
182182
* `.powrc`
183183
* `.powenv`
184+
* `.pumaenv`
184185

185186
Additionally, puma-dev uses a few environment variables to control how puma is started that you can overwrite in your loaded shell config.
186187

dev/app.go

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -251,6 +251,10 @@ if test -e .powenv; then
251251
source .powenv
252252
fi
253253
254+
if test -e .pumaenv; then
255+
source .pumaenv
256+
fi
257+
254258
if test -e Gemfile && bundle exec puma -V &>/dev/null; then
255259
exec bundle exec puma -C $CONFIG --tag puma-dev:%s -w $WORKERS -t 0:$THREADS -b unix:%s
256260
fi

0 commit comments

Comments
 (0)