Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/prodyna/go-training-service
Go Services for everyone :-)
https://github.com/prodyna/go-training-service
Last synced: about 1 month ago
JSON representation
Go Services for everyone :-)
- Host: GitHub
- URL: https://github.com/prodyna/go-training-service
- Owner: PRODYNA
- License: mit
- Created: 2021-11-09T17:27:02.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2023-06-21T20:33:37.000Z (over 1 year ago)
- Last Synced: 2024-11-30T20:23:20.416Z (about 1 month ago)
- Language: Go
- Size: 6.08 MB
- Stars: 3
- Watchers: 13
- Forks: 2
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Go Training Service
## Purpose
The purpose of this project is to allow participants of the Go training sessions to have a hands-on experience, developing and
deploying a simple Go service.## Usage
Using this project to develop and deploy a small Go service is quite simple and straightforward. To create and deploy a
new service simply follow the steps outlined below:### Code preparation
1. Start by creating a branch from `main`. **Make sure that your branch adheres to this naming convention `team/`**.
For example, a valid branch name is `team/dkrizic`.
2. Copy all the contents of the `src/template/` folder in a new folder named `/src/`. **Make sure that the
username defined in the branch name is the same as the name of your folder.**
3. Rename all occurrences of `template` within the copied code to match your **username**.
4. Do all the necessary code changes to your Go code.### Pull Requests
1. Once all the code changes are done, you can go ahead and open up a pull-request targeting the `main` branch.
2. Opening up a pull request will trigger a CI run for your code. This will build your code and verify its integrity.
3. You can perform any number of commits whilst the PR is open, each triggering a new CI run.### Merging
1. Upon finalizing your code changes and given that the newly added code gets built properly, you can go ahead and merge to `main`.
2. :warning: **Make sure that you do not tamper with GitHub's default commit message as it contains the branch name**. The latter is
required for the retrieving deployment related information. If a custom message must be provided, please make sure to include
the branch name in lowercase.
3. After merging the changes and once the CI is finished, you can verify the liveliness of your service by visiting the following
link `.20.71.73.61.nip.io`