{{ cookiecutter.project_short_description }}
- GNU Make
- Python3
Docker
(if you wish to build and test the service locally)
- Add your additional libraries to the appropriate in file
env-config
- The Dockerfile shall be modified to install additional packages, software and/or Jupyter kernels (if something is need in addition to 1.)
- Optional: the .osparc is the configuration folder and source of truth for metadata: describes service info and expected inputs/outputs of the service. If you need to change the inputs/outputs of the service, description, thumbnail, etc... check the
metadata.yml
file - Optional: if you need to change the start-up behavior of the service, modify the
boot_notebook.bash
file - Optional (for testing): The service docker image may be built with
make build
(see "Useful Commands" below) - Optional (for testing): The service docker image may be run locally with
make run-local
(see "Useful Commands" below)
Once you're happy with your code:
- Push it to a public repository.
- An automated pipeline (GitHub Actions) will build the Docker image for you (as in step 5)
- Wait for the GitHub pipeline to run successfully
- Check that the automated pipeline executes successfully
- Once the pipeline has run successfully, get in touch with o²S²PARC Support, we will take care of the final steps!
If you wish to change your Service (e.g. add additional librarie), after it has been published on o²S²PARC, you have to create a new version:
- Go back to your repository
- Apply the desired changes
- Increase ("bump") the Service version: in your console execute:
make version-patch
, ormake version-minor
, ormake version-major
- Commit and push the changes to your repository
- Wait for the GitHub/GitLab pipelines to run successfully
- Once the pipeline has run successfully, get in touch with o²S²PARC Support, we will take care of publishing the new version!
$ make help
$ make build # This will build an o²S²PARC-compatible image (similar to `Docker build` command)
$ make run-local # This will run the JupyterLab interface on your computer. Follow the instructions in your console to open it in your browser (useful e.g. to test that your code runs as expected)