A project on Taubyte is represented by a YAML file stored in a Git repository. This YAML file contains vital details of your project such as its ID, name, description, and notification settings. Here’s a sneak peek of a simple project configuration:
id: QmfZhf5eUQw2SY63JDKwMyLe6eGWKpz4CLn4MAEsvpyiAb name: yoo description: "" notification: email: email@example.com
Configuration Repository: This repository is a collection of YAML files that collectively outline your project’s resources. It houses the main YAML file which defines your project, along with any additional YAML files required to specify other resources necessary for your project to run effectively.
Inline Code Repository: This repository works in tandem with your configuration repository, providing a place for your inline code to reside. It’s the ideal storage for code related to your serverless functions and other alike resources.
A Multiverse of Truths
A unique feature of Git is that a repository isn’t confined to a single state but instead exhibits a state for each specific commit (or branch). Taubyte takes advantage of this characteristic, empowering you to deploy varying versions of your projects to different regions of the network. While you can choose the branch to deploy, most of the nodes in the network default to the master (or main) branch as their source of truth.
Since you’re leveraging Git repositories, you retain full control of your project. Modifying access to your project is as straightforward as adjusting your repository’s settings. It means that you decide who can read or write to your project by simply managing the access control of your repositories.
Deploying projects across multiple cloud networks is made painless with Taubyte. To launch a project on another Taubyte-based cloud computing network, all you need to do is register the project’s two core repositories with that network.
This functionality breaks down the barriers to deploying across different cloud environments, enabling you to manage multi-cloud deployments effortlessly. It embodies the true essence of decentralization, where you are not tied down to a single cloud provider but have the flexibility to leverage the best of each.