Tips & Tricks : Apache2 autostart on openSUSE 13.1


In order to have Apache2 started automatically after reboot use:

systemctl enable apache2.service


How-To : Deploy VisualEditor extension for MediaWiki 1.24.2 on openSUSE 13.1 x64


In previous article I described how-to Deploy Parsoid on openSUSE 13.1 (which turns out to be quite a challenging task). Parsoid is component required for VisualEditor. Now it’s time for VisualEditor deployment.

Downloading VisualEditor

At the moment, when I’m doing deployment, stable version of MediaWiki is 1.24.2. VisualEditor is an extension written for certain version of MediaWiki, hence we can’t just download latest version and use it. It has to be specific release for specific MediaWiki version.

So, first we download VisualEditor for MediaWiki 1.24.2:

git clone -b REL1_24 https://github.com/wikimedia/mediawiki-extensions-VisualEditor.git
cd mediawiki-extensions-VisualEditor/
git submodule update --init

Once it’s done we need to place content of mediawiki-extensions-VisualEditor in extensions/VisualEditor folder under MediaWiki folder structure.

Finally, once we have all files in proper places it’s time to inform MediaWiki about VisualEditor.

Changes to LocalSettings.php

Changes which have to be applied to LocalSettings.php:

# VISUAL Editor
$wgDefaultUserOptions['visualeditor-enable'] = 1;
$wgHiddenPrefs[] = 'visualeditor-enable';
$wgVisualEditorParsoidURL = 'http://localhost:8000';
$wgVisualEditorParsoidPrefix = 'localhost';
Remember to adjust Parsoid URL and Prefix accordingly to setup of your Parsoid service.

From now on you can enjoy VisualEditor until you decide to upgrade to newer version of MediaWiki.
Prior to that I would suggest to check if there is VisualEditor available for new release and test it prior to live deployments.


How-To : Deploy Parsoid for MediaWiki on openSUSE 13.1 x64


I took a challenge of running MediaWiki with Visual Editor extension on openSUSE 13.1 x64. Task sounds maybe easy, but turned out to be little madness, so once I got this working I think it might be nice to share my steps.

Operating system has been deployed from ISO image: openSUSE-13.1-NET-x86_64.iso.

Installing Node.js

Basically Node.js package which is included in distro doesn’t work properly. For that reason first step is to add new repository for Node.js:

sudo zypper ar http://download.opensuse.org/repositories/devel:/languages:/nodejs/openSUSE_13.1/ Node.js
sudo zypper in nodejs nodejs-devel
yast -i nodejs


Updating NPM

Once Node.js is installed it’s not quite fully working yet and any attempt of using npm fails. Some symlinks are missing, so to fix it we can just update npm:

curl -L https://npmjs.org/install.sh | sudo sh


Parsoid deployment

Now we can download Parsoid and make it work:

cd /srv
git clone https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid
cd parsoid
npm install
npm test
npm start
Parsoid will be located in /srv/parsoid folder. Do not forget to modify /srv/parsoid/api/localsettings.js for your system.

This is quite brief description, however saves lot of time and fight with Node.js and npm on openSUSE.




Tips & Tricks : Configure Apache on Debian 7 for RT4


Once Request Tracker 4 is installed on Debian 7, there is one more thing to do.

Small change in Apache configuration to make RT4 website to work.

First edit Apache configuration file:

root@hostname:~# vi /etc/apache2/sites-available/default

Then add to that file (at the end):

Include /etc/request-tracker4/apache2-modperl2.conf
RedirectMatch ^/$ /rt

TIps & Tricks : Searching for packages in Debian


If you want to install some packages on Debian and don’t know names of packages you can search in packages cache.

For example if you want to see all packages related to MySQL:

root@hostname:~# apt-cache search mysql
akonadi-backend-mysql - MySQL storage backend for Akonadi
ampache-themes - Themes for Ampache
aolserver4-nsmysql - AOLserver 4 module: module for accessing MySQL databases
libapq3.2.0 - Pluggable Ada 95 Binding to various database systems (library)
libapq3.2.0-dbg - Pluggable Ada 95 Binding to various database systems (debug)
libapq3.2.0-dev - Pluggable Ada 95 Binding to various database systems (development)
libaprutil1-dbd-mysql - Apache Portable Runtime Utility Library - MySQL Driver
asterisk-mysql - MySQL database protocol support for the Asterisk PBX
audiolink - makes managing and searching for music easier
auth2db - Powerful and eye-candy IDS logger, log viewer and alert generator
auth2db-common - Common configuration files for Auth2db backend and web frontend
auth2db-filters - Auth2db defaults filters pack
auth2db-frontend - Web frontend view for auth2DB log engine
automysqlbackup - daily, weekly and monthly backup for your MySQL database
autopostgresqlbackup - Automated tool to make periodic backups of PostgreSQL databases
backup-manager - command-line backup tool
backupninja - lightweight, extensible meta-backup system
bacula-common-mysql - network backup service - MySQL common files
bacula-common-mysql-dbg - network backup service - MySQL common files (debugging)
bacula-director-mysql - network backup service - MySQL storage for Director

Tips & Tricks : Session log files in SecureCRT


I use SecureCRT quite often to access Linux systems as well as network devices.

When going through one of the presentations on SecureCRT web page I found handy tip how to configure session logs to have it divided by date, time and session.

Screenshot below demonstrates settings for log file:

SecureCRT Log File configuration

Basically parameters are set to:

  • Log file name: %Y-%M-%D–%h-%m-%s.%t__%S(%H).txt
  • Options / Start log upon connect: checked
  • Custom log data / On each line: %h:%m:%s(%t):

These settings will create separate log file for each session every time connection will be established.

In addition to that each line will start with timestamp added by SecureCRT.

Page 4 of 6« First...23456