Skip to content

Commit 996dca4

Browse files
committed
update README
1 parent b4c632c commit 996dca4

File tree

1 file changed

+11
-18
lines changed

1 file changed

+11
-18
lines changed

README.md

Lines changed: 11 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -235,24 +235,6 @@ You need to keep `.env` files in sync between machines, environments, or team me
235235
</details>
236236
<details><summary>Multiple Environments</summary><br>
237237

238-
Use [dotenvx](https://github.com/dotenvx/dotenvx) to generate `.env.ci`, `.env.production` files, and more.
239-
240-
&nbsp;
241-
242-
</details>
243-
244-
<details><summary>Deploying</summary><br>
245-
246-
You need to deploy your secrets in a cloud-agnostic manner? Use [dotenvx](https://github.com/dotenvx/dotenvx) to generate a private decryption key that is set on your production server.
247-
248-
&nbsp;
249-
250-
</details>
251-
252-
&nbsp;
253-
254-
## Multiple Environments
255-
256238
Use [dotenvx](https://github.com/dotenvx/dotenvx)
257239

258240
Run any environment locally. Create a `.env.ENVIRONMENT` file and use `--env-file` to load it. It's straightforward, yet flexible.
@@ -281,6 +263,17 @@ Hello local
281263

282264
&nbsp;
283265

266+
</details>
267+
<details><summary>Deploying</summary><br>
268+
269+
You need to deploy your secrets in a cloud-agnostic manner? Use [dotenvx](https://github.com/dotenvx/dotenvx) to generate a private decryption key that is set on your production server.
270+
271+
&nbsp;
272+
273+
</details>
274+
275+
&nbsp;
276+
284277
## Deploying
285278

286279
Use [dotenvx](https://github.com/dotenvx/dotenvx).

0 commit comments

Comments
 (0)