You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm very confused by this. I run my own gitea server, so having a .env is fine, until I want to mirror it to Github or some other more public facing repo.
Shouldn't it be cloning the repo as is and I can manually fill in the .env when I build and deploy? Nothing in the documentation states it (or I can't find it at least).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm very confused by this. I run my own gitea server, so having a .env is fine, until I want to mirror it to Github or some other more public facing repo.
Shouldn't it be cloning the repo as is and I can manually fill in the .env when I build and deploy? Nothing in the documentation states it (or I can't find it at least).
Beta Was this translation helpful? Give feedback.
All reactions