feat(readme): Format information and warnings into blocknotes.
This commit is contained in:
parent
eae26ad67a
commit
9a6e2ae33f
1 changed files with 11 additions and 9 deletions
18
README.md
18
README.md
|
@ -32,9 +32,10 @@ We aim to introduce new developers to Blueprint with easy to understand guides,
|
|||
* Common sense.
|
||||
|
||||
**Installation:**
|
||||
1. Blueprint doesn't mix well with other modifications, so if you already have any, [perform a panel update](https://pterodactyl.io/panel/1.0/updating.html) before moving on with this guide.
|
||||
2. Navigate to your Pterodactyl folder. (most likely `/var/www/pterodactyl`)
|
||||
3. Install NodeJS, NPM and Yarn using the following commands. This assumes you are running Pterodactyl on Ubuntu or Debian-based systems.
|
||||
> **Important**
|
||||
> Blueprint doesn't mix well with other modifications, so if you already have any, [perform a panel update](https://pterodactyl.io/panel/1.0/updating.html) before moving on with this guide.
|
||||
1. Navigate to your Pterodactyl folder. (most likely `/var/www/pterodactyl`)
|
||||
2. Install NodeJS, NPM and Yarn using the following commands. This assumes you are running Pterodactyl on Ubuntu or Debian-based systems.
|
||||
```sh
|
||||
sudo apt-get install -y ca-certificates curl gnupg
|
||||
sudo mkdir -p /etc/apt/keyrings
|
||||
|
@ -45,14 +46,14 @@ apt-get install -y nodejs
|
|||
npm i -g yarn
|
||||
yarn
|
||||
```
|
||||
4. Download [the latest release of Blueprint](https://github.com/teamblueprint/main/releases/latest) and extract it (stable build) or pull the files via git (bleeding-edge build).
|
||||
5. If you haven't already, place the Blueprint files inside of your Pterodactyl folder. (common location is `/var/www/pterodactyl`)
|
||||
6. Run the Blueprint installation script. This runs the commands required for Blueprint to function correctly. If your Pterodactyl folder is not `/var/www/pterodactyl` you may need to put `_FOLDER="/path/to/pterodactyl"` in front of `bash blueprint.sh`.
|
||||
3. Download [the latest release of Blueprint](https://github.com/teamblueprint/main/releases/latest) and extract it (stable build) or pull the files via git (bleeding-edge build).
|
||||
4. If you haven't already, place the Blueprint files inside of your Pterodactyl folder. (common location is `/var/www/pterodactyl`)
|
||||
5. Run the Blueprint installation script. This runs the commands required for Blueprint to function correctly. If your Pterodactyl folder is not `/var/www/pterodactyl` you may need to put `_FOLDER="/path/to/pterodactyl"` in front of `bash blueprint.sh`.
|
||||
```sh
|
||||
chmod +x blueprint.sh
|
||||
bash blueprint.sh
|
||||
```
|
||||
7. After waiting for the installation script to finish, open up your Pterodactyl admin panel and click on the puzzle icon in the top right of the website.
|
||||
6. After waiting for the installation script to finish, open up your Pterodactyl admin panel and click on the puzzle icon in the top right of the website.
|
||||
|
||||
<br/>
|
||||
|
||||
|
@ -62,7 +63,8 @@ We've made some guides and documentation for extension development over on [GitB
|
|||
<br/>
|
||||
|
||||
## Extensions
|
||||
[Open an issue](https://github.com/teamblueprint/main/issues) on GitHub to get your extension listed here. To install an extension, upload your `something.blueprint` file to your Pterodactyl folder and run `blueprint -install something`.
|
||||
> **Information**
|
||||
> [Open an issue](https://github.com/teamblueprint/main/issues) on GitHub to get your extension listed here. To install an extension, upload your `something.blueprint` file to your Pterodactyl folder and run `blueprint -install something`.
|
||||
|
||||
**Announcements**: [PterodactylMarket](https://pterodactylmarket.com/resource/679), [sourceXchange](https://www.sourcexchange.net/products/announcements), [BuiltByBit](https://builtbybit.com/resources/announcements-for-blueprint.32546/)\
|
||||
**Arc.io Integration**: [BuiltByBit](https://builtbybit.com/resources/pterodactyl-v1-addon-arc-integration.32109/)\
|
||||
|
|
Loading…
Reference in a new issue