-
-
Notifications
You must be signed in to change notification settings - Fork 734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configurable Default Electron Port #504
Comments
You need an additional configuration in the electron.manifest.json file with the key aspCoreBackendPort:
The application then runs automatically as a single instance. I hope you like it that way. |
I have the aspCoreBackendPort accounted for. I need the electronPort changed from its default of 8000 and then searching for whatever is available if 8000 is taken. Ultimately I need the electron port to behave exactly like what was already done with aspCoreBackendPort. Thanks for the quick reply! |
Thanks for putting it on a milestone. I have a local branch. I don’t think I have permission to push. Are there any other steps to implementing this other than what I have above? Also how can I workaround this for now? |
In this video I show, how you can work with the repository: Your pull request is very welcome to us :) |
I put in the PR. Let me know if it is wrong. |
I'd love to see this get In ASAP. Low risk, big impact. Thanks guys! |
@skarin At the moment I'm still a bit busy - I don't think I'll have time for Electron until December - but a lot will happen that really rocks! |
Is there some guidance on the electron.manifest.json “files” section? I think I can work around this problem by making my own main.js but I can’t find any docs on how it works and copying an example ElectronHostHook does seem to overwrite the main.js. |
So is there a way to set a default electron port in 23.6.1? |
|
In many environments developers are not permitted to find available port. We must use specified ports allotted. Can we change the main.js file to include the following (~ line 66):
This will allow users to explicitly set the port just as you can do with the aspNetCore port.
The text was updated successfully, but these errors were encountered: