From 077bebe17889d8a0cff2a1dbfebd72b4b8147ab3 Mon Sep 17 00:00:00 2001 From: SF-Zhou Date: Wed, 22 Mar 2017 23:02:49 +0800 Subject: [PATCH] doc: fix table render error in en env.md (#621) --- docs/source/en/basics/env.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/source/en/basics/env.md b/docs/source/en/basics/env.md index dd58783099..da4320e120 100644 --- a/docs/source/en/basics/env.md +++ b/docs/source/en/basics/env.md @@ -31,11 +31,11 @@ Lots of Node.js applications use `NODE_ENV` for environment setting, but `EGG_SE Default mapping of `EGG_SERVER_ENV` and `NODE_ENV` (will generate `EGG_SERVER_ENV` from `NODE_ENV` setting if `EGG_SERVER_ENV` is not specified) -NODE_ENV | EGG_SERVER_ENV | remarks ----------- | -------------- | ------------ - | local | local development environment -test | unittest | unit test environment -production | prod | production environment +| NODE_ENV | EGG_SERVER_ENV | remarks | +| ---------- | -------------- | ----------------------------- | +| | local | local development environment | +| test | unittest | unit test environment | +| production | prod | production environment | For example, `EGG_SERVER_ENV` will be set to prod when `NODE_ENV` is production and `EGG_SERVER_ENV` is not specified.