How to access your .NET application
Private internal access​
Projects in Zerops represent a group of one or more services. Services can be of different types (runtime services, databases, message brokers, object storage, etc.). All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its internal port.
To connect to your application with app hostname running on internal port 5000, simply use http://app:5000
Do not use https:// when communicating with .NET from other runtime services in the same project. The internal communication is done over a private network and is isolated from other projects.
Use .NET environment variables​
Zerops creates default environment variables for each .NET service to help you with connection within the same project. To avoid the need to copy the access parameters manually, use generated environment variables of the .NET service.
Prefix the environment variable key​
All services of the same project can reference environment variables from other services. To use an environment variable from one service in another service in the same project, you must prefix the environment variable key with the service hostname and underscore.
Example:​
To access the API_TOKEN env variable of the app service, use app_API_TOKEN as the env variable key.
Read more about env variables.
Private access via VPN​
Start VPN connection​
You can securely connect to your .NET application from your local workspace via Zerops VPN. Zerops VPN client is included into zCLI, the Zerops command-line tool. To start a VPN connection to the selected Zerops project, follow these steps:
Access .NET application through VPN​
Once the VPN session is established, you have the secured connection to the project's private network in Zerops. You can access all project services locally by using their hostname. The only difference is that no environment variables are available when connected through VPN. To connect to your .NET application in Zerops set the hostname and internal port e.g. http://app:5000
Do not use https:// when communicating with .NET over the VPN. The security is assured by the VPN. The internal communication is done over a private network and is isolated from other projects.
Connect via SSH​
Use the ssh command to connect to your service via SSH.
Stop VPN connection​
Stop the Zerops VPN in zCLI.
Public access through zerops.io subdomain​
By default, your .NET service is not publicly accessible. To test your application, enable the public access through zerops.io subdomain.
Public access through your domain​
By default, your .NET service is not publicly accessible. When your application is ready for production or if you want to test it on the production domain, configure the public access through your domain.
Public access from another Zerops project​
All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its internal port. Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either through zerops.io subdomain or through your domain.