This repository was archived by the owner on Nov 2, 2024. It is now read-only.
Replies: 2 comments
-
Nope |
Beta Was this translation helpful? Give feedback.
0 replies
-
I could hide a bunch of variables, gotta think about making it easier to vet the code for a particular application |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As I'm getting more familiar with all the functions and utilities in this repo, I see a few opportunities of improvements. I would like to know your thoughts on these:
msg_info
function is defined both inbuild.func
andinstall.func
common.func
file with common functions that can be loaded at the beginning ofbuild.func
andinstall.func
default_settings
function inside an app's script only to superseed a base configurationMTU=""
,SD=""
,NS=""
andMAC=""
, the entire set of options could be defined somewhere else (say abase_settings
function inbuild.func
), so by callingdefault_settings
after loading the base settings, scripts would only need to specify what is specific (RAM, CPU...)APT_CACHER
andAPT_CACHER_IP
options since people would only need to set them up in the base settings/environment variablesBeta Was this translation helpful? Give feedback.
All reactions