mirror of
https://github.com/ClusterCockpit/cc-backend
synced 2024-11-10 00:47:26 +01:00
Backend for ClusterCockpit Monitoring Framework. GitHub Mirror
.github/workflows | ||
auth | ||
config | ||
frontend@41b8953eb1 | ||
graph | ||
metricdata | ||
schema | ||
templates | ||
utils | ||
.env | ||
.gitignore | ||
.gitmodules | ||
go.mod | ||
go.sum | ||
gqlgen.yml | ||
init-db.go | ||
LICENSE | ||
README.md | ||
rest-api.go | ||
server.go |
ClusterCockpit with a Golang backend (Only supports archived jobs)
Run server
# The frontend is a submodule, so use `--recursive`
git clone --recursive git@github.com:ClusterCockpit/cc-jobarchive.git
# Prepare frontend
cd ./cc-jobarchive/frontend
yarn install
yarn build
cd ..
go get
go build
# The job-archive directory must be organised the same way as
# as for the regular ClusterCockpit.
ln -s <your-existing-job-archive> ./var/job-archive
# Create empty job.db (Will be initialized as SQLite3 database)
touch ./var/job.db
# This will first initialize the job.db database by traversing all
# `meta.json` files in the job-archive. After that, a HTTP server on
# the port 8080 will be running. The `--init-db` is only needed the first time.
./cc-jobarchive --init-db
# Show other options:
./cc-jobarchive --help
Update GraphQL schema
This project uses gqlgen for the GraphQL API. The schema can be found in ./graph/schema.graphqls
. After changing it, you need to run go run github.com/99designs/gqlgen
which will update graph/model
. In case new resolvers are needed, they will be inserted into graph/schema.resolvers.go
, where you will need to implement them.