Category Archives: HowTo

By Vivian Morales [CC-BY-2.0 (http://creativecommons.org/licenses/by/2.0)], via flickr

openSUSE Upgrade 13.1

… because my recent topic “moving”, now something completely different! Well, not really … it’s similar … an operating-system upgrade …

… just a simple openSUSE Upgrade …

In the aftermath of Heartbleed bug, which showed that it is sometimes not a bad thing to be not up to date and only apply security patches, we had to upgrade a openSUSE system from version 12.3 to 13.1. While version 12.3 is still supported, version 13.1 is available since November last year, so it was not that unreasonable to update now. Five months should be enough time to fix all quirks and bugs of a new version … you might think …

The upgrade was smooth, the server rebooted without problems … then our monitoring system started delivering error reports 😉

Apache

… was not running at all because it had not been started at boot time, no problem there:
Continue reading openSUSE Upgrade 13.1

Facebooktwittergoogle_plusredditpinterestlinkedintumblrmailFacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

Flattr this!

Malte Schmidt at the German language Wikipedia [CC-BY-SA-3.0 (http://creativecommons.org/licenses/by-sa/3.0), CC-BY-SA-3.0-de (http://creativecommons.org/licenses/by-sa/3.0/de/deed.en) or GFDL (http://www.gnu.org/copyleft/fdl.html)], via Wikimedia Commons

How-To Update phpList

phpList an open-source newsletter manager, with lots of features – the best of them: it’s free …

… like with Tiny Tiny RSS, when you install phpList on your own server, you need to keep the software up to date.

How you are going to update depends strongly, on how you have installed the software. Let’s assume the source code is installed outside the web root and is symbolically linked to.
Continue reading How-To Update phpList

Facebooktwittergoogle_plusredditpinterestlinkedintumblrmailFacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

Flattr this!

Bundesarchiv, Bild 183-V08147 / Marquardt / CC-BY-SA [CC-BY-SA-3.0-de (http://creativecommons.org/licenses/by-sa/3.0/de/deed.en)], via Wikimedia Commons

How-To update Tiny Tiny RSS

In Summer this year Google discontinued the Google Reader – a free service to collect various RSS streams and to view them online. Tiny Tiny RSS is an open-source software which provides the same functionality on your own (local) server. It requires PHP and MySQL, is quite easy to install and allows even to import data from Google Reader …

… however running the reader on your own server – even if it provides “more” privacy – requires keeping the software up to date.

How to update Tiny Tiny RSS?

First backup your current installation as well as the database.

Let’s say your current installation version 1.9 is at ttrss, just create a copy of that directory naming it with the “old” version number. Why? If something goes wrong, you want to go back to the current – working – installation.

cp -rp ttrss ttrss-1.9

database backup using phpMyAdminTo create a backup of your current database use your favorite tool, e.g. phpMyAdmin

or by command line

mysqldump -u [db-username] -p ttrss > ttrss-1.9.sql

For the actual update, you could download the new version and do a manual update, but there is a more convenient way. Let it do Tiny Tiny RSS itself:

cd ttrss; php -q update.php --update_self

This will download the new version, (create a copy of the current version – which we actually do not need because we created a backup above).

The current version also fixes the permissions on the cache folder, but seems missing the upload folder which it will tell you when opening the online interface the next time. Just change it yourself e.g.

chmod -R 707 cache/upload/

Now open the online interface in your browser, the software will run an update on your database … done

Facebooktwittergoogle_plusredditpinterestlinkedintumblrmailFacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

Flattr this!

By nathanmac87 (Confetti Uploaded by Anastasiarasputin) [CC-BY-2.0 (http://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons

Adding Snippets to Eclipse

The problem:

You want/need to add/use the same code pieces again and again

You could just copy and paste, which becomes tedious when you have different pieces …

… or you could yous the snippets plugin which you can access via

 -> Window -> Show View -> Other … -> General -> Snippets

… if it is not already there, install it. Go to

-> Help -> Install New Software …

choose the site of your current eclipse version and select inside

Web, XML, Java EE and OSGi Enterprise Development

the plugin

Eclipse Web Developer Tools

Click all the necessary “next”, “I agree”, and “finish” buttons … finally restart eclipse …

Add new snippets using the right mouse button and selecting “cusotmize”.

Facebooktwittergoogle_plusredditpinterestlinkedintumblrmailFacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

Flattr this!

By Sebastian Hartlaub (Own work) [CC-BY-SA-2.5 (http://creativecommons.org/licenses/by-sa/2.5)], via Wikimedia Commons

Apache with Security Enhanced Linux (SELinux)

From Quick HOWTO : Ch20 : The Apache Web Server:

Fedora Core 3 introduced the concept of security contexts as part of the Security Enhanced Linux (SELinux) definition. A Web page may have the right permissions, but the Apache httpd daemon won’t be able to read it unless you assign it the correct security context or daemon access permissions. Context-related configuration errors will give “403 Forbidden” browser messages, and in some cases, you will get the default Fedora Apache page where your expected Web page should be.

… to view the security context:

ls -Z

… to set web context for the current folder and its sub folders:

chcon -R -h -t httpd_sys_content_t .
Facebooktwittergoogle_plusredditpinterestlinkedintumblrmailFacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

Flattr this!

By Benreis (Own work) [GFDL (http://www.gnu.org/copyleft/fdl.html) or CC-BY-3.0 (http://creativecommons.org/licenses/by/3.0)], via Wikimedia Commons

Vacation message using procmail

If you use procmail to filter messages, you can use it also to setup a vacation email response:

  1. Create a file called vacation.txt and fill it with your “vacation message”.
  2. Create a file called vacation.rc fill it with the following commands (and don’t forget to adjust the values for USER, DOMAIN, and PATHxxx to your needs):
:0 Whc: vacation.lock
* .*for <USER@DOMAIN>
* !^FROM_DAEMON
* !^X-Loop: USER@DOMAIN
| formail -rD 8192 vacation.cache
:0 ehc
| (formail -rA”Precedence: junk (autoreply)”
-A”X-Loop: USER@DOMAIN” ;
cat PATHTOVACATIONMESSAGE/vacation.txt
) | PATHTOSENDMAIL/sendmail -oi -t
  1. Find your .procmailrc file and add the following line after your filter commands (again adjust the PATH):
#INCLUDERC=PATHTORCFILE/vacation.rc

If you receive an email at USER@DOMAIN and it is not filtered out by your spam filter, the vacation commands are activated. It checks if the email is for you, does not originate from a mailing list, and has not been processed before. It also creates a file called vacation.cache, where it stores the email addresses to which a vacation message has already been sent, in order to do not send such a message again (don’t forget to delete it when you deactivate the vacation filter). At last it replies with the message stored in vacation.txt.

The “Precedence: junk (autoreply)” part helps to avoid bouncing messages from other MTAs.

Facebooktwittergoogle_plusredditpinterestlinkedintumblrmailFacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

Flattr this!

By luiscurse [CC-BY-SA-3.0 (http://creativecommons.org/licenses/by-sa/3.0/)], via deviantART

Wonders of Typo3

A lot of people complain about Typo3. They say it is too heavy for a CMS. They may be right, it is complex and it takes some time to get used to it. But it pays!

Today a customer complained, that one of his pages in Typo3 was missing completely. He was right, it was not there any more. What happened? One of his employees accidentally deleted the wrong page … Which is not really a problem of Typo3. If you delete it, it is gone. It does not matter which system you are using … Well, problem for Typo3.

Unfortunately, content versioning was disabled, which made it a little bit more work:

  • open the database
  • find the page (write down the pid)
  • change deleted from 1 to 0
  • repeat those steps for all content entries with that pid
  • return to the administrator of Typo3
  • move the page to its correct location
  • reposition the content inside the page

… done in 5 minutes … with content versioning enabled it would have been a simple click …

Facebooktwittergoogle_plusredditpinterestlinkedintumblrmailFacebooktwittergoogle_plusredditpinterestlinkedintumblrmail

Flattr this!