# Functions
🔑 RouteAuthPublic can be accessed by anyone.
Gets the GRPC Method from the context and the Route from that Method.
Our Routes are named by the last part of their GRPC Method.
As on the init func we load the .env file, in here we already have available all of the env vars.
No description provided by the author
No description provided by the author
No description provided by the author
# Constants
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
# Variables
Gorm Levels go from silent (lowest) to info (highest), as opposed to our Logger Levels.
No description provided by the author
No description provided by the author
Levels go from debug (lowest) to fatal (highest).
Map of routes.
# Structs
No description provided by the author
No description provided by the author
⭐️ Our App holds a reference to one of this, which contains all the config values to be passed from the App to the different services and tools.
No description provided by the author
🌍 Global Configs.
No description provided by the author
These are the claims that live encrypted on our JWT Tokens.
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
Routes are the representation of a single endpoint, and it holds all the things that both versions of said endpoint should share.
For TLSEnabled, see [Globals].
# Interfaces
No description provided by the author
No description provided by the author
With this you can avoid importing the tools pkg.
No description provided by the author
With this you can avoid importing the tools pkg.
No description provided by the author
No description provided by the author
No description provided by the author
With this you can avoid importing the tools pkg.
No description provided by the author
No description provided by the author
This isn't used like the other tools, as it's instantiated per request.
With this you can avoid importing the tools pkg.
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
With this you can avoid importing the tools pkg.
With this you can avoid importing the tools pkg.
All Protobuf requests with a userID on the URL should implement this.
With this you can avoid importing the tools pkg.
With this you can avoid importing the tools pkg.
No description provided by the author
With this you can avoid importing the tools pkg.
With this you can avoid importing the tools pkg.
Each service is defined in a .proto file.
With this you can avoid importing the tools pkg.
No description provided by the author
With this you can avoid importing the tools pkg.
With this you can avoid importing the tools pkg.
With this you can avoid importing the tools pkg.
These are the interfaces to all of our tools.
No description provided by the author
No description provided by the author
# Type aliases
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author