pterodactyl/documentation
1
0
Fork 0
mirror of https://github.com/pterodactyl/documentation.git synced 2025-12-10 10:44:43 -06:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of https://github.com/pterodactyl/documentation

Browse Source
This commit is contained in:
Dane Everitt 2020-12-06 15:59:49 -08:00
commit 191d9243bb
No known key found for this signature in database
GPG Key ID: EEA66103B3D71F53
4 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
daemon/0.6/installing.md
View File

@ -1,5 +1,9 @@
# Installation
::: warning
This specific software is for Pterodactyl v0.7 and **must not be used for Pterodactyl v1.0**. If you have installed 1.0 you should use [Wings](/wings/1.0/installing.html) instead.
:::
[[toc]]
## Supported Systems

2
panel/1.0/upgrade/1.0.md
View File

@ -47,7 +47,7 @@ php artisan config:clear
```
## Database Updates
You'll also need to update your database schema for the newest version of Pterodactyl. Running the two commands below
You'll also need to update your database schema for the newest version of Pterodactyl. Running the command below
will update the schema and ensure the default eggs we ship are up to date (and add any new ones we might have). Just
remember, _never edit core eggs we ship_! They will be overwritten by this update process.

5
project/terms.md
View File

@ -5,7 +5,10 @@ nodes and servers to the system.
**Node** — A node is a physical machine that runs an instance of the Daemon.
**Daemon** — A service written in Nodejs that interfaces with Docker and the Panel to provide secure access for
controlling servers via the Panel.
controlling servers via the Panel before 1.0.
**Wings** — The newer service written in Go that interfaces with Docker and the Panel to provide secure access for
controlling servers via the Panel after 1.0.
**Server** — In this case, a server refers to a running instance that is created by the panel. These servers are
created on nodes, and you can have multiple servers per node.

2
tutorials/creating_ssl_certificates.md
View File

@ -66,7 +66,7 @@ curl https://get.acme.sh | sh
```
### Obtaining CloudFlare API Key
After installing acme.sh, we need to fetch a CloudFlare API key. Please make sure that a DNS record (A or CNAME record) is pointing to your target node, and set the cloud to grey (bypassing CloudFlare proxy). Then go to My Profile > API keys and on Glocal API Key subtab, click on "view", enter your CloudFlare password, and copy the API key to clipboard.
After installing acme.sh, we need to fetch a CloudFlare API key. Please make sure that a DNS record (A or CNAME record) is pointing to your target node, and set the cloud to grey (bypassing CloudFlare proxy). Then go to My Profile > API keys and on Global API Key subtab, click on "view", enter your CloudFlare password, and copy the API key to clipboard.
### Creating a Certificate
Since the configuration file is based on Certbot, we need to create the folder manually.