Repository navigation
Prevent Same name to be ported using 'as' command #6
Description
ported using same name on same port
Results
No issues on browsing..
Ported Using different name on same port
Results
- No issues on browsing
- Both Service is running
So Main issue is, when stopping on service which is same name on same port will halt current active service
** Left ** and ** Right ** terminal is activated as same name. But Closing Right Terminal request prevent to browse which is valid but showing active on left is not valid.
Activity
thebinary commentedon Aug 17, 2020
Actually the newer command run (with same service name) always replaces the older service endpoint. Older local service does not recieve any further requests.
There are 2 possible options I currently see to resolve service name conflict:
I see option 2 to be a better option but I want to give this a bit more thought before implementing. Till then I will keep this issue open.
And this project is open for suggestions too 🙂