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
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,7 +165,7 @@ function fetch-s3-package () {
165
165
166
166
## Configuration at the top
167
167
168
-
Extract configuration and parameters into environment variables, place these at the top of your script. This will help anyone looking at your `Bakefile` or libraries understand what configuration options you're using and how to set or override them.
168
+
Extract configuration and parameters into environment variables, place these at the top of your script. This will help anyone looking at your `Bakefile` or libraries understand what configuration options you're using and how to set or override them.
bake_echo_red "Error: please copy $CONFIG.template to $CONFIG and
186
+
bake_echo_red "Error: please copy $CONFIG.template to $CONFIG and
187
187
bake_echo_red "fill in the required paramters."
188
188
return 1
189
189
fi
@@ -280,7 +280,7 @@ function alembic () {
280
280
281
281
## Namespaces
282
282
283
-
`bash` technically doesn't have namespaces forfunctions, yet it allows for periods `.` and colons `:`in the names of shell functions. Using these allows us to get many of the benefits of namespaces.
283
+
`bash` technically doesn't have namespaces forfunctions, yet it allows for periods `.` and colons `:`in the names of shell functions. Using these allows us to get many of the benefits of namespaces.
284
284
285
285
Here's an example of using colons `:` for namespacing
0 commit comments