Portainer
/
portainer-docs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #124 from samdulam/upgrade-docs 

Icons on a few more pages
pull/126/head
samdulam 2021-02-23 21:49:27 +01:00 committed by GitHub
parent 57d8993113 3b0bc3ff02
commit 8c262b2dff
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/v2.0-be/deploy/requirements.md
View File

@ -1,4 +1,4 @@
# Requirements
# :fontawesome-solid-clipboard-list: Requirements
Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine.
By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose a TCP tunnel server over the port `#!Ruby 8000`. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
@ -8,7 +8,7 @@ Every single release of Portainer goes through an extensive testing process (fun
To try and alleviate confusion as to what we test against, we have documented the configurations that we personally validate as "functional"; any other variant is not tested (this does not mean it wont work, it just means its not tested).
## Validated Configurations
## :fontawesome-solid-check-double: Validated Configurations
| Portainer Version | Release Date | Docker Version | Kubernetes Version | Architectures | Operating Systems |
|-----------------------|--------------|----------------|-----------------------|---------------|----------------------------------------------------------------------------------------------|

6
docs/v2.0-be/deploy/ssl.md
View File

@ -1,8 +1,8 @@
# Secure Portainer using SSL
# :fontawesome-solid-shield-alt: Secure Portainer using SSL
By default, Portainer’s web interface and API is exposed over HTTP. This is not secure, Portainer recommends enabling SSL, particularly in a production environment.
## Securing Portainer using SSL with Docker
## :fontawesome-solid-lock: Securing Portainer using SSL with Docker
To do so, you can use the following flags <code>--ssl</code>, <code>--sslcert</code> and <code>--sslkey</code>:
@ -10,7 +10,7 @@ To do so, you can use the following flags <code>--ssl</code>, <code>--sslcert</c
Now, you can navigate to https://$ip-docker-host
## Securing Portainer using SSL with Docker Swarm
## :fontawesome-solid-lock: Securing Portainer using SSL with Docker Swarm
Securing Portainer on Docker Swarm is fairly simple. The following example takes in to asumption that you have an external overlay network and external secrets. If you do not, simply create them:

4
docs/v2.0/deploy/requirements.md
View File

@ -1,4 +1,4 @@
# Requirements
# :fontawesome-solid-clipboard-list: Requirements
Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine.
@ -8,7 +8,7 @@ Every single release of Portainer goes through an extensive testing process (fun
To try and alleviate confusion as to what we test against, we have documented the configurations that we personally validate as "functional"; any other variant is not tested (this does not mean it wont work, it just means its not tested).
## Validated Configurations
## :fontawesome-solid-check-double: Validated Configurations
| Portainer Version | Release Date | Docker Version | Kubernetes Version | Architectures | Operating Systems |
|--------------------------|----------------|----------------|------------------------------|----------------------|----------------------------------------------------------------------------------------------------------|

6
docs/v2.0/deploy/ssl.md
View File

@ -1,8 +1,8 @@
# Secure Portainer using SSL
# :fontawesome-solid-shield-alt: Secure Portainer using SSL
By default, Portainer’s web interface and API is exposed over HTTP. This is not secure, Portainer recommends enabling SSL, particularly in a production environment.
## Securing Portainer using SSL with Docker
## :fontawesome-solid-lock: Securing Portainer using SSL with Docker
To do so, you can use the following flags <code>--ssl</code>, <code>--sslcert</code> and <code>--sslkey</code>:
@ -10,7 +10,7 @@ To do so, you can use the following flags <code>--ssl</code>, <code>--sslcert</c
Now, you can navigate to https://$ip-docker-host
## Securing Portainer using SSL with Docker Swarm
## :fontawesome-solid-lock: Securing Portainer using SSL with Docker Swarm
Securing Portainer on Docker Swarm is fairly simple. The following example takes in to asumption that you have an external overlay network and external secrets. If you do not, simply create them: