To install and use Hero on a full VM running on the grid, read the [full VM guide](https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/docs/hero_mdbook_fullvm.md).
## Create a New mdBook
## Create a New mdBook
To create a new mdbook, read the [mdbook creation guide](https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/docs/hero_create_mdbook.md).
To create a new mdbook, read the [mdbook creation guide](./docs/hero_create_mdbook.md).
## Use Hero with Docker
You can use Hero with Docker. Read the docs [here](./docs/hero_mdbook_docker.md).
## Basic Mdbook Info
To get started with Mdbook before learning Hero Mdbook, read [this documentation](./docs/mdbook_basics.md).
## Contribute
## Contribute
To contribute to this repository, make a pull request of your changes.
To optimize updates to this repository, we propose a uniform way to collaborate.
### Branches and Forks
To contribute to this repository, make a pull request of your changes. There are two main methods.
1. Fork the repository and make a pull requests with your changes
1. Fork the repository and make a pull requests with your changes
2. If you have access, create a new branch in this repo and make a pull request with your changes
2. If you have access, create a new branch in this repo and make a pull request with your changes
### Overview
- The production-ready content is published on the **main** branch
- The staging content is published on the **development** branch
- Any changes to development must go through a pull request (PR) and its associated review from a different branch with the prefix `development_`.
- The name of the branch should indicate the work being done, e.g. working on the readme, `development_readme_work`
- Once staging is done on development, the code owners will merge development branch to main branch.
- The mdbooks will be updated online.
### Content Update Procedure
- Create new branch out of development (e.g. `development_work`)
- Make changes to the files
- Make a PR to merge to development
- Get reviewed and adjust accordingly
- PR is approved and the content is merged to development
- Code owners will merge development to main to update the books online
We are more than just Container or VM technology, see [our Beyond Container Document](beyond_containers).
We are more than just Container or VM technology, see [our Beyond Container Document](beyond_containers.md).
A 3Node is a Zero-OS enabled computer which is hosted with any of the TF_Farmers.
A 3Node is a Zero-OS enabled computer which is hosted with any of the TF_Farmers.
There are 4 storage mechanisms which can be used to store your data:
There are 4 storage mechanisms which can be used to store your data:
- ZOS_FS is our dedupe unique filesystem, replaces docker images.
- Zero-Image is our dedupe unique filesystem, replaces docker images.
- ZOS_Mount is a mounted disk location on SSD, this can be used as faster storage location.
- Zero-Mount is a mounted disk location on SSD, this can be used as faster storage location.
- QSFS, this is a super unique storage system, data can never be lost or corrupted. Please be reminded that this storage layer is only meant to be used for secondary storage applications.
- Quantum Safe Storage System, this is a super unique storage system, data can never be lost or corrupted. Please be reminded that this storage layer is only meant to be used for secondary storage applications.
- ZOS_Disk, a virtual disk technology, only for TFTech OEM partners.
- Zero-Disk, a virtual disk technology, only for TFTech OEM partners.
There are 4 ways how networks can be connected to a Z-Machine.
There are 4 ways how networks can be connected to a Z-Machine.
-Planetary_network : is a planetary scalable network, we have clients for windows, osx, android and iphone.
-Mycelium : is a planetary scalable network, we have clients for windows, osx, android and iphone.
-zos_net : is a fast end2end encrypted network technology, keep your traffic between your z_machines 100% private.
-Zero-Net : is a fast end2end encrypted network technology, keep your traffic between your z_machines 100% private.
-zos_bridge: connection to a public ipaddress
-Zero-Bridge: connection to a public ipaddress
-web_gw: web gateway, a secure way to allow internet traffic reach your secure Z-Machine.
-Web-Gateway: web gateway, a secure way to allow internet traffic reach your secure Z-Machine.
@@ -47,8 +47,8 @@ In addition, wireless meshing requires you to know a lot about the network aroun
The planetary network is a continuation & implementation of the [Yggdrasil](https://yggdrasil-network.github.io/about.html) network initiative. This technology is in beta but has been proven to work already quite well.
The planetary network is a continuation & implementation of the [Yggdrasil](https://yggdrasil-network.github.io/about.html) network initiative. This technology is in beta but has been proven to work already quite well.
> Click [here](manual:planetary_network_connector) to read more about Planetary Network Connector Installation. Click [here](manual:yggdrasil_client) to read more about Planetary Network Installation (advanced).
> Click [here](manual:planetary_network_connector) to read more about Planetary Network Connector Installation. Click [here](manual:yggdrasil_client) to read more about Planetary Network Installation (advanced).
@@ -8,4 +8,4 @@ The quantum save storage system is zero knowledge proof compliant. The storage s
The zero proof knowledge compliancy comes from the fact the all the physical storage nodes (3nodes) can proof that they store a valid part of what data the quantum safe storage engine (QSSE) has stored on multiple independent devices. The QSSE can validate that all the QSSE storage devices have a valid part of the original information. The storage devices however have no idea what the original stored data is as they only have a part (description) of the origina data and have no access to the original data part or the complete origal data objects.
The zero proof knowledge compliancy comes from the fact the all the physical storage nodes (3nodes) can proof that they store a valid part of what data the quantum safe storage engine (QSSE) has stored on multiple independent devices. The QSSE can validate that all the QSSE storage devices have a valid part of the original information. The storage devices however have no idea what the original stored data is as they only have a part (description) of the origina data and have no access to the original data part or the complete origal data objects.
Imagine a storage system with the following benefits
Imagine a storage system with the following benefits
!!!include:qss_benefits_
!!wiki.include page:qss_benefits_
> This is not a dream but does exist and is the underpinning of the TFGrid.
> This is not a dream but does exist and is the underpinning of the TFGrid.
@@ -13,9 +13,9 @@ Our storage architecture follows the true peer-to-peer design of the TF grid. An
Peer-to-peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. Also, you might want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture and could be built by using the same building blocks produced by farmers and consumed by developers or end-users.
Peer-to-peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. Also, you might want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture and could be built by using the same building blocks produced by farmers and consumed by developers or end-users.
@@ -33,6 +33,6 @@ As a consequence, no tcp/ip is coming in AT ALL, making the full set-up reach un
- You don’t have to worry about ‘how to secure my DB’ as my DB is not exposed, only accessible in Wireguard private network.
- You don’t have to worry about ‘how to secure my DB’ as my DB is not exposed, only accessible in Wireguard private network.
- In containers you can specify to have specific IPv6 address, so deploy reverse proxy in container which has public access, = entry point in the network, deploy reverse tcp connection (=tcp router client), connects to the gateways and allows incoming connection.
- In containers you can specify to have specific IPv6 address, so deploy reverse proxy in container which has public access, = entry point in the network, deploy reverse tcp connection (=tcp router client), connects to the gateways and allows incoming connection.
### Imagine an operating system with the following benefits
### Imagine an operating system with the following benefits
@@ -28,9 +28,9 @@
- **Simplicity**: An operating system should be simple, able to exist anywhere, for anyone, good for the planet.
- **Simplicity**: An operating system should be simple, able to exist anywhere, for anyone, good for the planet.
- **Stateless**. In a grid (peer-to-peer) set up, the sum of the components is providing a stable basis for single elements to fail and not bring the whole system down. Therefore, it is necessary for single elements to be stateless, and the state needs to be stored within the grid.
- **Stateless**. In a grid (peer-to-peer) set up, the sum of the components is providing a stable basis for single elements to fail and not bring the whole system down. Therefore, it is necessary for single elements to be stateless, and the state needs to be stored within the grid.
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
