From f0bc6a3635afdbf33fd8dff8e376a4a73b5be843 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Am=C3=A9lia=2EZz?= Date: Sat, 6 Apr 2024 12:29:45 -0300 Subject: [PATCH] docs: fixing the library name and simplifying use example --- README.md | 21 +++------------------ 1 file changed, 3 insertions(+), 18 deletions(-) diff --git a/README.md b/README.md index 40e4200..019e55a 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -

(🔺) Mozz.js

+

(🔺) Mozz.Env

Mozz is your Environment Enhancer

## How to use @@ -19,22 +19,7 @@ Let's set up two environments, one for development and one for production using } ``` -> In the Mozz profile you can set `@file` for every environment to change your `.env` file, for example: - -```json -{ - "production": { - "@file": ".env", - "hostname": "0.0.0.0" - }, - "development": { - "@file": ".env.local", - "hostname": "localhost" - } -} -``` - -And we will also configure the `MOZZ_ENV` environment variable: +We will also configure the variable `MOZZ_ENV` in `.env` so the library knows which environment we are wanting: ```env MOZZ_ENV="development" @@ -43,7 +28,7 @@ MOZZ_ENV="development" Now, we can move on to the code, just import `Mozz` and create a instance to access your environment settings ```js -const Mozz = require('mozz.js') +const Mozz = require('mozz.env') const Enhancer = new Mozz() Enhancer.env.hostname // localhost