mirror of
https://github.com/hedgedoc/hedgedoc.git
synced 2024-11-25 19:26:31 -05:00
Remove section about production deployments
As this is meant to document a development setup. Signed-off-by: Falk Rehse <neuringe1234@gmail.com>
This commit is contained in:
parent
a3a2ffea6d
commit
954c751cca
1 changed files with 2 additions and 11 deletions
|
@ -25,18 +25,9 @@
|
|||
|
||||
2. Enter the directory and run `yarn install`.
|
||||
|
||||
## Running the Code
|
||||
## Running Hedgedoc with auto-reload
|
||||
|
||||
Now that everything is in place, we can start HedgeDoc:
|
||||
|
||||
**ToDo:** Document how to build the frontend and backend or remove this paragraph entirely.
|
||||
|
||||
## Running the Code with Auto-Reload
|
||||
|
||||
The commands above are fine for production, but you're a developer and surely
|
||||
you want to change things. You would need to restart both commands whenever you
|
||||
change something. Luckily, you can run these commands that will automatically
|
||||
rebuild the backend andfrontend or restart the server if necessary.
|
||||
We will run Hedgedoc in development mode, which means the backend and frontend will automatically rebuild or restart when you make changes.
|
||||
|
||||
The commands will stay active in your terminal, so you will need multiple tabs
|
||||
to run both at the same time.
|
||||
|
|
Loading…
Reference in a new issue