Websites are a type of resource that you can host on a Taubyte-based cloud computing network. They’re perfect for serving websites, web content, or any type of web assets. You can host Single Page Applications (SPAs), images, documents, and more, with the capability to update all of it simply through Git.
One key thing about websites on Taubyte is that they are built into assets which are addressed using a Content Identifier (CID). CIDs are unique labels that are used to point to digital content in a distributed system. This means each asset is not only verifiable for data integrity but is also cacheable at the edge. So, your websites are essentially CDN-native, giving you scalability and optimized performance.
The configuration of your website will reside in a YAML file in your project’s configuration repository. Here’s an example of what it looks like:
id: Qmb6LSfwzBpdqHYdbZjm42d88yWmK67N4n5Qqirao4Ezgy description: "" tags:  domains: - GeneratedDomain source: paths: - / branch: main github: id: 654784341 fullname: taubyte0/tb_website_test_tfil_cloud
Here’s a breakdown of what each field in the YAML file represents:
id: This is a unique identifier for your website.
description: Here, you can provide a brief summary of your website.
tags: These are optional metadata tags for your website that can be used for provisioning.
domains: This is a list of domains where your website will be accessible. You can read more about this in the DNS section.
source: This field specifies where the source code of your website resides.
paths: These define the paths that your website will be available at.
branch: This is where you specify the Git branch to be used.
github: Here, you specify the GitHub repository that contains your website’s code.
Apart from the configuration file, websites also have their own separate repository. This repository contains the website’s code and potentially CI/CD instructions for building the website. This segregation of code and configuration makes managing and scaling your web applications easier. We’ll go into more depth about CI/CD in a separate section.