Idea ID: 2877317

Use Application Name instead of Port from VTS

Status: Accepted

Backlog item for a future release.

See status update history

Currently, we're using port numbers to identify and route traffic to our various applications. While this approach has served us well, it can become cumbersome to manage, especially as we scale and add more services.

To address this, I suggest that we transition from using port numbers to using application names as identifiers. Instead of specifying port numbers, we can use clear and intuitive application names to access our services. This change not only streamlines our configuration but also makes it easier for team members to work with our services.

Here's how it would work:

  • Each application will have a unique name.
  • We'll maintain a mapping of these application names to their corresponding ports and internal service addresses.
  • Nginx, our web server, will be configured to route traffic to the appropriate service based on the provided application name.

This transition will simplify our server configuration and improve the accessibility of our services, making it easier for team members to interact with different applications.

Tags:

  • Hello guys
    This is a very valid enhancement.
    We see two ways to implement this capability.

    1. The VTS server should work in the Nginx (port forwarding) way.
      This method would still ensure that you the customer would still be required to do the Application-PortNumber mapping in the Reverse Proxy, and of cause, replace the port number with application name in all the scripts.
    2. An alternative is to keep the server intact as it is , and you can run the server in either the normal or the Nginx way. We could look to provide a new VTS connection API (or update the current one) and what you would need to do is to provide the mapping file and replace the port number with application name in all the scripts.

     So having discussed this with the team we have decided to accept option 1 and have added a code change feature into our backlog for a future release.
    Thanks David

     

  • Hi Pavan,

    With VTS we have two kinds of access. It looks like you are referring to the UI access.Your idea will be convenient. Creating a VTS instance requires to give an instance name, so this name might be serve as argument to your app parameter.

    For the API access the port number is mandatory, because the API connects directly to this port on the give server. This gives the most scalability in VTS. The API is very lightweight and fast. To me that is an very important aspect.

    Regards, Erik

    How to ask questions

    Reward contributions via likes or 'verified answers'

  • Thanks for quick response Remmelzwaal.

    I understand this cannot be extended. But i am looking a solution from nginx by using map method.

    For ex. my server is "Server=">">https://server" and another port would be "Server=">">https://server/port=1234", from this i want to use something like "Server=">">https://server/app=xyz".

    Also while starting new instance from VTS Name and Port is the mandatory fields, but why can't we use instance name instead of port to access VTS.

    If this can be done this would be great feature i guess.

  • ,

    In the example on this page, you can specify "Server=">https://server". Unfortunate this cannot be extended to "Server=">https://server/VTS/APP1" This would be good enough to resolve your issue with help of Nginx. I would also like this to be available, because we hide out AWS VTS instances behind a nginx proxy, so API access is not possible.

    Suggestion:

    We maintain on the main page of VTS instances ( port 8888) an admin page were per project a row contains: name / port / URL / contact person / comments.

    You might write a small function that encapsulates the lrvtc_connect(_ex) function. This function just uses the project name and this function takes care to make the right connection. You hide the port numbers from the scripts in this way.

    How to ask questions

    Reward contributions via likes or 'verified answers'