FOG Updater
-
-
It does now.
For you all, the ‘trunk’ variable is what it’s basing stable or dev-branch (RC’s) to be installed.
If you add
trunk='yes'
or just any value other than blank, it will assume you’re wanting to install a development branch.You can add
trunk='yes'
to your /opt/fog/.fogsettings or call it inline like:trunk='yes' ./fogupdater.sh
-
It should work, though I’ll admit I’ve not tested it in a while.
-
is this what the filename is intending? will this auto update without hassles to latest dev branch build? Something that may can be used by a cronjob by night?
-
Lets try this again with better formatting:
Result:
-
Code from updater wont post correctly. I am pretty sure the URLs are outdated
-
@Tom-Elliott it doesn’t work.
-
It does now.
For you all, the ‘trunk’ variable is what it’s basing stable or dev-branch (RC’s) to be installed.
If you add
trunk='yes'
or just any value other than blank, it will assume you’re wanting to install a development branch.You can add
trunk='yes'
to your /opt/fog/.fogsettings or call it inline like:trunk='yes' ./fogupdater.sh
-
@x23piracy I’d highly recommend using the base stuff. The whole purpose of the
-y
argument was to kind of allow automating the stuff you need done. While the utils are there, I believe they were there before we added the -y arguments and it still required user input. Essentially, the util was there as a “oh look there’s a nice way to check if there are updates”. Ultimately, in my own opinion, this utility is rather pointless, especially now with the slew of arguments we have available now. -
@Tom-Elliott don’t slap me, i will not use the script i was just fighting for the op