diff options
| author |  vantezzen <hello@vantezzen.io> | 2020-04-02 17:33:16 +0200 |
|---|---|---|
| committer | vantezzen <hello@vantezzen.io> | 2020-04-02 17:33:16 +0200 |
| commit | c99f8760b6851559b6656ea27eb9fc645fddaa03 (patch) | |
| tree | cde626cf423b2a5d823fc16215e28e6402389acd /docs/updating.md | |
| parent | Fix documentation linking (diff) | |
| download | ferdium-recipes-c99f8760b6851559b6656ea27eb9fc645fddaa03.tar.gz ferdium-recipes-c99f8760b6851559b6656ea27eb9fc645fddaa03.tar.zst ferdium-recipes-c99f8760b6851559b6656ea27eb9fc645fddaa03.zip | |
Add better formatting
Diffstat (limited to 'docs/updating.md')
| -rw-r--r-- | docs/updating.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/updating.md b/docs/updating.md index afb29da..204d0a2 100644 --- a/docs/updating.md +++ b/docs/updating.md | |||
| @@ -4,7 +4,7 @@ If you want to improve or update an existing recipe, please follow this guide. | |||
| 4 | 4 | ||
| 5 | Please **do not** simply change files inside `uncompressed` - Ferdi only uses the packaged archives, the uncompressed files are only to improve accessibility of the repository. | 5 | Please **do not** simply change files inside `uncompressed` - Ferdi only uses the packaged archives, the uncompressed files are only to improve accessibility of the repository. |
| 6 | 6 | ||
| 7 | 0. Find the recipe ID of the recipe you want to update | 7 | ## 0. Find the recipe ID of the recipe you want to update |
| 8 | 8 | ||
| 9 | Before you can start updating the recipe, you'll need to know its internal ID. The ID is a string of lowercase letters and hyphens that Ferdi uses to store and manage them. | 9 | Before you can start updating the recipe, you'll need to know its internal ID. The ID is a string of lowercase letters and hyphens that Ferdi uses to store and manage them. |
| 10 | 10 | ||
| @@ -12,7 +12,7 @@ To find the recipe ID, you can search <https://github.com/getferdi/recipes/blob/ | |||
| 12 | 12 | ||
| 13 | In the rest of this guide, always replace "<recipe id>" with the ID of the recipe you want to edit. | 13 | In the rest of this guide, always replace "<recipe id>" with the ID of the recipe you want to edit. |
| 14 | 14 | ||
| 15 | 1. Implement your updates | 15 | ## 1. Implement your updates |
| 16 | 16 | ||
| 17 | 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. | 17 | 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. |
| 18 | 18 | ||
| @@ -23,7 +23,7 @@ You can find the recipe source Ferdi uses at: | |||
| 23 | 23 | ||
| 24 | After changing the files in that folder, you can reload the service inside Ferdi using `CTRL/CMD + R`. | 24 | After changing the files in that folder, you can reload the service inside Ferdi using `CTRL/CMD + R`. |
| 25 | 25 | ||
| 26 | 2. Setting up the recipe repository | 26 | ## 2. Setting up the recipe repository |
| 27 | 27 | ||
| 28 | - Fork https://github.com/getferdi/recipes and clone it to your computer | 28 | - Fork https://github.com/getferdi/recipes and clone it to your computer |
| 29 | - Open a terminal in the `scripts/` folder of that repository | 29 | - Open a terminal in the `scripts/` folder of that repository |
| @@ -31,7 +31,7 @@ After changing the files in that folder, you can reload the service inside Ferdi | |||
| 31 | 31 | ||
| 32 | This will setup the repository so that you can work on updating it. | 32 | This will setup the repository so that you can work on updating it. |
| 33 | 33 | ||
| 34 | 3. Loading and updating the recipe | 34 | ## 3. Loading and updating the recipe |
| 35 | 35 | ||
| 36 | Again, please **do not** edit any of the files located inside the `uncompressed` folder! Before editing, you'll need to "load" the recipe you want to edit using | 36 | Again, please **do not** edit any of the files located inside the `uncompressed` folder! Before editing, you'll need to "load" the recipe you want to edit using |
| 37 | ```JavaScript | 37 | ```JavaScript |
| @@ -41,12 +41,12 @@ yarn load <recipe id> | |||
| 41 | 41 | ||
| 42 | Your recipe is now loaded into `scripts/recipe_src`. You can now make changes to the files **in that folder*. | 42 | Your recipe is now loaded into `scripts/recipe_src`. You can now make changes to the files **in that folder*. |
| 43 | 43 | ||
| 44 | 4. Updating the version number | 44 | ## 4. Updating the version number |
| 45 | 45 | ||
| 46 | In order for Ferdi to update its recipe, you'll need to bump its version number. Increase the `version` inside `scripts/recipe_src/package.json`. | 46 | In order for Ferdi to update its recipe, you'll need to bump its version number. Increase the `version` inside `scripts/recipe_src/package.json`. |
| 47 | 47 | ||
| 48 | 5. Re-packaging the recipe | 48 | ## 5. Re-packaging the recipe |
| 49 | 49 | ||
| 50 | You can now run `yarn package` to repackage your updated files. Your changes will be automatically copied into the recipe source at `uncompressed` and compressed into `archives/<recipe id>.tar.gz` - no need to update anything manually! | 50 | You can now run `yarn package` to repackage your updated files. Your changes will be automatically copied into the recipe source at `uncompressed` and compressed into `archives/<recipe id>.tar.gz` - no need to update anything manually! |
| 51 | 51 | ||
| 52 | 6. Commit your changes and create a PR to <https://github.com/getferdi/recipes> | 52 | ## 6. Commit your changes and create a PR to <https://github.com/getferdi/recipes> |