Setting up a dev Onedata instance

Overview
Creative Commons License: CC-BY Questions:
  • How to set up a minimal Onedata dev instance?

  • How can I test the Galaxy & Onedata integration in a sandbox environment?

Objectives:
  • Quickly set up a zero-config dockerized Onedata deployment.

  • Run Onedata locally for Galaxy development and testing purposes.

Requirements:
Time estimation: 20 minutes
Level: Introductory Introductory
Supporting Materials:
Published: Mar 24, 2025
Last modification: Mar 24, 2025
License: Tutorial Content is licensed under Creative Commons Attribution 4.0 International License. The GTN Framework is licensed under MIT
version Revision: 1

Prerequisites

It’s recommended that you have basic knowledge about Onedata. If needed, follow this tutorial first!

Introduction

If you are familiar with docker, you can easily set up a local Onedata sandbox deployment. It may come in handy if you wish to test Galaxy & Onedata integration or develop features related to data management in Galaxy.

Demo mode

Use the official Onedata tutorial for running the system in demo mode.

If you are new to this, run a Onezone and Oneprovider instance in foreground. When the setup is finished, log in to the Onezone interface, using the IP address and credentials displayed in Onezone docker logs (as explained in the guide).

Use the Onezone docker IP as the Onezone domain in all Onedata related configs in Galaxy. Use the predefined Space called demo-space for Storage Location configs (global or BYOS).

Warning: The demo mode runs on self-signed certificates

You will need to accept the untrusted connection in your browser to enter the UI.

Remember to disable TLS certificate validation in the Galaxy configs!

Follow the getting started tutorial to acquire an access token, or use the convenience scripts of the demo mode (as explained in the guide).

Related materials

The demo mode is used for setting up Onedata in Galaxy’s Object Store integration tests. Take a look at the code (search for “onedata”).