Topic: [ANNOUNCE] Typo3 CMS (Version 4.04) as rpm for SME7

[berdie]

to the community,

for the ease of installation a rpm package of Typo3 version 4.03 for the SME Server 7.0 is available at http://sudemo.info/sme/sme7/webapp/typo3/smeserver-typo3-4.0.3-1.noarch.rpm
This package installs the popular Content Management System Typo3 within a new ibay "typo3".
You can start the Typo3-Frontend with http://MyServer/typo3
Yun can start the Typo3-Backend with http://MyServer/typo3/typo3
(User="admin", password="password"). Please change the password after the first login.

Regards,
Dietmar

New Version based on typo3-4.0.4. available: see my posting further down

[fpausp]

Hi berdie,

Have got a little problem when i try to install typo3:

[root@server ~]# rpm -Uvh smeserver-typo*
Preparing...                ########################################### [100%]
        file /usr/man/man8/lat-ibays.8.gz from install of smeserver-typo3-4.0.3-1 conflicts with file from package e-smith-lazy_admin_tools-0.9.1-1

Have installed lazy... thats a part of zoneminder installation.


regards
fpausp

[berdie]

In this case you should use the additional --force command.

Rgds.
Dietmar

[mrjhb3]

In this case you should use the additional --force command.

Rgds.
Dietmar

I don't think you should require people to use the force option to install this rpm.  Why have you included the lat-ibays man page with your rpm?  If your rpm required the LAT, then include a section in your rpm that says requires.  The latest LAT info is in my contribs directiory.

John

[berdie]

Thank you John, you're right.
I'll correct this.

Dietmar

[berdie]

New version without lat-ibays can be download from here:

http://sudemo.info/sme/sme7/webapp/typo3/smeserver-typo3-4.0.3-2.noarch.rpm

Dietmar

[miroj]

Installation of the RPM has passed without problems, but after installation I have a problem to insert a new page or any content to it.

It shows an error that it can't find a field into a table, or something like that.

Anyone having the same problem or any clue what could be the problem?

Thanks.

----

I'm using SMS 7.0 with all available updates and a small number of add-ons, but I don't think that they are causing any problem.

[cromeu]

It's a typo3 error , you must upgrade typo3 with  4.0.4 version  and all is correct.

[miroj]

Thanks.

Should I wait for new RPM from Dietmar or I can just "overwrite" the 4.03 installation with 4.04 sources from typo?

Is any changes in the MySQL database files? Do I have to recrete the database?

Thanks again.

[cromeu]

When you upgrade typo3 , at the end you must use TYPO3 INSTALL TOOL and run the database analyser with the COMPARE option. TYPO3 change the typo3 database  with SQL statment like ALTER TABLE.
We can note that typo3user dont have ALTER PRIVILEGES so you must with phpmyadmin add ALTER autorisation.

I am sorry  for my english !!!

Be carreful !

see this link in french :  
http://www.typo3journal.com/home/installation-typo3/mise-a-jour-typo3.html  


Christophe

thanks Dietmar for the rpm.

[berdie]

New version based on Typo3-4.0.4 is here available:
http://sudemo.info/sme/sme7/webapp/typo3/smeserver-typo3-4.0.4-1.noarch.rpm

I have changed some things:
- Add privileges INDEX and ALTER for the typo3user
- Change location for httpd.conf fragment

Rgds.
Dietmar

[SoftDux]

Hi berdie

I like what you have done, but would like to make a special request.

Is it possible to have typo3 installed into the Primary ibay instead, or even another iBay, which I can then manually update as the primary one. Reason? It makes it easier for backup & disaster recovery purposes if it's installed in an ibay and not /opt

[cactus]

Hi berdie

I like what you have done, but would like to make a special request.

Is it possible to have typo3 installed into the Primary ibay instead, or even another iBay, which I can then manually update as the primary one. Reason? It makes it easier for backup & disaster recovery purposes if it's installed in an ibay and not /opt

AFAIK all content is stored in the MySQL database, so reinstalling and importing this backup should have your site up and running. RPMs should never install into ibays.

I don't think setting it up in the ibay makes backup easier, the only difference is that it might be included in almost all default backup jobs, but ho hard is it to include another directory like /opt?

[SoftDux]

cactus, thank you for the reply, but due to very very frequent reinstallations on the system with 4x 250GB HDD's, I live off backups these days. And I'd prefer not to backup the /opt for varius obvious reasons.

If it's an in ibay, then I know it's going to get backed up.

The fact that it's an rpm, merely means it's an easy to use package. Instead of using the tarball from their website, the use who setup the rpm already went through all the trouble of figuring out how it works. I was just hoping he would share in his knowledge on this. I actually use phpMyAdmin in this way. Then I know it's always backed up, and there when I need it, after a restore. Do you know how much time it takes to reinstall every contrib I have, just cause it's installed in /opt? Restoring 160GB over USB is already a pain in the neck, but I have to, since we have frequent blackouts, which simply leaves my machine unbootable afterwards

[cactus]

cactus, thank you for the reply, but due to very very frequent reinstallations on the system with 4x 250GB HDD's, I live off backups these days. And I'd prefer not to backup the /opt for varius obvious reasons.

Well to me it is not that obvious as it might be to you. I see no reason not to backup (part of) /opt.

If it's an in ibay, then I know it's going to get backed up.

Including another directory in a backup schedule is way less work than rebuilding everything to install in an ibay. To me it looks like you are using work around to fix the actual problem.

Do you know how much time it takes to reinstall every contrib I have, just cause it's installed in /opt?

Not that much I think if you keep the RPMs in some sort of backup location as well, you just need to execute yum localinstall *.rpm then.

I think you need to rethink your backup solution. AFAIK installing contribs is quite simple, painless and quick. I fyou backup the data they generate (files, (mysql) database etc) you only have to reinstall contribs and restore the files or the (mysql) database. This saves you in backup data size as you only need to backup the data you need.

Restoring 160GB over USB is already a pain in the neck, but I have to, since we have frequent blackouts, which simply leaves my machine unbootable afterwards

This leaves me wondering again. Why are you not investing in proper backup solutions as well as fixing the reason of the blackouts or reduce the burden of them on your server by installing UPS or some sort of backup power solution over restoring your server over and over again? In my opinion a server should be reliable and have high availability/uptime and run unattended without to much administration so doing a restore time and time again is certainly not a way I would choose.