Skip to content
Snippets Groups Projects
Commit 3cb6b943 authored by Claudio Rosati's avatar Claudio Rosati
Browse files

Updated README.md

parent 4154711e
No related branches found
No related tags found
No related merge requests found
# ESS CS-Studio OPIs
This folder contains the validated and approved CS-Studio OPI files to be used at ESS to control the facility.
This folder contains the validated and approved CS-Studio OPI files to be used
at ESS to control the facility.
## Structure
......@@ -146,9 +147,28 @@ target-station/
└── tune-up-dump
```
## File and Folder Names
- File and folder names should be in accordance with the naming conventions.
- Folder names must be all lowercase.
- No white spaces are allowed in file/folder names: use '-' instead.
## Contributing the Repository
The repository can be cloned by everyone interested in. Changes can be performed
only through Pull Requests.
Currently only Claudio Rosati (claudio.rosati@esss.se) and Bejamin Bertrand (for
safety, as Infrastructure Group member, benjamin.bertrand@esss.se) are allowed
to approve the pull requests, and merge them into the repository.
As soon as someone else will be appointed to be in charge of this repository,
this readme file will be updated accordingly.
## Deployment
The ess-opis repository is cloned and mounted in CS-Studio by the [Ansible role](https://gitlab.esss.lu.se/ics-ansible-galaxy/ics-ans-role-cs-studio)
used to deploy CS-Studio.
Every time a push is done on the master branch, it triggers an Ansible job via AWX API to update the git repository on the LCR workstations.
Refer to the `.gitlab-ci.yml` file for the implementation.
Every time a push is done on the master branch, it triggers an Ansible job via
AWX API to update the git repository on the LCR workstations. Refer to the
`.gitlab-ci.yml` file for the implementation.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment