Terranaut Api Gateway
  • C# 66.1%
  • Dockerfile 33.9%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
njooris e5b5d2f0ce Merge pull request 'feat: notification' (#9) from feature/notification into master
Reviewed-on: #9
Reviewed-by: njooris <njooris@student.42lyon.fr>
2026-11-09 10:48:02 +00:00
.devcontainer feat: Added game & signalR support via new CORS policy 2026-10-02 11:06:59 +02:00
Properties feat: WIP ApiGateway 2026-09-23 19:31:22 +02:00
.env.example Initial commit 2026-09-22 11:37:43 +00:00
.gitignore Initial commit 2026-09-22 11:37:43 +00:00
ApiGateway.csproj feat: WIP ApiGateway 2026-09-23 19:31:22 +02:00
appsettings.Development.json feat: notification 2026-11-02 17:35:21 +01:00
appsettings.json feat: notification 2026-11-02 17:35:21 +01:00
Dockerfile feat: WIP ApiGateway 2026-09-23 19:31:22 +02:00
Program.cs feat: now forward ips 2026-10-20 15:39:40 +02:00
README.md Initial commit 2026-09-22 11:37:43 +00:00

/!\ You just created a new repo from this template :

This is a basic template for any new aspnet microservice in the terranaut project.

Before you start coding there is a few things you need to do :

.env.example

Copy the .env.example file to a .env file.

.devcontainer/compose.yml

To ensure proper functionability of the provided development envrionnement, you need to make sure the other runnig services will be able to see and connect to the dev container :

To do so, change the name of the service (here service_serv) to the exact same name of the service in the compose.yml in the main repo.

This will allow docker DNS resolution to work properly. Other running services that need to connect to this one (mainly the mesage broker and API gateway), won't be aware of the difference between the normal container and the dev container.

If you need to connect your dev container to other service than the message broker :

Feel free to add an external docker network to .devcontainer/compose.yml

nuget.config.example

Rename nuget.config.example to nuget.config. It should stay git ignored since it can contain your forgejo credentials.

Authentication

If your micro service will need Authentication run the following commands to download our Asymmetric Authentication package :

dotnet nuget add source --name Terranaut --username your_username --password your_token --store-password-in-clear-text https://forgejo.asventi.net/api/packages/Terranaut/nuget/index.json
dotnet add package --version 1.0.1 Terranaut.AsymmetricAuthentication

(this README isn't automatically updated so check the last package version).

service.csproj

If you want to rename your service, just change the name of service.csproj to {your_service}.csproj