cyclops-community
/
cyclops-4-hpc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Cyclops 4 HPC is the purpose built stack to support large HPC centers with resource accounting and billing of cluster as well as cloud resources.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4 Commits
2 Branches
0 Tags
4.2 MiB
 
 
Tag: Branch: Tree: main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
cyclops-4-hpc/extensions/lexis
History
Diego Martin 0ea0435502
[U] Sync of latest codebase 		3 years ago
..
client [0] Initial code release 3 years ago
models [0] Initial code release 3 years ago
restapi [0] Initial code release 3 years ago
run [0] Initial code release 3 years ago
server [0] Initial code release 3 years ago
README.md [0] Initial code release 3 years ago
go.mod [U] Sync of latest codebase 3 years ago
planManagerLoader.sh [U] Sync of latest codebase 3 years ago
swagger.yaml [0] Initial code release 3 years ago

README.md

LEXIS EXTENSIONs SERVICE

Cyclops Engine's Extension Service for LEXIS implemented in Go

How to build

The building of the service is carried by a multistage docker build, we build everything in an image containing everything needed to build Golang applications and then the executable is moved to a new image that contains the bare minimum starting from the scratch image.

Within the folder build at the root of the repo there's a script call start.sh, it's invokation admits "Dev" as parameter. Running the script with the parameter will use the local version in the repository as the base for the building of the service's docker image, however doing it without providing it will make the building of the service taking everything from sources.

./start.sh [Dev]

The initial branch used when building from sources is "master", it can be changed with a few other parameters by editing the script.

Using the [Dev] optional argument will take the code present in the repo at the moment of invokation.

How to run

Within the folder run at the root of the repo there's a docker-compose sample file and a config.toml sample file. Once configured with appropriate data to start the service just issue the following command:

docker-compose up -d