Forge deployment clears .env file

Question

Ok, i'm not sure i've got this figured out quite right yet.

Everywhere i look, everyone says not to include your .env file in your repo. This makes sense. What I don't understand is how i'm meant to add the .env to a deployed site.

I'm building a laravel app and trying to deploy through forge. This much works, and then i edit the .env through the forge interface. This seems like a better approach indeed, except whenever another deploy goes through, the .env file gets wiped. So is there a better way to do this or is there a setting i need to check?

I have this problem too:( – Peter Kota Oct 11 '15 at 08:41 — Peter Kota, Oct 11 '15 at 08:41
@KótaPéter see my answer below – eurobob Oct 11 '15 at 09:20 — eurobob, Oct 11 '15 at 09:20

score 1 · Accepted Answer · answered Oct 11 '15 at 09:20

1

So i've found two solutions. One for forge, and one for envoyer.

For forge, I created a recipe that makes the .env file, and this seems to run when forge deploys.

However, the process is different if you use envoyer. In your project, navigate to the servers tab and click manage environment. This allows you to enter your environment variables and feels like a much cleaner way to do this.

Hope this helps any future people struggling with this!

answered Oct 11 '15 at 09:20

eurobob

221
1
4
18

Can you show me your forge recipe? How can I make .env from recpie? – Peter Kota Oct 11 '15 at 09:30
1

It's just a bash script: echo " DB_PASSWORD=XXXXXX (etc.) " > site-folder.com/.env – eurobob Oct 11 '15 at 10:07
(Multiple lines is fine, it just won't let me format it that way for a comment) – eurobob Oct 11 '15 at 10:08

score 0 · Answer 2 · answered Dec 03 '15 at 04:15

0

Actually this video says it will happen magically. The only thing you need to keep in mind that you need to have your set up with done first. Next time you deploy, symlink will be added automatically.

answered Dec 03 '15 at 04:15

Mikhail Kozlov

31
1

Forge deployment clears .env file

2 Answers2