fix includes syntax
This commit is contained in:
@@ -11,4 +11,4 @@ A major step in accepting and importing Docker images is to transpose docker ima
|
||||
- Easy import and transpose facility
|
||||
- deduplicated application deployment simplifying aplication image management and versioning
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
@@ -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.
|
||||
- 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.
|
||||
|
||||
!!!def alias:network_wall,net_wall
|
||||
!!def alias:network_wall,net_wall
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
|
@@ -27,4 +27,4 @@ At Threefold, we are aware of the existence of private networks, IPsec, VPN, WAN
|
||||
|
||||

|
||||
|
||||
!!!def alias:quantumsafe_network_concept,qsn_concept
|
||||
!!def alias:quantumsafe_network_concept,qsn_concept
|
@@ -34,6 +34,6 @@ The Prometheus ecosystem consists of multiple components, many of which are opti
|
||||
- ONLY for OEM partners today
|
||||
|
||||
|
||||
!!!def alias:zos_monitoring
|
||||
!!def alias:zos_monitoring
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
|
@@ -5,7 +5,7 @@
|
||||

|
||||
|
||||
|
||||
!!!include:whatis_zos
|
||||
!!wiki.include page:whatis_zos
|
||||
|
||||
### 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.
|
||||
- **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.
|
||||
|
||||
<!-- !!!include:zos_toc -->
|
||||
<!-- !!wiki.include page:zos_toc -->
|
||||
|
||||
!!!def alias:zos,zero-os,threefold_operating_system,tf_os,threefold_os
|
||||
!!def alias:zos,zero-os,threefold_operating_system,tf_os,threefold_os
|
||||
|
||||
|
||||
|
||||
|
@@ -3,4 +3,4 @@
|
||||

|
||||
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
@@ -18,4 +18,4 @@ The operating system is not installed on any local storage medium (hard disk, ss
|
||||
|
||||
The mechanism to allow this to work in a safe and efficient manner is a ThreeFold innovation called our container virtual filesystem. This is explained in more detail [here](flist)
|
||||
|
||||
!!!def alias:zero_os_install
|
||||
!!def alias:zero_os_install
|
@@ -3,4 +3,4 @@
|
||||

|
||||
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
|
Reference in New Issue
Block a user