On Saturday 10 December 2005 15:41, Lior Kaplan wrote:
> Shlomi Fish wrote:
> > On Saturday 10 December 2005 14:45, Lior Kaplan wrote:
> >>Fine by me. But:
> >>
> >>1. Try to keep it simple - both the user interface and the backend.
> >
> > That I can do. The user-interface should be a standard web UI of a LUG or
> > Linux portal. For the first incarnation I plan most changes to have to be
> > made either using database queries, or by editing the sources of the
> > repositories. I may add some admin screens later on, but it won't be a
> > hard priority.
> >
> >>2. Please document what you system needs - so every can know which
> >>packages they should NOT remove or WHAT to check after an upgrade.
> >
> > OK.
> >
> >>3. Please use this change to make the web site more standard on the
> >>server site - directories and apache configure wise.
> >
> > Define "standard" in this context?
>
> See bellow
>
> >>Using /iglu isn't standard.
> >
> > It's /IGLU and now /IGLU/index.php. I will probably keep them for the
> > PostNuke system. But the root directory - http://www.iglu.org.il/ will
> > now be the main site.
>
> I ment /iglu on the server ... but /IGLU is also discourged. Please use
> /var/www/www.iglu.org.il as your DocumentRoot. This way other sites can
> have similar directories.
Hmmm... everything is already under /iglu (and cannot be effectively removed).
I like everything to be under one place rather than spread in two or more
different places in the filesystem. Apache doesn't care if we put it this way
or the other, and we'll probably retain the old paths for a long time.
The default place to put the HTML files in Mandriva is /var/www/html, but this
is just for the primary domain. But it's just a recommendation - you can put
these anywhere you like. We've decided (for historical and other reasons) to
put everything under /iglu/ where we know they are taken care of.
>
> >>And the apache config has too many overrides
> >>of the cgi-bin dir.
> >
> > That's not a problem. Apache configurations are expected to have stuff
> > like Aliases, ScriptAliases, etc. It's perfectly natural.
> >
> > As an example consider a directory that has the files "myscript.pl" and
> > "MyConfig.pm" and "password.txt". Now, you don't want people to access
> > MyConfig.pm, much less want them to access "password.txt". So what you do
> > is set a ScriptAlias (or a different mod_perlified alias) pointing to
> > "myscript.pl" (preferably with a nice URL), and then you are safe.
>
> That's why you don't put the password.txt in a directory which is under
> the DocumentRoot... So in any case - no one can access it from the web.
>
I like to put the script along with the password.txt and the configuration
files in one directory (not under DocumentRoot) and then:
1. Make a server alias directly to the CGI script.
2. Access the password.txt and the configuration files from the same
directory.
That way - they are both self-contained and secure. Putting a CGI script
under /var/www/cgi-bin and letting it access a password.txt file from
somewhere completely different does not scale too well, because you have to
recreate the different path somewhere else. It reminds me of all these
open-source web applications where you need to set up places in a gazillion
different paths before they'll work.
> And I'd like to use Debian's default httpd.conf, all the other stuff
> should be in the include files. In this issue our status is quite good.
>
That is something worth pursuing. But please let me do it as I am webmastering
most of the sites. Please put the Debian default httpd.conf
as /etc/apache/httpd.conf.debian (while preserving the origin file
in /etc/apache/httpd.conf), and I'll try to conslidate them step by step.
> >>4. Good idea! It would be really nice to see a site that has all the
> >>info about the LUGs in Israel - including info about what & where is the
> >>next lecture.
> >
> > Sure, that would be a good idea. The clubs have some RSS feeds for their
> > events, which I can use. We may wish to switch to our own custom XML
> > format, because we have relatively bastarised RSS in this case. But I
> > also plan www.iglu.org.il to be a general portal (in English) about
> > GNU/Linux and FOSS in Israel, and a usable way to access the other
> > resources on the site.
>
> Please start small, do try to have it all in one place. I think we have
> enough protals alrady. Let the public ask for new stuff.
I will start small, and also first put it on a temporary hostname. (I need it
so relative links to external resources will be given). My objectives for the
new site are:
1. Link to the useful resources on www.iglu.org.il in a good, usable way.
2. Introduce and provide information about the Israeli Linux and FOSS
community to foreigner visitors or surfers.
3. Provide a useful portal for English-speakers (not necessarily native
English speakers) in Israel.
Regards,
Shlomi Fish
---------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Homepage: http://www.shlomifish.org/
95% of the programmers consider 95% of the code they did not write, in the
bottom 5%.
