If you want to use GetGenius Node on your own hardware for yourself or your company and even customize it, you can do this at any time using the modular file system with extensions.
In this article, we will focus specifically on the GetGenius Node file system.
An overview of the file system of the GetGenius Node:
- root
- data
- aep
- assets
- fonts
- templates
- checkpoints
- output
- scripts
- tmp
- training
- aep
- environments
- app-cms
- stable-diffusion-webui
- workspaces
- data
/data #
The /data folder is the local storage space of the GetGenius Node. For example, AI models, rendered media and training data are stored here.
This folder is automatically synchronized with GetGenius. The folder is mainly used to minimize the necessary amount of data traffic, to compensate for short-term Internet outages and to protect against data loss.
/data/aep #
This folder is used exclusively for After Effects-based media rendering and contains After Effects footage, templates and required fonts
/data/checkpoints #
AI models, for example Large Language Models or Stable Diffusion / Motion Models, are stored in this folder in order to be globally available for various GetGenius tools
/data/output #
Files and media generated outside a workspace are saved in this folder.
/data/scripts #
This folder contains scripts required for the operation of the GetGenius Node, which are responsible for the processing of individual tasks and communication, for example.
/data/tmp #
This is a local cache folder in which only temporary files are stored.
/data/training #
This folder is used for individual AI model training. For example, media is prepared here so that it can be reused for AI training.
The individual AI models are also saved here during the training before they are moved to the /data/checkpoints folder after successful completion.
/environments #
Environments are individual modules and tools of the GetGenius ecosystem, which are automatically installed based on the activated tools and the available hardware.
/workspaces #
Workspaces are temporary, virtual environments that are configured and created individually based on a specific requirement or task.
