diff options
| author |  Vijay A <vraravam@users.noreply.github.com> | 2022-04-17 01:38:50 +0530 |
|---|---|---|
| committer | Vijay A <vraravam@users.noreply.github.com> | 2022-04-17 01:38:50 +0530 |
| commit | fc58230e6d229acb0573fc10b6fc4fd451c87c9c (patch) | |
| tree | f26a9b8abe0625da06c0d5d1216c8faa34be160c /docs/updating.md | |
| parent | Changed license filename and the new license-holders (diff) | |
| download | ferdium-recipes-fc58230e6d229acb0573fc10b6fc4fd451c87c9c.tar.gz ferdium-recipes-fc58230e6d229acb0573fc10b6fc4fd451c87c9c.tar.zst ferdium-recipes-fc58230e6d229acb0573fc10b6fc4fd451c87c9c.zip | |
Rebranded from 'ferdi' to 'ferdium' (companion changes for the main repo PR #2)
Diffstat (limited to 'docs/updating.md')
| -rw-r--r-- | docs/updating.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/updating.md b/docs/updating.md index f18da33..f840f50 100644 --- a/docs/updating.md +++ b/docs/updating.md | |||
| @@ -7,9 +7,9 @@ If you want to improve or update an existing recipe, please follow this guide. | |||
| 7 | We highly suggest that you implement and test your updates to the recipe inside Ferdi before implementing them into the recipe repository. This will save you time on debugging and repackaging the recipe later. | 7 | We highly suggest that you implement and test your updates to the recipe inside Ferdi before implementing them into the recipe repository. This will save you time on debugging and repackaging the recipe later. |
| 8 | 8 | ||
| 9 | You can find the recipe source Ferdi uses at: | 9 | You can find the recipe source Ferdi uses at: |
| 10 | * Mac: `~/Library/Application Support/Ferdi/recipes/<recipe id>/` | 10 | * Mac: `~/Library/Application Support/Ferdium/recipes/<recipe id>/` |
| 11 | * Windows: `%appdata%/Ferdi/recipes/<recipe id>/` | 11 | * Windows: `%appdata%/Ferdium/recipes/<recipe id>/` |
| 12 | * Linux: `~/.config/Ferdi/recipes/<recipe id>` | 12 | * Linux: `~/.config/Ferdium/recipes/<recipe id>` |
| 13 | 13 | ||
| 14 | > If you can't find the recipe's folder, please make sure that you have created a service inside Ferdi with that recipe - otherwise Ferdi will not load it into the folder | 14 | > If you can't find the recipe's folder, please make sure that you have created a service inside Ferdi with that recipe - otherwise Ferdi will not load it into the folder |
| 15 | 15 | ||
| @@ -17,7 +17,7 @@ After changing the files in that folder, you can reload the service inside Ferdi | |||
| 17 | 17 | ||
| 18 | ## 2. Setting up the recipe repository | 18 | ## 2. Setting up the recipe repository |
| 19 | 19 | ||
| 20 | Simply fork https://github.com/getferdi/recipes. You may also want to clone the repository to your computer to edit it locally. | 20 | Simply fork https://github.com/ferdium/ferdium-recipes. You may also want to clone the repository to your computer to edit it locally. |
| 21 | 21 | ||
| 22 | ## 3. Updating the recipe inside the repository | 22 | ## 3. Updating the recipe inside the repository |
| 23 | 23 | ||
| @@ -33,4 +33,4 @@ Ferdi uses this version to determine if it should update the local copy of the r | |||
| 33 | 33 | ||
| 34 | This might be the __most important step__ of this guide. You'll need to run the `pnpm run package` command to ensure that all validation checks are run. | 34 | This might be the __most important step__ of this guide. You'll need to run the `pnpm run package` command to ensure that all validation checks are run. |
| 35 | 35 | ||
| 36 | ## 6. Commit your changes and create a PR to <https://github.com/getferdi/recipes> | 36 | ## 6. Commit your changes and create a PR to <https://github.com/ferdium/ferdium-recipes> |