Requirements
- .NET SDK 10 installed locally
- Account on Vertra Cloud
- An ASP.NET Core or console project with a
.csproj
Project Structure
.csproj, .fsproj, .sln or global.json at the root of the project. It publishes the project in Release mode with dotnet publish and starts the result.
Configuration
MyServer.csproj
vertracloud.config
MAIN is the .csproj file.
Example: Minimal API
ASPNETCORE_HTTP_PORTS. The platform already sets it to 80, so you don’t need to configure the port in code or with extra settings.
Deploy
- Dashboard
- CLI
- VS Code
- Compress the project into a
.zipor push it to GitHub. - In the dashboard, click New Project and upload the
.zipor paste the repository URL. - In Build, check the runtime (.NET), the main file (
MyServer.csproj) and the memory. Start and build commands are under Advanced settings. - Add your environment variables in Environment.
- In Network, turn on web publishing so the app gets a
*.vertraweb.appaddress (Pro plan or higher, 512 MB of memory). The app must listen on port 80. - Review and deploy. Follow the output in the Logs tab.
Available Versions
Notes
- Build: the project is published with
dotnet publishin Release mode during deployment, so the first deploy can take a few minutes. Give the build enough memory - Exclude from the zip:
binandobjfolders - Environment variables: read them with
Environment.GetEnvironmentVariable("KEY")or throughbuilder.Configuration - Logging: use
ILoggerorConsole.WriteLine()for logs that appear in real time - Keep
TargetFrameworkatnet10.0
Common Errors
- Project file not found:
MAINmust point to the.csproj, relative to the root of the zip. - Site doesn’t open: the app must listen on the port in
ASPNETCORE_HTTP_PORTS(80). Remove any port you hardcoded in code, so the app followsASPNETCORE_HTTP_PORTS. - Build runs out of memory: raise the application’s memory and deploy again. See Common Errors.