Installing TYPO3 Version 4 on Debian

Just a quick walk through the steps necessary to get typo3 up and running. I had serendipity running for some time on apache2.2 with php5. So that worked prior to installing typo3. Than do

  1. sudo aptitude install typo3 php5-curl unrtf (php5-curl and unrft are only suggestions I splashed out on)
  2. zless /usr/share/doc/typo3/README.Debian.gz which lists what else to do
  3. sudo ln -s /etc/typo3-dummy/apache.conf /etc/apache2/sites-available/typo3 to make the typo3 directory (and underlying php stuff) available to apache2
  4. sudo rm -f /etc/apache2/conf.d/typo3-dummy.conf which is placed here by the debian package (maybe it is better placed here because it’s not really a site but some basic server config… I’ll delete it anyway)
  5. sudo a2ensite typo3 to enable the “site”. Bear in mind that this config grants access from anywhere (Order allow,deny \ Allow from all)
  6. sudo /etc/init.d/apache2 reload or alternatively do apache2ctl restart which, as the command suggests, restarts the whole server.
  7. Since PHP save mode is used the file and directory permissions on file system level have to be set to WWWUSER/WWWGROUP (www-data/www-data) for /var/lib/typo3-dummy. It’s done by the package allready.
  8. Log in to phpmyadmin and create a table (search for “Create new database”) named “typo3-dummy” (don’t use “typo3-dummy” unless you can enter the escape sequence "\`" for characters like “-“). An alternative method is to use the command line mysqladmin -u root -p create typo3dummy (see the typo3 wiki and mysql manual)
  9. Use the command line mysql -u root -p typo3dummy to log in to the new database (note the command is not mysqladmin) and grant permissions with mysql> GRANT ALL ON typo3dummy.* TO '<username>'@'localhost' IDENTIFIED BY '<password>';
    where everything in <> has to be individually replaced (without the <>).
  10. Now the hot stuff begins: Point the browser at http://servername/typo3/ which will start the 1-2-3 install tool. Login with your root user and password for mysql server and follow the steps. That’s it, folks! Enjoy.

Looking for a quick starter, some test page to try out typo3 on? Have a look at a german tutorial by Dawn or go directly to the suggested url to download the .t3d and instructions. Another place to go and grab some it the YAML for typo3 page. One might need to increase the memory size available to php via the apache config file /etc/php5/apache2/php.ini and search for memory_limit. Don’t forget to reload the apache2 configs afterwards.

4 Comments

  1. Saturday, 18th Jun 2011 at 13:33

    One important issue is that when you are searching for a education loan you may find that you will need a co-signer. There are many situations where this is correct because you will find that you do not employ a past credit rating so the financial institution will require you have someone cosign the credit for you. Great post.

  2. Friday, 9th Jul 2010 at 12:43

    […] […]

  3. sysblogd said,

    Thursday, 21st Jun 2007 at 12:06

    Hi wolf.

    I don’t have my configs handy and it’s been a while, but what seams strange to me is that you’re refering to /etc/typo3-dummy/apache.conf and /etc/apache2/sites-available/typo3 as if they were two files. As in 3. I suggest a ln -s it’s a symlink so they are actually the same files.

    Two questions come to my mind:

    Have you done the bit suggested in 4. above, remove the .deb /etc/apache2/conf.d/typo3-dummy.conf?

    What does apache say when you /etc/init.d/apache restart (or reload) the server? Any bitching on doublicated entries or the like?

    I’m just curious. Thanks for posting your solution!

  4. wolf said,

    Wednesday, 20th Jun 2007 at 09:36

    I had a problem with a recursion caused by point 3:
    sudo ln -s /etc/typo3-dummy/apache.conf /etc/apache2/sites-available/typo3

    however inside /etc/typo3-dummy/apache.conf there is an alias named typo3 which causes recursion to etc/apache2/sites-available/typo3

    If you have:
    cat /var/log/apache2/error.log

    [error] [client xx.xxx.xx.xx] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.

    then you should look for solving this recursion.

    I did this simply with copying the alias section from /etc/typo3-dummy/apache.conf to etc/apache2/sites-available/default and deleting the typo3 symlink in sites-enabled


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: