You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ MoonLight functionality is aimed at running effects on multiple lights. It's pri
15
15
16
16
MoonLight is a [MoonModules.org](https://moonmodules.org) project. MoonModules is a group of lighting enthusiasts who also made WLED MM and contribute to WLED. Where WLED (MM) is aimed at 1D and 2D effects and LED setups, MoonLight is build to support 2D and 3D effects and multiple light setups. MoonLight has been built from scratch using the experience gained working on WLED (MM).
17
17
18
-
* Latest release can be found [here](https://github.com/MoonModules/MoonLight/releases). Release v0.5.8 is a developer release and works towards MoonLight 0.6.0 which is aimed at end users and is expected in September 2025. Containing presets controller pad, user friendly installer, physical and virtual driver for large displays, WLED audio sync and more.
18
+
* Latest release can be found [here](https://github.com/MoonModules/MoonLight/releases). Release v0.5.9 is a developer release and works towards MoonLight 0.6.0 which is aimed at end users and is expected in September 2025. Containing presets controller pad, user friendly installer, physical and virtual driver for large displays, WLED audio sync and more.
19
19
* Progress can be tracked in the [Kanban board](https://github.com/users/MoonModules/projects/2/)
20
20
* Get started [here](https://moonmodules.org/MoonLight/gettingstarted/overview/)
21
21
* Follow us on [Discord/MoonLight](https://discord.gg/TC8NSUSCdV) or [Reddit](https://reddit.com/r/moonmodules).
|18 LED Bars|<imgwidth="300"src="https://github.com/user-attachments/assets/75b18cf6-bc32-4bf0-a03b-7eea8dbfd677" />|[Shop](https://s.click.aliexpress.com/e/_EQMKbmK)|
Copy file name to clipboardExpand all lines: docs/statefulservice.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -601,7 +601,7 @@ By enabling `FT_DOWNLOAD_FIRMWARE=1` in [features.ini](https://github.com/theeli
601
601
```ini
602
602
-D BUILD_TARGET="$PIOENV"
603
603
-D APP_NAME=\"ESP32-Sveltekit\" ; Must only contain characters from [a-zA-Z0-9-_] as this is converted into a filename
604
-
-D APP_VERSION=\"0.5.8\" ; semver compatible version string
604
+
-D APP_VERSION=\"0.5.9\" ; semver compatible version string
605
605
```
606
606
607
607
A build script copies the firmware binary files for all build environment to `build/firmware`. It renames them into `{APP_NAME}_{$PIOENV}_{APP_VERSION}.bin`. It also creates a MD5 checksum file for verification during the OTA process. These files can be used as attachment on the GitHub release pages.
Copy file name to clipboardExpand all lines: docs/structure.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ Also you must make use of couple build flags in [platformio.ini](https://github.
98
98
```ini
99
99
-D BUILD_TARGET=\"$PIOENV\"
100
100
-D APP_NAME=\"ESP32-Sveltekit\"; Must only contain characters from [a-zA-Z0-9-_] as this is converted into a filename
101
-
-D APP_VERSION=\"0.5.8\"; semver compatible version string
101
+
-D APP_VERSION=\"0.5.9\"; semver compatible version string
102
102
```
103
103
104
104
Out of these flags the [rename_fw.py](https://github.com/theelims/ESP32-sveltekit/blob/main/scripts/rename_fw.py) script will copy and rename the firmware binary to `/build/firmware/{APP_NAME}_{$PIOENV}_{APP_VERSION}.bin`. In addition it will also create a corresponding MD5 checksum file. These files are ready to be uploaded to the Github release page without any further changes. The frontend searches for the firmware binary which matches the build environment and uses this as the update link. This allows you to serve different build targets (e.g. different boards) from the same release page.
0 commit comments