Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/sah4ez/gosvm
gosvm is a tool for managing dependencies of services in microservices architecture approach.
https://github.com/sah4ez/gosvm
dependency-manager glide golang gomod microservices
Last synced: 8 days ago
JSON representation
gosvm is a tool for managing dependencies of services in microservices architecture approach.
- Host: GitHub
- URL: https://github.com/sah4ez/gosvm
- Owner: sah4ez
- License: mit
- Created: 2018-02-24T17:04:31.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2019-04-08T16:01:05.000Z (over 5 years ago)
- Last Synced: 2024-06-20T00:39:23.323Z (5 months ago)
- Topics: dependency-manager, glide, golang, gomod, microservices
- Language: Go
- Homepage:
- Size: 6.25 MB
- Stars: 3
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# gosvm
Golang services version manager
# Install
For install on Linux run:
```bash
sudo wget https://github.com/sah4ez/gosvm/releases/download/v0.0.13/gosvm-v0.0.13-linux-amd64 -O /usr/local/bin/gosvm
sudo chmod +x /usr/local/bin/gosvm
```
For install on OS X run:
```bash
sudo wget https://github.com/sah4ez/gosvm/releases/download/v0.0.13/gosvm-v0.0.13-darwin-amd64 -O /usr/local/bin/gosvm
sudo chmod +x /usr/local/bin/gosvm
```
# Background
For development many services, each can used common packages, example: logger, DB driver, data model and etc.
Each service using own repository and vendoring (dep, glide or go.mod)
gosvm provide tool for version management for several repositoreis
Example:
``` bash
$ pwd
/go/src/github.com/sah4ez/
$ ls -lah
drwxr-xr-x 2 sah4ez sah4ez 64B 27 feb 21:45 events
drwxr-xr-x 2 sah4ez sah4ez 64B 27 feb 21:45 logger-wrap
drwxr-xr-x 2 sah4ez sah4ez 64B 27 feb 21:45 models
drwxr-xr-x 2 sah4ez sah4ez 64B 27 feb 21:45 mongo
drwxr-xr-x 2 sah4ez sah4ez 64B 27 feb 21:45 processor
drwxr-xr-x 2 sah4ez sah4ez 64B 27 feb 21:45 scheduler
```
We have the project structure:
- events - event implement package for send between sevices or server-client
- logger-warp - wrapper for logger implement own format/logic
- mongo - wrapper for MongoDB driver
- models - data model for persist document to MongoDB
- processor - simple service which process input events and persist to MongoDB
- schdeudler - to execute deferred events
And we can simple describe all structure in `svm.toml` and version manage or update it for all services. Examlpe:
```toml
Title = "exmaple-project"
Description = "Example project with library and services"
Version = "1.0.0"
BasePath = "github.com/sah4ez"
[[SubProject]]
Title = "events"
Description = "package implement event for send between sevices or server-client"
Version = "1.1.0"
[[SubProject]]
Title = "logger-warp"
Description = "wrapper for logger implement own format/logic"
Version = "0.2.1"
[[SubProject]]
Title = "mongo"
Description = "wrapper for MongoDB driver"
Version = "0.2.1"
[[SubProject]]
Title = "models"
Description = "structure of models for persist document to MongoDB"
Version = "0.2.1"
[[SubProject]]
Title = "processor"
Description = "simple service which process input events and store to MongoDB"
Version = "0.2.1"
[[SubProject]]
Title = "schdeudler"
Description = "execute deferred events"
Version = "0.2.1"
[[Library]]
Title = "library"
Description = "some utilites library"
Version = "0.2.1"
```
# Commands
| name | description |
|-----:|-------------|
| list | formatted output svm.toml |
| libs | analyse of packages usage in all packages and formatted output |
| version | print current version, revision number and date build |
| clone | clone repositories if not exists in basePath |
| pull | pull last changes from remote repos |
| doc | generate spec for all project from svm.toml file of each repository |
| generate | generate template spec for SubProject in automationMode or custom |
| set | (plan) set version for all or specifict packages (implemented for glide) |
| get | (plan) get specific package version or all version package usage for specifict package |
| update | (plan) update vendor or v and .lock and commit changes |
| revert | (plan) revert commit from gosvm |
| ... | you can contribute your ideas here or issues... |
Example commands:
```bash
$ ls
svm.toml
$ gosvm list
Title: exmaple-project
Description: Example project with library and services
Version: 1.0.0
SubPackages:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
$ gosvm libs
Title: exmaple-project
Description: Example project with library and services
Version: 1.0.0
====================Libs====================
github.com/sah4ez/events
!!!2 differnt vesrion are used!!!
^1.2.0 :
processor
^1.2.2 :
scheduler
github.com/sah4ez/logger-wrap
!!!4 differnt vesrion are used!!!
^1.0.0 :
events
^1.3.0 :
models
^3.2.0 :
processor
^4.2.1 :
scheduler
github.com/sah4ez/models
!!!2 differnt vesrion are used!!!
^1.0.0 :
processor
^1.2.1 :
scheduler
github.com/sah4ez/mongo
!!!3 differnt vesrion are used!!!
^2.3.1 :
scheduler
^2.3.0 :
models
^2.2.0 :
processor
github.com/sirupsen/logrus
master :
logger-wrap
```
# Known troubles
Cloning via public key not work. Using `ssh-add` and `ssh-agent`.
# dependecy manager
Supported:
- dep
- glide
- go.mod