| 17 Jul 2024 |
 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 |
| @wst:imagisphe.re | But I'm getting ahead of myself | 22:01:55 |
| @wst:imagisphe.re | I see | 22:03:44 |
| @wst:imagisphe.re | So the frontend part lives in joi as far as I understood | 22:05:06 |
| Cobalt | I'm not too sure about that. You would likely lose some functionlaity. Their electron app is a bit more than a simple wrapper and also, e.g., offers tray support and appears to be doing some fancy stuff to make it appear more native-sh. | 22:05:05 |
| @wst:imagisphe.re | To build it I would need to run first pull the dependencies in advance, since there's no network while building derivation | 22:06:20 |
| Cobalt | Redacted or Malformed Event | 22:05:20 |
