aboutsummaryrefslogtreecommitdiffstats
path: root/docs/updating.md
diff options
context:
space:
mode:
authorLibravatar vantezzen <hello@vantezzen.io>2020-04-02 17:31:21 +0200
committerLibravatar vantezzen <hello@vantezzen.io>2020-04-02 17:31:21 +0200
commitac582422d821edb614608cd8256f9f48efcf52d7 (patch)
tree0198a09e9af5f8e56c3b1a92c56453a0563b7ebe /docs/updating.md
parentFix habitica logo (diff)
downloadferdium-recipes-ac582422d821edb614608cd8256f9f48efcf52d7.tar.gz
ferdium-recipes-ac582422d821edb614608cd8256f9f48efcf52d7.tar.zst
ferdium-recipes-ac582422d821edb614608cd8256f9f48efcf52d7.zip
Add docs about updating existing recipes
Diffstat (limited to 'docs/updating.md')
-rw-r--r--docs/updating.md52
1 files changed, 52 insertions, 0 deletions
diff --git a/docs/updating.md b/docs/updating.md
new file mode 100644
index 0000000..afb29da
--- /dev/null
+++ b/docs/updating.md
@@ -0,0 +1,52 @@
1# How to update/change recipes
2
3If you want to improve or update an existing recipe, please follow this guide.
4
5Please **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
70. Find the recipe ID of the recipe you want to update
8
9Before 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
11To find the recipe ID, you can search <https://github.com/getferdi/recipes/blob/master/all.json> for the recipe you want to edit.
12
13In the rest of this guide, always replace "<recipe id>" with the ID of the recipe you want to edit.
14
151. Implement your updates
16
17We 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
19You can find the recipe source Ferdi uses at:
20 * Mac: `~/Library/Application Support/Ferdi/recipes/<recipe id>/`
21 * Windows: `%appdata%/Ferdi/recipes/<recipe id>/`
22 * Linux: `~/.config/Ferdi/recipes/<recipe id>`
23
24After changing the files in that folder, you can reload the service inside Ferdi using `CTRL/CMD + R`.
25
262. Setting up the recipe repository
27
28- Fork https://github.com/getferdi/recipes and clone it to your computer
29- Open a terminal in the `scripts/` folder of that repository
30- Run `yarn install` to install all dependencies
31
32This will setup the repository so that you can work on updating it.
33
343. Loading and updating the recipe
35
36Again, 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
38yarn load <recipe id>
39```
40(e.g. `yarn load gmail`)
41
42Your recipe is now loaded into `scripts/recipe_src`. You can now make changes to the files **in that folder*.
43
444. Updating the version number
45
46In 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
485. Re-packaging the recipe
49
50You 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
526. Commit your changes and create a PR to <https://github.com/getferdi/recipes>