docs: update user_changes with octoprint_compat requirement
Signed-off-by: Eric Callahan <arksine.code@gmail.com>
This commit is contained in:
parent
6ba45f6e35
commit
84f663e2bc
|
@ -18,7 +18,7 @@ to see if any action is necessary on their part. The date of the most
|
||||||
recent change is included.
|
recent change is included.
|
||||||
|
|
||||||
Users:\
|
Users:\
|
||||||
[user_changes.md](/docs/user_changes.md) - December 31st 2020
|
[user_changes.md](/docs/user_changes.md) - March 4th 2021
|
||||||
|
|
||||||
Developers:\
|
Developers:\
|
||||||
[api_changes.md](/docs/api_changes.md) - January 31st 2021
|
[api_changes.md](/docs/api_changes.md) - January 31st 2021
|
||||||
|
|
|
@ -1,5 +1,8 @@
|
||||||
This file will track changes that require user intervention,
|
This file will track changes that require user intervention,
|
||||||
such as a configuration change or a reinstallation.
|
such as a configuration change or a reinstallation.
|
||||||
|
### March 4th 2021
|
||||||
|
- To enable Octoprint compatibility with slicer uploads it is now
|
||||||
|
required to add `[octoprint_compat]` to `moonraker.conf`.
|
||||||
|
|
||||||
### December 31st 2020
|
### December 31st 2020
|
||||||
- The file manager no longer restricts the `config_path` to a folder
|
- The file manager no longer restricts the `config_path` to a folder
|
||||||
|
|
Loading…
Reference in New Issue