Latest Development FOG
-
Opening this thread to maintain the “latest” and greatest of FOG updates. This will be where I post about what’s happening, what revisions we’re up to etc…
-
r1714 released.
Add’s a pause prompt after the installation/upgrade of the fog Web system to inform the installer to go to the page so they can update the schema. This way all can continue successfully as long as the user follows the instructions.
While it’s been a few revision updates since, the most pertinent and important to note upgrades is that I’ve modified the way mysql is queried. I’ve also moved all the plugins into their own folders outside of management/plugins. As a matter of fact, management/plugins is no more at all. The new location is statically located at lib/plugins and follows a directory tree structure to help standardize and implement new things.
Tree structure for plugins is now:
/var/www/{fog,html/fog}/lib/plugins/
<PLUGINNAME>/ #The plugin name needs match the $fog_plugin[‘name’] = <PLUGINNAME>
html/ #Contains the run.php
images/ #Contains the images the plugin is to use.
includes/ #Contains any of the needed include files for the plugin.
hooks/ #Contains (NOT WORKING YET) the hooks to change the FOG pages.
config/ #Contains the plugin.config.php file that initializes the plugin to FOG.
class/ #Class files Class name to match the plugin name as well. (e.g. Capone.class.php,CaponeManager.class.php)
That is about it. See any of the current plugins within this directory for an example of what’s needed.Of note: Class files are typically used for Database interaction. So each class, if a required database install, would need A base.class.php and baseManager.class.php where base is the same as the class name of the plugin. BaseManager is what allows for find, count, destroy, search, parameters to operate.
-
Tested latest revision 1716 and Kernel Update under FOG Configuration works fine on my side
-
[quote=“Albatros, post: 27804, member: 16710”]Tested latest revision 1716 and Kernel Update under FOG Configuration works fine on my side ;)[/quote]
Important to note, does imaging still work?
-
[quote=“Tom Elliott, post: 27817, member: 7271”]Important to note, does imaging still work?[/quote]
Tested download and upload of an image, didn’t got any problems.
-
[quote=“Albatros, post: 27825, member: 16710”]Tested download and upload of an image, didn’t got any problems.[/quote]
AWESOME! YAY!
-
how can I get this revision
-
[quote=“darkxeno, post: 27881, member: 4011”]how can I get this revision[/quote]
Take a look at this
[url]http://fogproject.org/wiki/index.php/SVN[/url] -
or download the BTSync and get all the changes as they happen.
-
The location plugin appears to be broken now. When I try to install it I hit submit and it goes to a white screen and stays there. I am running the latest revision on 1.0.1. I am running Ubuntu 12.04 I really need this functionality to work for my setup, Does anyone know how to make this work?
Small note: this was working in 1.0.0
apache log:
[CODE][Fri May 23 08:17:05 2014] [error] [client 172.30.100.75] PHP Fatal error: Call to a member function mainMenu() on a non-object in /var/www/fog/management/index.php on line 72
[Fri May 23 08:19:49 2014] [error] [client 172.30.100.75] PHP Parse error: syntax error, unexpected ‘}’ in /var/www/fog/lib/plugins/location/class/LocationManager.class.php on line 46, referer: http://fogserver/fog/management/index.php?node=plugin&sub=installed&run=d5189de027922f81005951e6efe0efd5&installed=d5189de027922f81005951e6efe0efd5
[Fri May 23 08:20:34 2014] [error] [client 172.30.100.75] PHP Parse error: syntax error, unexpected ‘}’ in /var/www/fog/lib/plugins/location/class/LocationManager.class.php on line 46, referer: http://fogserver/fog/management/index.php?node=plugin&sub=installed&run=d5189de027922f81005951e6efe0efd5&installed=d5189de027922f81005951e6efe0efd5[/CODE] -
[quote=“bradlylewis22, post: 28037, member: 23940”]The location plugin appears to be broken now. When I try to install it I hit submit and it goes to a white screen and stays there. I am running the latest revision on 1.0.1. I am running Ubuntu 12.04 I really need this functionality to work for my setup, Does anyone know how to make this work?
Small note: this was working in 1.0.0
apache log:
[CODE][Fri May 23 08:17:05 2014] [error] [client 172.30.100.75] PHP Fatal error: Call to a member function mainMenu() on a non-object in /var/www/fog/management/index.php on line 72
[Fri May 23 08:19:49 2014] [error] [client 172.30.100.75] PHP Parse error: syntax error, unexpected ‘}’ in /var/www/fog/lib/plugins/location/class/LocationManager.class.php on line 46, referer: http://fogserver/fog/management/index.php?node=plugin&sub=installed&run=d5189de027922f81005951e6efe0efd5&installed=d5189de027922f81005951e6efe0efd5
[Fri May 23 08:20:34 2014] [error] [client 172.30.100.75] PHP Parse error: syntax error, unexpected ‘}’ in /var/www/fog/lib/plugins/location/class/LocationManager.class.php on line 46, referer: http://fogserver/fog/management/index.php?node=plugin&sub=installed&run=d5189de027922f81005951e6efe0efd5&installed=d5189de027922f81005951e6efe0efd5[/CODE][/quote]I’ve fixed this in svn.
-
Hi is the latest fog 1.0.0 compatible with Ubuntu 10.04 LTS and up?
-
yes, the latest fog 1.0.1 is compatible with Ubuntu 10.04 LTS and up, though i don’t recommend 14.04 due to the number of issues reported on it. Ubuntu 13.10 and 12.04 are fine, however.
-
[quote=“Junkhacker, post: 28167, member: 21583”]yes, the latest fog 1.0.1 is compatible with Ubuntu 10.04 LTS and up, though i don’t recommend 14.04 due to the number of issues reported on it. Ubuntu 13.10 and 12.04 are fine, however.[/quote]
FWIW, I’ve been using 14.04 without an issue. I did change the /var/www/html back to /var/www … don’t know if that makes a difference or not. No fog issues, created an image using VirtualBox, uploaded it and then deployed it and snapins onto a few different PCs/Laptops now.
Obviously, everyone, listen to the devs, if they say they can support you better using 13.10, use it, BUT, if you’ve already got a 14.04 server going and don’t want to have to start from scratch, give it a try, it wasn’t even difficult to get fog going, if you ask me.
-
SVN 1731 released
Hooks and Page Classes are now called through as autoload rather than directly including the files. It’s still the same, but uses the proper methods needed.
Quick registration now has an option to join a quick registered host to a group at registration time.
Major speed performance increase on the GUI side as I know only register hooks if they’re active rather than having hook manager display what’s active. I don’t know if this will translate to those on isolated networks, but it won’t hurt either.
SVN 1732 released
Only includes Hook’s who have a value of true for their active flag. If the hook is by a plugin, it only includes the hook if the plugin is active. -
SVN 1738 released
Suggestive change to 1.1.0. Updates the changelog with all the changes and fixes I could remember at the time.
Updates the installer to point out the new supported OS’s Windows 7, Windows 8, Linux ext 2,3,4
Fixes the report management page if an image is not assigned to a host. -
When installing it prompts the user to leave the MySQL password blank.
however when you get near the end of the install it asks for your MySQL password and wont accept a blank password.could we update the warning or is this something different?
-
[quote=“VincentJ, post: 28240, member: 8935”]When installing it prompts the user to leave the MySQL password blank.
however when you get near the end of the install it asks for your MySQL password and wont accept a blank password.could we update the warning or is this something different?[/quote]
I’ve added a check. It will ask if you left the password blank. If you did (which it defaults to) it continues on as normal, otherwise it will prompt for the password at install time. Hopefully this helps.
-
Possibly also consider getting the first warning to let users know they can enter it later rather than telling them they need to edit a file later
Just installed my test suite on the btsync version. luckily means every fog server becomes a btsync peer.
could we have a quick script that can be run without interaction that does updates?
-
when not participating in beta testing, updates only need to be installed infrequently. for this reason, i do not feel that a “no touch” updater is needed. there was another forum poster that created one, however, if you care to seek it out. though, as i recall, this script broke slightly with one of the updates to the install/update script.
