From 26ff2ef1b6f0ea529724c3b33e288f673864b402 Mon Sep 17 00:00:00 2001
From: Koen Punt <koen@koenpunt.nl>
Date: Thu, 4 Jun 2020 15:04:26 +0200
Subject: [PATCH 1/2] 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.
---
 dev/app.go | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/dev/app.go b/dev/app.go
index dbf3443e..718a46aa 100644
--- a/dev/app.go
+++ b/dev/app.go
@@ -251,6 +251,10 @@ if test -e .powenv; then
 	source .powenv
 fi
 
+if test -e .pumaenv; then
+	source .pumaenv
+fi
+
 if test -e Gemfile && bundle exec puma -V &>/dev/null; then
 	exec bundle exec puma -C $CONFIG --tag puma-dev:%s -w $WORKERS -t 0:$THREADS -b unix:%s
 fi

From 615ccfd925d3864352abb7ee885553fd45f9b548 Mon Sep 17 00:00:00 2001
From: Koen Punt <koen@koenpunt.nl>
Date: Thu, 4 Jun 2020 15:05:14 +0200
Subject: [PATCH 2/2] Update README.md

---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index 3403c344..f799c4f7 100644
--- a/README.md
+++ b/README.md
@@ -181,6 +181,7 @@ Puma-dev supports loading environment variables before puma starts. It checks fo
 * `.env`
 * `.powrc`
 * `.powenv`
+* `.pumaenv`
 
 Additionally, puma-dev uses a few environment variables to control how puma is started that you can overwrite in your loaded shell config.