You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28-2Lines changed: 28 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,16 +96,41 @@ Pushes a file system path onto the end of `BAKEPATH`.
96
96
97
97
### `bake_require libname`
98
98
99
-
Searches `BAKEPATH` for the library and sources it, loading the file (executing its contents). Libraries should (generally) only contain declarations, as any imperative code will be executed when the library is loaded. Libraries may load other libraries.
99
+
Searches `BAKEPATH` for the library and sources it, loading the file (executing its contents). Libraries should (generally) only contain declarations, as any imperative code will be executed when the library is loaded. Libraries may load other libraries.
100
+
101
+
You can also load libraries from Github or Enterprise Github instances. See the [Remote Libraries](#remote_libraries) section for more details.
100
102
101
103
## Look Ma, no `Bakefile` aka lets use a `./bake` directory
102
104
103
105
`bake` can also be used without a `Bakefile`, if you make a directory called `bake` and place shell files within it, `bake` will treat everything in that directory as library and require it automatically. See the section on libraries below.
104
106
105
-
# Libraries!
107
+
108
+
# Libraries
106
109
107
110
Some of the goals I had for for `bake` are for it to encourage best practices for shell scripting and to encourage re-use by encouraging the creation of small re-useable parts including libraries. Bake encourages small re-useable functions essentially by requiring the use of shell functions. It's up to you to break your functions into libraries that can be shared across your projects. Have a look at the [Best Practices](#best-practices) section below.
0 commit comments