Licensed under the Apache License, Version 2.0; you may not use this app except in compliance with the License. You may obtain a copy of the License at https://opensource.org/licenses/Apache-2.0.
Important
Potential legal non-compliance (This is not legal advice).
This software is currently under development and may not yet comply with all legal requirements and specific laws, like GDPR. There may be potential risks associated with using the software in its current state.
Server used by the company "Gislaine Studio" in Andradina-SP, Brazil.
Warning
Guidelines for copyright and trademarks
This project may contain trademarks or logos for projects, products, or services.
The images included in this repository are not part of the open-source license and cannot be freely used or modified without explicit permission. These images are protected by copyright and are provided solely for reference purposes within the context of this project.
Individuals are not authorized to use these images (bitmap and vector) for any purpose without obtaining explicit permission from the copyright holder. Modifying these images is strictly prohibited without prior consent from the copyright holder. Permission is required for any commercial or non-commercial use of the images, including but no limited to advertising, marketing, or product development.
By accessing or using the images in this repository, you agree to abide by these usage guidelines and respect the intellectual property rights associated with the images.
Trademarks are names and designs that tell the world the source of a good or service. Protecting trademarks for an open source project is particularly important. Anyone can change the source code and produce a product from that code, so it’s important that only the original product, or variations that have been approved by the project, use the project’s trademarks. Trademarks cannot be used in ways that appear (to a casual observer) official, affiliated, or endorsed by the original project.
TL;DR: Use of trademarks or logos in modified versions of this project must not cause confusion or imply sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
- Official website - Official documentation, libraries, resources, samples and FAQ.
- Technical documentation - Collection of useful technical documentation.
- gRPC status codes - Status codes and their use in gRPC.
- gRPC status code mapping - HTTP to gRPC Status Code Mapping.
- grpc-errors - Code examples in each language on how to return and handle error statuses.
- API Design Guide - Google Cloud API Design Guide useful for gRPC API design insights.
- Overview for gRPC on .NET - C# Tooling support for
.protofiles. - gRPC services with C# - This document outlines the concepts needed to write gRPC apps in C#. The topics covered here apply to both C-core-based and ASP.NET Core-based gRPC apps.
To get started, I recommend you to have the following tools installed:
- I recommend installing the latest version of Visual Studio Code.
- I use the extension C# for Visual Studio Code.
- My VS Code setup is available in NatanAmorim/my-config at vscode_config.md.
For .NET development, install .NET Core SDK I used the .NET SDK 8.0 for this project.
- installation on Mac
- installation on Linux
- installation on Windows (I recommend to use Windows Subsystem for Linux 2)
docker pull postgresdocker run --name postgresql -e POSTGRES_PASSWORD=<password> -p 5432:5432 -d postgres
The following instructions are for dotnet-cli that comes with the .NET Core SDK:
dotnet restore
dotnet build- If you want to contribute code to this repository check CONTRIBUTING.md.
If you believe you have found a security vulnerability in this software, we encourage you to inform us immediately. We will investigate all legitimate reports and do our best to quickly correct the issue.
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
This information will help us triage your report more quickly.