Description of problem:
Moodle installs fine, but it isn't "ready to use".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install moodle (eg yum install moodle moodle-en)
2. point browser at http://localhost/moodle
Blank page with no hint to what could be wrong
Working Moodle setup (probably the run-once config setup page)
Moodle depends on having either mysql or postgresql running. However neither
is actually shown as a dependency - it would probably be better to pick one as
a required dependency.
After that, Moodle requires access to a set of tables, but they are not
created. It would be good if the moodle install started the database and
created the required user (with a randomly generated password) and moodle
There is probably also some httpd magic required - I haven't got that working
One of the documentation files included in the package has some instructions on
how to set the package up once it's been installed. I agree that they could be a
little more explicit, but if the moodle main page doesn't give any clues as to
what could be wrong there's little I can do about that.
As for the database dependency and especially the SQL structures, not happening.
It's not the packages job to modify other system items, especially since there's
no guarantee that the web server and database server are the same machine.
I'll modify the instructions to be a little more detailed, but in the end
there's not an awful lot I can or should do.
(Sorry, owner change apparently not propagated to Bugzilla yet.)
Do the recent documentation updates address your concerns?
I don't think my opinion and that of the maintainer(s) agree, but this bug
isn't going to fix that.
I'm happy for it to be closed.
Ok. I certainly didn't write comment #1, but it still is part of the overall
guidelines for packaging database-driven apps.