498
edits
Changes
Jump to navigation
Jump to search
Line 39:
Line 39: + + + + + + + + + + + + − ==upload size limit== − Max allowed packet value is locked at 10M by default on SME. − Let's delete the mysql custom-template in the future RPM! − − We can modify this value to only affect the ocs directory. − − Add the following lines to Apache template: − <Directory /opt/inventory/ocs/ocsreports> − .. − php_admin_value post_max_size $ocs{'MaxUpload'} − php_admin_value upload_max_filesize $ocs{'MaxUpload'} − Apply changes: − config setprop ocs MaxUpload xxM − expand-template /etc/httpd/conf/httpd.conf − /etc/init.d/httpd-e-smith condrestart − Default value: 10M − − ==aliases== − Future RPM will allow to add aliases using 'URL' value to ocs and glpi − { − if (exists $foo{'URL'}) − { $OUT .= "Alias /$foo{'URL'} /opt/foo\n"; } − } − − ==RPM is not a chatroom== − Less chat in the install output, just say look at the renamed wiki page − − ==events== − Don't use signal-event my-own-event: just give all the commands, or use an existing one, we could use domain-modify − − Stefen − ---- − Here's the future createlinks perl script: − #!/usr/bin/perl -w − use esmith::Build::CreateLinks qw(:all); − − # Templates to adjust − templates2events("/etc/e-smith/sql/init/80ocs_mysql.sql", qw(domain-modify post-upgrade )); − templates2events("/etc/e-smith/sql/init/82glpi_mysql.sql", qw(domain-modify post-upgrade )); − templates2events("/etc/e-smith/sql/init/84ocs-glpi.sql", qw(domain-modify post-upgrade )); − templates2events("/etc/ocsinventory-agent/ocsinv.conf", qw(domain-modify post-upgrade )); − templates2events("/opt/inventory/glpi/config/config_db.php", qw(domain-modify post-upgrade )); − templates2events("/opt/inventory/ocs/ocsreports/dbconfig.inc.php", qw(domain-modify post-upgrade )); − # Services to restart − safe_symlink("start", "root/etc/e-smith/events/domain-modify/services2adjust/mysql.init"); − Apache is already expanded and restarted by event ''domain-modify'' so I removed these useless lines... Events are also available when calling a ''post-upgrade''. I based this on how SME handles webmail and also what I've found in other SPRMs... − − − How I handle SME integration: − 80ocs_mysql.sql => create/update ocs database+user+password − 82glpi_mysql.sql => create/update glpi database+user+password − 84ocs-glpi.sql => apply ocs' password in glpi database − ocsinv.conf => apply Agent config − config_db.php => MySQL DB passwords − dbconfig.inc.php => MySQL DB passwords − {{Warning box|These templates allow to restore the good password when using www/ocs/install.php (used for web interface updates!!!)}} − {{Note box|These templates also ensures that if ocs password changes, it will be updated in glpi MySQL database!!!}} − {{Note box|These templates are working for RPM install, RPM updates and everyday use :-)}} − Cool34000 − ---- − − ==save bandwidth== − Create a separate RPM with the ''ocsagent.exe'' and ''guide.pdf'' and make it a dependency of the main RPM... − − Or maybe not? − − => files deleted in the tarball, this is 1.5MB + 6MB − − => ocsagent.exe needs to be installed anyway with www/ocs/install.php − − People should download latest client and put ocsagent.exe in www/ocs/files − − Will document this later − − => figured out why the guide.pdf is needed: there a link to it the web interface... − − People can download this file... Or not, let's warn that the help page won't be accessible in OCS! − − I think there is no need to put them as requires. I can put the guide.pdf in my folder and give the link in the wiki. − − ==MySQL init scripts == − /etc/e-smith/sql/init/* should only be used one to create the db table, then it is deleted − httpd.conf and php.ini are in standard events (and are we still changing php.ini?) − which only leaves three fragments to document in the rare case that something changes − − Stefen − ---- − Yes, all that goes in /etc/e-smith/sql/init/ is dropped after a successful importation. I know that, I use it this way: − *3 templates to dynamically create the DB+User+Password and change OCS' password in GLPI' database. These templates are harmless if re-expanded... − − *2 databases (one for ocs, one for glpi). They are imported ONLY ON NEW INSTALL. These 2 databases are dropped once imported (no need to keep them!)... It also allows me to import the right GLPI database according to ''$LANG'' − − So when the RPM runs: − * 3 files loaded on RPM updates − * 5 files loaded on RPM install − Take a look on their name when all 5 files are put in /etc/e-smith/sql/init/ once expanded − − Cool3400 − ---- − − Line 152:
Line 63: − − − − ==new accounts== − 2 'url' accounts types will be created for ocs: − root/etc/e-smith/db/accounts/defaults/ocsinterface − root/etc/e-smith/db/accounts/defaults/ocsinventory − These virtual locations are used by ocs server-side.
Talk:OCS Inventory Tools (view source)
Revision as of 23:49, 8 November 2007
, 23:49, 8 November 2007Would like to fix deps before releasing...
stephen
stephen
----
----
=RPM 1-6=
Job already done:
- Removed useless MySQL custom-template
- Removed ocsagent.exe and guide.pdf
- Upload limit fixed
- 'MaxUpload' DB entry added to set dynamically max upload file size (default still at 10M)
- Events moved to domain-modify
- 2 new 'url' types added for ocs' virtual locations
- Uninstall script now also deletes new DB values + logs + old inventories
- Improved Apache templates to allow adding aliases for both web interfaces
- RPM runs silently :'(
=future RPM=
=future RPM=
What will be fixed in next RPM release...
What will be fixed in next RPM release...
==dependencies==
==dependencies==
change the install method to install the perl dependencies that are available from existing repos.
change the install method to install the perl dependencies that are available from existing repos.
stephen
stephen
----
----