![]() Sorry, fink is just not an option for the audience we have in mind. The bonus there is that you don't have to package php or mysql, I would make a wrapper around testing for- and installing fink, and go from there. Anyone who's clever enough to have installed it elsewhere is also clever enough to not need this package. How will you make sure that you don't overwrite an existing mysql installīy making sure that /usr/local/mysql doesn't already exist. That's why I want to use a PackageMaker package, which is the standard software packaging tool for this platform. I'll be jumping in the same waters soon )ĭon't you care about the maintainabilty of your users computers? And if your package derives from his, you can always share bugfixes and enhancements.Īt any rate, keep us posted on how it goes. If you use fink, it's trivial to port the Debian package to fink - one less thing to think about. His package is a great place to start looking into if you are thinking of installing the cronjob and general installation scripts. ![]() There is a Debian package of Moodle, maintained by Isaac Clerencia (and very up-to-date, Isaac is using Moodle himself quite a bit). Edit: fink is often used to deploy software in large OSX clusters, with scripting techniques similar to the ones we use on our clusters at Catalyst. If it should work as well for production servers (edit: like that massively sexy Xserver cluster you've got), I'd go for Fink. PackageMaker is great for GUI apps, but is pretty dead on the water when it comes to upgrades ( AFAIK) - but this may not matter to you if it's just for test installations. Actually, it's all Perl, so I can get to the guts of it riding the camel. The fink route makes things easier for long-term maintenance, and has all the dependencies covered.įink package-building is all commandline, so it's really easy to automate with a bit of bash. In the case of package maker, I'd make a Fink package and distribute Fink +my package + dependencies. I've promised I'd package eXe - a Moodle-related project more info at - for the Mac, and I'm still undecided, doubting between PackageMaker and Fink. I am very interested in hearing of your experience using PackageMaker, specially wrt to automating the creation of new versions of the package. This whole thing is on hold until the end of the semester most likely. I think Daryl Hawes' suggestion is probably what we'll go with. This actually makes a lot of sense for most things, but could pose a problem for Moodlers who need to get into their data folders using the GUI finder. If I go out to tcsh, on the other hand, I see: My personal files are under Users/tonyhursh, rather than /home/tonyhursh as they would be on most Linux systems. The GUI only lets you browse to places where a "normal" user should be able to go, not to places where system files are kept.įor example, on my own machine the Finder shows me Applications, Developer, Library, moodledata, sw (used by Fink), System, and Users. The problem here is that you can't browse to /usr with the GUI Finder, you have to get there through the command line. Well I am not sure if OSX has a defined filesystem hierachy All he or she will see is a couple of prompts for setting passwords. If this is done properly, all the shell script stuff should be invisible to the user. I definitely don't want to clobber any existing stuff. This should definitely check to see if Apache and MySQL are running beforehand, and refuse to proceed if they are. ![]() Launch browser and point it at the Moodle install (shell script or AppleScript).ĭoes anyone see an important step I'm leaving out? Use perl or PHP to stick the right user info for the database in config.php.ĩ. Create a Moodle data folder and give it the correct permissions (shell script).ħ. Unpack Moodle into the proper place (/Library/WebServer/Documents), along with a pre-written config.php file (shell script)Ħ. Create MySQL users, databases, etc (shell script does this, using AppleScript to prompt for passwords for the the MySQL root user and the Moodle user).ĥ. ![]() Install My SQL (AppleScript or shell script)Ĥ. ![]() Install PHP (AppleScript or shell script).ģ. Open mpkg file containing Liyanage PHP package, MySQL, and Moodle.Ģ. I'm pretty sure I can use a combination of PackageMaker, shell scripting, and AppleScript to automate the process shown here (this is slightly different from the process given in the Moodle installation wiki).ġ. I've been tasked with creating a simple Moodle install package for OS X (similar to the easy install packages that exist for Windows). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |