Skip to content
Snippets Groups Projects
Select Git revision
  • dev protected
  • master default protected
  • Issue/3130-onboardingUzK
  • Issue/3109-onboarding
  • Issue/2915-migrateSql2Linked
  • test_ci
  • Issue/xxxx-fixDevcontainer
  • Issue/xxxx-generateLatestTag
  • Issue/2980-fixContainerBuild
  • Issue/2967-fixGD
  • Issue/2944-gdShenanigans
  • Issue/2906-containerCron
  • Issue/2880-gd
  • petar.hristov-master-patch-9e49
  • Issue/2668-graphDeployer
  • gitkeep
  • Hotfix/xxxx-fastDeployment
  • Hotfix/2615-graphDeployerLag
  • Issue/2568-betterLogging
  • Issue/2518-docs
  • v2.1.11
  • v2.1.10
  • v2.1.9
  • v2.1.8
  • v2.1.7
  • v2.1.6
  • v2.1.5
  • v2.1.4
  • v2.1.3
  • v2.1.2
  • v2.1.1
  • v2.1.0
  • v2.0.1
  • v2.0.0
  • v1.2.11
  • v1.2.10
  • v1.2.9
  • v1.2.8
  • v1.2.7
  • v1.2.6
40 results

README.md

Blame
    • Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    README.md 564 B

    GraphDeployer

    This repository handles the deployment of every static graph which gets included into the CoScInE environment.

    Usage

    For every deployable graph repository, an entry is expected in the configuration path: coscine/local/graphs/.

    Every repository MUST include the key coscine/local/graphs/{graphname}/repositoryurl for specifying the url (e.g. git.rwth-aachen.de/coscine/applicationprofiles.git) and CAN include the key coscine/local/graphs/{graphname}/branch which specifies the state of the repository being imported (e.g. master).