development_manual #64
| @@ -2,10 +2,10 @@ | ||||
|  | ||||
| <h2> Table of Contents </h2> | ||||
|  | ||||
| - [Zero-OS Hub](manual:zos_hub.md) | ||||
| - [Zero-OS Hub](zos_hub.md) | ||||
| - [Generate an API Token](api_token.md) | ||||
| - [Convert Docker Image Into Flist](./flist_hub/convert_docker_image.md) | ||||
| - [Convert Docker Image Into Flist](convert_docker_image.md) | ||||
| - [Supported Flists](./grid3_supported_flists.md) | ||||
| - [Flist Case Studies](./flist_case_studies/flist_case_studies.md) | ||||
|   - [Case Study: Debian 12](./flist_case_studies/flist_debian_case_study.md) | ||||
|   - [Case Study: Nextcloud AIO](./flist_case_studies/flist_nextcloud_case_study.md) | ||||
| - [Flist Case Studies](flist_case_studies.md) | ||||
|   - [Case Study: Debian 12](flist_debian_case_study.md) | ||||
|   - [Case Study: Nextcloud AIO](flist_nextcloud_case_study.md) | ||||
| @@ -49,7 +49,7 @@ As a general advice, before creating an flist for a ThreeFold deployment, you sh | ||||
|  | ||||
| Before we go any further, let us recall what is an flist. In short, an flist is a technology for storing and efficiently sharing sets of files. While it has many great features, it's purpose in this case is simply to deliver the image contents to Zero-OS for execution as a micro VM. It thus acts as a bundle of files like a normal archive. | ||||
|  | ||||
| One convenient thing about the flist technology is that it is possible to convert any Docker image into an flist, thanks to the [ThreeFold Docker Hub Converter tool](https://hub.grid.tf/docker-convert). It is very easy to do and we will show you how to proceed in this case study. For a quick guide on converting Docker images into flists, read [this section](../flist_hub/convert_docker_image.md) of the ThreeFold Manual. | ||||
| One convenient thing about the flist technology is that it is possible to convert any Docker image into an flist, thanks to the [ThreeFold Docker Hub Converter tool](https://hub.grid.tf/docker-convert). It is very easy to do and we will show you how to proceed in this case study. For a quick guide on converting Docker images into flists, read [this section](convert_docker_image.md) of the ThreeFold Manual. | ||||
|  | ||||
| ## Case Study Objective | ||||
|  | ||||
| @@ -70,7 +70,7 @@ One important thing to have in mind is that, when we create an flist, what we ar | ||||
|  | ||||
| Once we've successfully created an flist, we thus have a very quick way to deploy a specific workload while always obtaining the same result. This is why it is highly recommended to test a given deployment on a full or micro VM before building an flist. | ||||
|  | ||||
| For example, in the case of building a Nextcloud All-in-One flist, the prerequisites would be to successfully deploy a Nextcloud AIO instance on a full VM by executing each step sequentially. This specific example is documented in the Terraform section [Nextcloud All-in-One Guide](../../../system_administrators/terraform/advanced/terraform_nextcloud_aio.md) of the System Administrators book. | ||||
| For example, in the case of building a Nextcloud All-in-One flist, the prerequisites would be to successfully deploy a Nextcloud AIO instance on a full VM by executing each step sequentially. This specific example is documented in the Terraform section [Nextcloud All-in-One Guide](system_administrators@@terraform_nextcloud_aio) of the System Administrators book. | ||||
|  | ||||
| In our case, the flist we will be using has some specific configurations depending on the way we deploy Nextcloud (e.g. using or not the gateway and a custom domain). The Terraform **main.tf** we will be sharing later on will thus take all this into account for a smooth deployment. | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user