Skip to content

Commit 9993756

Browse files
authored
QOL improvement
1 parent 936126d commit 9993756

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ volumes:
189189
- Lastly, install your extensions again. You can reinstall all of the extensions in your extensions folder with ``blueprint -i *.blueprint``.
190190
- If any of your extensions' settings are gone after this step, restore from your backup and ask the author of those extensions where persistent data is stored so you can back it up and restore it after each update.
191191

192-
## Option 3: Update both Blueprint and Pterodactyl Panel WHEN YOU HAVE SET UP THE NONROOT DEVELOPMENT ENVIRONMENT in the previous major section of this README.
192+
## Option 3: Update both Blueprint and Pterodactyl Panel WHEN YOU HAVE SET UP THE NONROOT DEVELOPMENT ENVIRONMENT in the [previous section](https://github.com/BlueprintFramework/docker#setting-up-a-development-environment) of this README.
193193
- This guide operates under the assumption that individual extension/theme authors have chosen to store any persistent data such as settings in the database. If they have not done this... there isn't any specific place extension data is meant to be stored, so the data could be anywhere. You'll need to ask them if there is any persistent data stored anywhere that you have to back up before updating.
194194
- Go to the directory of your docker-compose.yml file
195195
- ```bash

0 commit comments

Comments
 (0)