[Typo3-debian] Provide a useful apache.conf - sendmail, cgi problems remaining

Christian Leutloff leutloff at debian.org
Thu Dec 2 08:14:12 CET 2004


Hello Michael,

Michael Stucki wrote:

>>yes, you are right. I'm doing it the way you described on my own servers.
>>But for Debian all other (PHP based) programs I know of (phpldapadmin,
>>phpmyadmin, dwww) use a sub dir in the local web server.

> Hmmm. I still disagree about your plan with site packages. But this is your
> decision. I'm already wondering to see how you will to update a database
> structure when a new release comes out...
 
> If you consequently used the site-installer to create new sites, then you
> could let the user decide if he wants to have a VirtualHost or just a
> subdirectory for his new site.

The (Debian) user will get the freedom to choose between the site packages and the site-installer. The site packages are provided to get a resonable production system with as little effort as possible. Therefor they provide secure and fast default settings and a well integration into the normal Debian systems.  All other users (and Debian ones if they like) will use the site-installer. I think that the site-installer will provide a more flexible way than the packages based installation.

The database is *not* updated automatically. The SQL-File will be used through the installation with the TYPO3 1-2-3 install tool. For the database upgrade the TYPO3 tools will be used, too.
 
> I have written a new htaccess file that is much larger and well commented.
> It takes care of all known bugs and is almost ready for the RealUrl
> extension. I also added this to our CVS repository, it's in
> doc/advanced.htaccess. Please have a look at it!

yes, thanks, superb! I'll base the apache.conf on that file!

> Don't know if it's better to specifiy these parts inside of the Apache
> config fire or within an .htaccess file, but I'd say the first options
> looks better to me (read the file and you'll see that there are parts that
> can only be set in the Apache config file, not in .htaccess).

you have given the answers yourself in the advanced.htaccess:

# Using rewriting in your httpd.conf is much faster, btw.

The reason is simple: if .htaccess is enabled through AllowOverride apache has to open every subdirectory between the Documentroot dir and the actual one, check for .htacces, load it and reparse the file. As stated in the apache documentation .htacces should be disabled if not required. 

 
>>yes, typo3 is located in /usr/share/typo3. In /var are only files that
>>will change through the operation of typo3.
> 
> Except the change in typo3/install/index.php, there is nothing to be changed
> inside of the source anymore.
> 
> Remember my suggestion of site config files in /etc/typo3/, then it would be
> very easy to enable/disable both install tool and the whole backend with
> just two lines.

I'll comment on the other post ...

Bye
Christian

-- 
Christian Leutloff, Aachen, Germany 
leutloff at sundancer.oche.de - http://www.oche.de/~leutloff/
Debian GNU/Linux - leutloff at debian.org - http://www.de.debian.org/



More information about the TYPO3-debian mailing list