updated dev instructions
Massimo Melina committed
Feb 7, 2022 at 12:49 UTC
23f4b3c16f2c3121fe28c1dfa0e259aef563c596
2 files changed
+9
-2
README.md
+8
-2
@@ -159,11 +159,17 @@ more reassuring, like "found 0 vulnerabilities", hopefully.
159
160
One way of working on sources here is to `npm run watch-server`.
161
This will give you auto-restarting of the server on back-end changes.
162
-A good idea is to first clone/create your working config file, and set an env to point to it `HFS_CONFIG=/tmp/config.yaml`, so that your gitted config file is not changed.
162
+Set an env `DEV=1` to let the code know we are in a dev environment.
163
164
-If you want to work on the front-end too, you should *first*
164
+If you want to work on the frontend and admin too, you should *first*
165
1. set an env `FRONTEND_PROXY=3000`
166
2. `npm run start-frontend`
167
+1. set an env `ADMIN_PROXY=3001`
168
+2. `npm run start-admin`
169
+
170
+Having this env-s will make the server get all related stuff from the other dev servers.
171
+Otherwise, you should be sure that frontend and admin have been built, and its files are ready to be used in `dist` folder.
172
+In this latter case, the `DEV=1` you set before will make the server get the files from inside the `dist` folder.
173
174
# Plug-ins
175
todo.md
+1
@@ -1,6 +1,7 @@
1
# To do
2
- start without config file
3
- allowed referer
4
+- admin/plugins
5
- log rotation
6
- log filter option
7
- log filter plugin