install-moonraker: allow configurable virtualenv location
Signed-off-by: Franklyn Tackitt <git@frank.af>
This commit is contained in:
parent
7cd29c068d
commit
16327ff551
|
@ -136,6 +136,16 @@ particularly for those upgrading:
|
||||||
This is useful for installations that occur outside of a standard environment
|
This is useful for installations that occur outside of a standard environment
|
||||||
where systemd is not running.
|
where systemd is not running.
|
||||||
|
|
||||||
|
Additionally, installation may be customized with the following environment
|
||||||
|
variables:
|
||||||
|
|
||||||
|
- `MOONRAKER_VENV`
|
||||||
|
- `MOONRAKER_REBUILD_ENV`
|
||||||
|
- `MOONRAKER_FORCE_DEFAULTS`
|
||||||
|
- `MOONRAKER_DISABLE_SYSTEMCTL`
|
||||||
|
- `MOONRAKER_CONFIG_PATH`
|
||||||
|
- `MOONRAKER_LOG_PATH`
|
||||||
|
|
||||||
When the script completes it should start both Moonraker and Klipper. In
|
When the script completes it should start both Moonraker and Klipper. In
|
||||||
`/tmp/klippy.log` you should find the following entry:
|
`/tmp/klippy.log` you should find the following entry:
|
||||||
|
|
||||||
|
|
|
@ -2,13 +2,13 @@
|
||||||
# This script installs Moonraker on a Raspberry Pi machine running
|
# This script installs Moonraker on a Raspberry Pi machine running
|
||||||
# Raspbian/Raspberry Pi OS based distributions.
|
# Raspbian/Raspberry Pi OS based distributions.
|
||||||
|
|
||||||
PYTHONDIR="${HOME}/moonraker-env"
|
PYTHONDIR="${MOONRAKER_VENV:-${HOME}/moonraker-env}"
|
||||||
SYSTEMDDIR="/etc/systemd/system"
|
SYSTEMDDIR="/etc/systemd/system"
|
||||||
REBUILD_ENV="n"
|
REBUILD_ENV="${MOONRAKER_REBUILD_ENV:-n}"
|
||||||
FORCE_DEFAULTS="n"
|
FORCE_DEFAULTS="${MOONRAKER_FORCE_DEFAULTS:-n}"
|
||||||
DISABLE_SYSTEMCTL="n"
|
DISABLE_SYSTEMCTL="${MOONRAKER_DISABLE_SYSTEMCTL:-n}"
|
||||||
CONFIG_PATH="${HOME}/moonraker.conf"
|
CONFIG_PATH="${MOONRAKER_CONFIG_PATH:-${HOME}/moonraker.conf}"
|
||||||
LOG_PATH="/tmp/moonraker.log"
|
LOG_PATH="${MOONRAKER_LOG_PATH:-/tmp/moonraker.log}"
|
||||||
|
|
||||||
# Step 2: Clean up legacy installation
|
# Step 2: Clean up legacy installation
|
||||||
cleanup_legacy() {
|
cleanup_legacy() {
|
||||||
|
|
Loading…
Reference in New Issue