Forum OpenACS Q&A: Installers and repositories
A lot of great work has already been done. Here are a few things I happen to have seen:
1. The efforts documented here:
2. Bart's work on RPMs
3. Derek's work on RPMs
Derek's post motivated this thread. I'm new to this, but am happy to do the legwork to support these awesome contributions.
OCT members, assuming this doesn't pose an undue performance or security risk, can we put this on our production machine?
Derek or Bart, can you outline what's involved in setting these repositories up?
Bear with me while I get up to speed.
Also in the other thread, Jade asked about integrating the repositories with file-storage. It sounds possible, and would give us RSS support, but would be a bit of extra work transferring all of the files in. We might be able to facilitate that with WebDav, assuming you can serve a yum repository from a different machine than the one you ran yum-arch on. Is this true?
- Windows Installer:
Please add our Project/Open installer to the list of installers (http://www.project-open.org/download/win/). The installer includes the same DotLrn configuration as Vlassis installer (together with the Project/Open options). Did you contact Vlassis recently? I haven't got any feedback from him during the last few weeks
- SuSE/Novell RPMs:
We've spent several days trying to build some source RPMs for SuSE including AOLServer, but we've failed terribly. I'm going to look for the code we've created so far. We would start again if we would have some support from some real RPM wizards.
Apart from that: Please count on our help if you've got something already, starting about the 10th of April (we've got some trade fairs before that...).
I can't tell you how happy I am to see this.
Wow, we now have SOAP support and we have a binary installers? The future is looking much brighter for OpenACS..
For the yum repository at least, the simplest approach seems to be giving Derek a filesystem directory where he can push stuff to the openacs.org server over rsync.
At this point I'm tasked with configuring rsync and granting the necessary rights. I'll try to get it done over the weekend.
For Frank's and any other non-repository oriented installers, perhaps a well-publicized link out, or a local copy in a file-storage instance, is in order.
For Frank's and any other non-repository oriented
installers, perhaps a well-publicized link out, or
a local copy in a file-storage instance, is in order.
Both would be fine with us.
However, the Windows installer currently has a quite
short release cycle (only 2-3 weeks), because of many
strange quirks that appear in different Windows versions.
So it would be important to include a link to the latest
version of the installer even if you maintain a local copy.
I would propose: http://www.project-open.org/download/win/.
We have just modified the page to explicitely include dotLrn.
Happy easter vacations!
Binary installers are not completely supported unless the
maintainer documents the process they used to build the
installer. We want to make it easy for someone else to step
in if a maintainer stops maintaining the installers. So this
is a criteria for full acceptance from the OCT.
Just seen this. So, anybody suspicious here? I don't know if that's directed towards P/O... It seems we've got an excellent reputation 😊 For clarity: The P/O installer is completely GPLed and _does_ include all of its sources and a "howto" document that explains how to build the installer.
Are there any volunteer for preparing an installer with the newest DotLrn version?
There is actually a new version of the installer coming out with P/O Beta8 probably tomorrow, which includes improved documentation and some tests to see if port 80 is free, whether there is already PG running and whether CygWin is already installed. These were the most frequent causes for installation errors in the past.
Finally some statistics: We had about 700 downloads of the "AlphaX versions since November and there were 54 installations of the "Beta5" and "Beta7" versions in the last three weeks.
please make sure you use the Beta8 since it now detects previously installed web servers and PostgreSQL instances. We haven't got any complaints since about failing installations.
However, there is still an issue with loading the timezone data on XP and Win2k3 and with PostgreSQL parameters different from the default values.
Does anybody know about issues with loading large quantities of data into CygWin PostgreSQL 7.4.3?
For details on the outstanding issues please check: