Replies: 2 comments
-
|
Looking for the same! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The installer setup is entirely a part of Electron Builder and the recommended default is nsis. Everything that is available via electron-build can be used in the build script, but not everything is (or needs to be) exposed via PHP config. But if there's anything there that you feel is especially valuable to make configurable, please create a PR 🙏🏼 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
Thank you for the work on NativePHP and the Laravel ecosystem.
I wanted to ask if it is possible (or if there are recommended approaches) to use a custom installer for the executable generated by NativePHP. For example, using Inno Setup, NSIS, or a custom shell installer to package the generated executable along with additional assets, registry keys, or environment configurations before distribution to end users.
Is there a recommended way to hook into the build process for this purpose?
Are there caveats when wrapping the NativePHP executable in a third-party installer?
Would such an approach affect updates or the NativePHP runtime in any way?
If this is not currently documented, I would be happy to help document it once clarified.
Thank you for your guidance.
Beta Was this translation helpful? Give feedback.
All reactions