Context
The Generic process allows you to execute code hosted in a Git repository or packaged as a Docker image:
On EDITO Cloud (CPU or GPU)
On an external SSH target
On an HPC environment
This process is designed for one-time execution.
It can also be used as a lightweight way to test and iterate on your process directly from My Workspace, without publishing it as an EDITO Playground Process.
This makes Generic useful both for standalone runs and for validating your process before deciding to make it available (or not) more broadly on EDITO.
💡 EDITO Pro Tip: you can save your configuration by giving it a name (1) and clicking on save (7)! Do not forget to save just before launching (8) to have the full configuration saved.
⚠️ Generic is not designed for runs repeated every day, especially on GPU:
- When it starts from a Dockerfile, it builds a new image at every run, which takes time and accumulates images;
- On GPU, the GPU is reserved during the whole build, not only while your code runs;
- The Python or Shell script mode does not support GPU.
For a process you run regularly, prefer add-your-process, which builds your image once per version.
Option 1 - Run your code on EDITO Cloud (CPU or GPU)
If your code is based on a Python or Shell script
Code section (2)
Select “My code is based on a Python or a Shell script”
Configure the Git repository - fill in the Git-related fields:
Provide script and environment - you must provide:
The path to your main script (Python or Shell)
The path to your environment YAML file
Example of a basic environment file:
name: my-env
channels:
- conda-forge
dependencies:
- python=3.13
- pipThis environment file is used to install all the dependencies required by your script before execution.
Target section (3)
First, select “My process should execute on EDITO Cloud”
Then configure the required resources:
CPU guaranteed and maximum
Memory guaranteed and maximum
📌 Note: if your process requires a GPU and if your EDITO quota include GPU access, enable “My process relies on GPU”.
S3 Configuration (4)
Provide your S3 credentials here. They will be automatically available as environment variables inside the container. Your script can use them to read/write data inside your bucket.
Copernicus Marine credentials (5)
Same behavior as S3, your credentials are exposed as environment variables.
Custom Runtime Environment Variables (6)
Use: “Additional custom Runtime Environment variables”
For each variable:
Name → environment variable name
Value → associated value
These variables will be accessible inside your script.
If your code is based on a Docker image or Dockerfile
Code section (2)
First, select “My code is based on Docker”
Then, choose how your image is provided:
If build from a Dockerfile, provide:
If using an existing Docker image:
Target section (3)
CPU guaranteed and maximum
Memory guaranteed and maximum
📌 Note: if your process requires a GPU and if your EDITO quota include GPU access, enable “My process relies on GPU”. Please, be sure to provide a Dockerfile based on a GPU-compatible image, or a GPU-based image.
S3 Configuration (4)
Provide your S3 credentials here. They will be automatically available as environment variables inside the container. Your script can use them to read/write data inside your bucket.
Copernicus Marine credentials (5)
Same behavior as S3, your credentials are exposed as environment variables.
Custom Runtime Environment Variables (6)
Use: “Additional custom Runtime Environment variables”
For each variable:
Name → environment variable name
Value → associated value
These variables will be accessible inside your script.
Option 2 - Run your code on an external SSH/HPC target
If your code is based on a Python or Shell script
Code section (2)
Select “My code is based on a Python or a Shell script”
Configure the Git repository - fill in the Git-related fields:
Provide script and environment - you must provide:
The path to your main script (Python or Shell)
The path to your environment YAML file
Example of a basic environment file:
name: my-env
channels:
- conda-forge
dependencies:
- python=3.13
- pip
This environment file is used to install all the dependencies required by your script before execution. EDITO will automatically build a Docker image from your code.
Target section (3)
Under Execution target, select "My process should execute on an external SSH target"
In the Run on a remote server via SSH section, configure the connection to your remote server by providing the required SSH settings:
SSH user: your username on the remote server. If you are connecting to an HPC system such as LIR, use your HPC username.
Host: the hostname or address of the remote server.
Private key and Public key: these fields are automatically filled in by EDITO.
These settings allow EDITO to connect to the remote target and execute your code.
These credentials allow EDITO to access and execute the job on your target.
HPC configuration (optional)
If your target is an HPC system:
Make sure your EDITO public key (My Account > Profile > HPC section) has been added to the
authorized_keysfile of your account on the HPC system. The procedure varies between HPC centers; refer to the relevant documentation if needed. This step has to be manually performed by the user for the targeted platform. If the connection can not be perfomed passwordless the process will stop.In the HPC access section, below the SSH configuration, enable the following option:
Check this if your target is an HPC. In that case, please enable S3 configuration to retrieve logs.
Configure the additional HPC settings as required by your HPC center:
Partition: the SLURM partition to use (
-p).Project: the project name used in the path
/scratch_path/project/user.Scratch directory: the scratch path used in
/scratch_path/project/user.SLURM account: the account to specify in the SLURM directive (
-A).
⚠️ Logs behavior
You must configure S3 credentials, the logs will be stored in S3 and retrieved from there:
SSH: Logs are directly visible in EDITO
HPC: Logs are automatically pushed to the configured S3 bucket, don't forget to fill out the S3 configuration section
GPU usage (optional)
If your target provides GPU resources, enable “My process relies on GPU”
EDITO will:
Build a GPU-compatible Docker image
Run it on your target
S3 Configuration (4)
Provide your S3 credentials here. They will be automatically available as environment variables inside the container. Your script can use them to read/write data inside your bucket.
Copernicus Marine credentials (5)
Same behavior as S3, your credentials are exposed as environment variables.
Custom Runtime Environment Variables (6)
Use: “Additional custom Runtime Environment variables”
For each variable:
Name → environment variable name
Value → associated value
These variables will be accessible inside your script.
If your code is based on a Docker image or Dockerfile
Code section (2)
First, select “My code is based on Docker”
Then, choose how your image is provided:
If build from a Dockerfile, provide:
If using an existing Docker image:
Target section (3)
Select “My process should execute on an external SSH target”
Configure the connection in the Run on a remote server via SSH section:
SSH user: your username on the remote server. For an HPC system, use your HPC username.
Host: the hostname or address of the remote server.
Private key and Public key: these fields are automatically filled in by EDITO.
These credentials allow EDITO to access and execute the job on your target.
HPC configuration (optional)
If your target is an HPC system:
Make sure your EDITO public key (My Account > Profile > HPC section) has been added to the
authorized_keysfile of your account on the HPC system. Refer to the HPC connection guide for more information.In the HPC access section, below the SSH configuration, enable the following option:
Check this if your target is an HPC. In that case, please enable S3 configuration to retrieve logs.
Fill in the HPC-specific settings as required by your HPC center:
Partition: the SLURM partition to use.
Project: the project name used in the path
/scratch_path/project/user.Scratch directory: the scratch path used in
/scratch_path/project/user.SLURM account: the account to specify in the SLURM directive (
-A).
⚠️ Logs behavior
You must configure S3 credentials, the logs will be stored in S3 and retrieved from there:
SSH: Logs are directly visible in EDITO
HPC: Logs are automatically pushed to the configured S3 bucket, don't forget to fill out the S3 configuration section
GPU usage (optional)
If your target provides GPU resources, enable “My process relies on GPU”
EDITO will:
Build a GPU-compatible Docker image
Run it on your target
S3 Configuration (4)
Provide your S3 credentials here. They will be automatically available as environment variables inside the container. Your script can use them to read/write data inside your bucket.
Copernicus Marine credentials (5)
Same behavior as S3, your credentials are exposed as environment variables.
Custom Runtime Environment Variables (6)
Use: “Additional custom Runtime Environment variables”
For each variable:
Name → environment variable name
Value → associated value
These variables will be accessible inside your script.
💡 Use the Generic Process to run and test your code directly from My Workspace, without creating a Playground Process on EDITO. Your code is fetched from your GitLab/GitHub repository or Docker image, so you can easily test and iterate on different versions. If you later decide to publish your process on EDITO, you can use add-your-process once it is ready.
What's next?
Ready to run your code?
To learn more about connecting to an external HPC from an EDITO application or process, read the HPC connection guide.
If you have any questions, problems, or suggestions, please contact us through the chat widget at the bottom right of this page.

























