| 17 Jul 2024 |
 @wst:imagisphe.re | There's no rush. I will be happy to accept any help. | 21:38:51 |
 Cobalt | So, afaict, this repo contains three node components. A web ui, a server for the corresponding backend and an electron app. The web ui and server can be used separately (see Dockerfile) and the electron app wraps the logic from the other components. You are currently trying to package the electron app. Does that sound about right? | 21:47:44 |
| Cobalt | To build the electron app, you require a compiled version of the frontend. | 21:48:54 |
| Cobalt | And the compiled frontend + docs needs to be copied into the electron source in copy:assets. | 21:51:33 |
| @wst:imagisphe.re | Yep, that's what I'm trying to do. | 21:56:41 |
| Cobalt | So my first guess would be to
- build the frontend and then
- build the electron app
in separate derivations. For 2. you would have to replicate the logic from copy:assets in the preBuild/ patchPhase phase using the compiled output from 1.
| 21:53:49 |
| @wst:imagisphe.re | I wonder if the "frontend" can just be wrapped with electron by some nixpkgs function. As far as I understand electron just renders the frontend, so I don't have to build electron from their repo | 22:01:47 |
| Cobalt | * So my first guess would be to
- build the frontend and then
- build the electron app
in separate derivations. For 2. you would have to replicate the logic from copy:assets in the preBuild/ patchPhase phase using the compiled output from 1.
| 21:54:17 |
