blade/materialious
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add support for @username urls

Browse Source
This commit is contained in:
WardPearce
2024-10-30 00:29:54 +13:00
parent 0d6a77c235
commit 8b9cd8f1cf
5 changed files with 31 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/BUILDING.md
+1 -5
View File
@@ -19,11 +19,7 @@ Materialious desktop builds are handled through GitHub using [prod-desktop.yml](
- From here, the process follows standard [electron-builder](https://www.electron.build/) steps to complete the build.
### Desktop Release (via Flatpak)
Flatpak builds for desktop releases are managed via [us.materailio.app](../flatpak/us.materialio.app.json).
- We generate the necessary remote npm packages with `flatpak-node-generator npm -r ../materialious/package-lock.json -R ../materialious/electron/package-lock.json`, which creates [generated-sources.json](../flatpak/generated-sources.json).
- The Linux x64 runtime is downloaded as part of the Flatpak build sources and placed in `main/materialious/electron/.electron-cache`. The [electron-builder.config.json](../materialious/electron/electron-builder.config.json) is configured to use this cache directory to avoid downloading the runtime again during the build.
- The build process is similar to [prod-desktop.yml](../.github/workflows/prod-desktop.yml), following the guidelines for [Flatpak Electron](https://docs.flatpak.org/en/latest/electron.html).
TODO
### Android Release
Android builds are handled using the workflow [prod-android.yml](../.github/workflows/prod-android.yml).