-
Notifications
You must be signed in to change notification settings - Fork 100
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
Customise Windows service name: omero.windows.servicename #3122
Conversation
OMEROmerge.master on Hake, from trout/merge: |
OMERO.master on Hake, from trout/merge:
|
Interestingly, the CLI told me:
Which is wrong, since you can clearly see in my previous comment it definitely connected to 14064.. :/ Other than that, 👍 🐟 |
Do you remember if you did |
In general, the problem is that the port of the previous session is saved in the session file itself (and not aliased list last host and last user), so if the session file is removed, there is no way to remember which port was used. A workaround may be to detect this case and not specify the port for the last connection if it cannot be read. |
Alternatively, to add the port to the host name on disk? |
As in an additional subfolder? |
that or, say, everything after a comma: |
Yes that would likely minimize the impact on the sessions logic (default to |
Customise Windows service name: omero.windows.servicename
--no-rebase |
This is needed to allow multiple server deployments on the same Windows system.
This is currently deployed as a merge-deploy on Hake (OMERO-5.1-merge-deploy-win, port 4064, servicename: OMEROmerge) alongside latest-deploy (OMERO-5.1-latest-deploy-win, port 14064, default servicename since PR isn't merged). Note multiple web/IIS isn't working for other reasons so ignore web for now.
Test locally on your own VM if you're feeling brave.