mirror of
https://github.com/hedgedoc/hedgedoc.git
synced 2025-05-23 03:27:05 -04:00
Docs: Move migration hints to getting started page
These are relevant for all installation methods, so they should be placed at a 'global' place. Signed-off-by: David Mehren <git@herrmehren.de>
This commit is contained in:
parent
2667b642f4
commit
a3ee2c6f8c
2 changed files with 13 additions and 17 deletions
|
@ -19,3 +19,13 @@ You can find more details about upgrading in the instructions of your installati
|
|||
!!! warning
|
||||
Before you upgrade, **always read the release notes**.
|
||||
You can find them on our [releases page](https://hedgedoc.org/releases/).
|
||||
|
||||
## Migrating from CodiMD & HackMD
|
||||
Migrating from CodiMD <= 1.6.0 or HackMD <= 1.1.0 to HedgeDoc should be safe,
|
||||
just make sure to read the release notes.
|
||||
A particular issue that has come up is when handling TLS connections using a reverse proxy.
|
||||
You must [set the `X-Forwarded-Proto` header correctly](https://docs.hedgedoc.org/guides/reverse-proxy/#reverse-proxy-config).
|
||||
|
||||
Migrating from more recent versions of CodiMD is not guaranteed to work, although some community members
|
||||
[reported success migrating from CodiMD 2.2](https://community.hedgedoc.org/t/solved-upgrade-from-dockerlized-codimd/271).
|
||||
If you successfully migrated from other versions, please report your upgrade results in the [community forum](https://community.hedgedoc.org/).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue