add open source to the core feature set

This commit is contained in:
dovholuknf 2023-02-02 09:21:19 -05:00
parent e37cacaab2
commit e9ec9f2120
No known key found for this signature in database
GPG Key ID: 0EE08251136D3480
3 changed files with 28 additions and 2 deletions

View File

@ -1,5 +1,5 @@
---
sidebar_position: 100
sidebar_position: 200
---
# Hosting

View File

@ -0,0 +1,26 @@
---
sidebar_position: 100
---
# Open Source
It's important to the `zrok` project that it remain free and open source software. The code is available on GitHub
for the world to use, inspect, and build upon!
Check out the repository over on GitHub at https://github.com/openziti/zrok. If you find `zrok` to be useful, and
you want to help spread the word of `zrok` give the project a star. It really does help get the word out about the
project.
The project also uses a very permissive license: Apache v2. We encourage people to fork the repo and use `zrok` for
your own purposes how you see fit or contribute back to the project.
## Built on OpenZiti
The power of `zrok` really lies in `private` sharing. It's increasingly clear that security needs to be a first-class
member of any organization. To enable `private` sharing, `zrok` was built on top of another excellent open source
project named OpenZiti.
OpenZiti is a secure overlay network focusing on bringing zero trust to applications. It is the __backbone__ of `zrok`.
In fact, `zrok` proudly proclaims itself as an OpenZiti _native_ application.
If you are interested in learning more about OpenZiti head over to https://openziti.io, read the docs, try the
quickstart, and don't forget to star that project too. We couldn't build `zrok` without OpenZiti!

View File

@ -25,6 +25,6 @@ be done in a public way, for more secure access.
Using `private` shares is easy and is accomplished using the `zrok share private` command. Run `zrok share private`
to see the usage output and to further learn how to use the command.
Unlike public shares, `private` shares do not need to be [reserved](./sharing-reserved.md). When sharing a
Unlike public shares, `private` shares do not need to be [reserved](./sharing-reserved.md) to be predictable. When sharing a
resource with `private`, the resource is shared at a known location. Resources shared with `private` do not
need to be `reserved`.