#installation script

Laravel 4.2 Installer – Installation Script (Help and Support Tools)

Purchase $12.00 Laravel 4.2 Installer is the perfect solution to install Laravel application, with this “tool” you don’t need to worry about spending extra time on coding and perfecting user friendly installation wizard so you can focus more on your product than anything else. Laravel 4.2 Installer does not require you to make any changes in your own software, what you need is to insert a single…

Laravel 4.2 Installer – Installation Script (Help and Support Tools)

Purchase $12.00 Laravel 4.2 Installer is the perfect solution to install Laravel application, with this “tool” you don’t need to worry about spending extra time on coding and perfecting user friendly installation wizard so you can focus more on your product than anything else. Laravel 4.2 Installer does not require you to make any changes in your own software, what you need is to insert a single…

New Post has been published on http://mocco.sk/using-solr-with-typo3-on-debian-wheezy/

Using Solr With TYPO3 On Debian Wheezy

Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Follow me on Twitter Last edited 05/06/2013

TYPO3′s default search extension called “Indexed Search” is fine for small web sites, but if your web site is bigger (> 500 pages), it is getting very slow. Fortunately, you can replace it with a search extension that uses the ultra-fast Apache Solr search server. This tutorial explains how to use Apache Solr with TYPO3 on Debian Wheezy.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

In this tutorial I’m using two servers:

server1.example.com (IP: 192.168.0.100): web server where the TYPO3 4.7 Introduction package is installed (in the www.example.com vhost).

server2.example.com (IP: 192.168.0.101): separate server where I will install Apache Solr.

Of course, it’s possible to install Solr on the same system as the web server; however, I’d like to split up both services so that they do not impact each other’s performance.

2 Installing Solr

server2.example.com:

First install Java:

apt-get install openjdk-6-jdk openjdk-6-jre unzip

update-alternatives –config java update-alternatives –config javac

The TYPO3 project provides a Solr installation script which we download as follows:

wget http://forge.typo3.org/projects/extension-solr/repository/revisions/master/raw/resources/shell/install-solr.sh chmod 755 install-solr.sh

Next check what the current Apache Tomcat 6 version is by visiting http://tomcat.apache.org/download-60.cgi. At the time of this writing it was 6.0.37. Now open install-solr.sh…

vi install-solr.sh

… and make sure that the TOMCAT_VER variable holds the correct version number – if necessary, change it:

[...] TOMCAT_VER=6.0.37 [...]

Now we install Solr. By default (if you don’t provide any languages as parameters), Solr is installed with support for the English language only; if you need support for more languages, just append them to the command, e.g. like this:

./install-solr.sh german english french

This installs a Tomcat server (where Solr is run on) and Solr. By default, Tomcat listens on 127.0.0.1 only; because we want to access Solr from a remote host, we must configure Tomcat to listen on all interfaces, therefore we replace 127.0.0.1 with 0.0.0.0 in /opt/solr-tomcat/tomcat/conf/server.xml:

vi /opt/solr-tomcat/tomcat/conf/server.xml

[...] <Connector port="8080" protocol="HTTP/1.1" maxHttpHeaderSize="65536" connectionTimeout="20000" redirectPort="8443" address="0.0.0.0" URIEncoding="UTF-8" /> [...]

Restart Tomcat:

/opt/solr-tomcat/tomcat/bin/shutdown.sh /opt/solr-tomcat/tomcat/bin/startup.sh

Next we can configure cores in Solr. By default, an English core is already configured; if you need more languages, you can add them to /opt/solr-tomcat/solr/solr.xml, e.g. like this:

vi /opt/solr-tomcat/solr/solr.xml

<?xml version="1.0" encoding="UTF-8" ?> <solr persistent="true"> <cores adminPath="/admin/cores" shareSchema="true"> <core name="core_en" instanceDir="typo3cores" schema="english/schema.xml" dataDir="data/core_en" /> <core name="core_de" instanceDir="typo3cores" schema="german/schema.xml" dataDir="data/core_de" /> <core name="core_fr" instanceDir="typo3cores" schema="french/schema.xml" dataDir="data/core_fr" /> </cores> </solr>

Restart Solr afterwards:

/opt/solr-tomcat/tomcat/bin/shutdown.sh /opt/solr-tomcat/tomcat/bin/startup.sh

Because we don’t want to start Tomcat manually each time the server is booted, we can add the Tomcat startup command to /etc/rc.local:

vi /etc/rc.local

[...] /opt/solr-tomcat/tomcat/bin/startup.sh [...]

2.1 Adding Authentication To Solr

Because Solr is listening on all interfaces, it is a good idea to add authentication to it. I will now configure the user user1 with the password secret for the English core.

Open /opt/solr-tomcat/tomcat/conf/web.xml…

vi /opt/solr-tomcat/tomcat/conf/web.xml

… and add the following section somewhere inside the <web-app> container:

[...] <security-constraint> <web-resource-collection> <web-resource-name>Solr authenticated application</web-resource-name> <url-pattern>/core_en/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>role1</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>Admin and Update protection</realm-name> </login-config> [...]

As you see, this is valid for the English core only (<url-pattern>/core_en/*</url-pattern>), and I’ve configured this for the role role1, so valid users must belong to that role. To add the user user1 with his password to that role, open /opt/solr-tomcat/tomcat/conf/tomcat-users.xml…

vi /opt/solr-tomcat/tomcat/conf/tomcat-users.xml

… and add the following section inside the <tomcat-users> container:

[...] <role rolename="role1"/> <user username="user1" password="secret" roles="role1"/> [...]

Restart Tomcat afterwards:

/opt/solr-tomcat/tomcat/bin/shutdown.sh /opt/solr-tomcat/tomcat/bin/startup.sh

You can now open a browser and visit Solr under http://192.168.0.101:8080/solr where you should see all configured cores:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

When you visit the English core (for which we have just configured authentication), you should be asked for a username and a password:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

After successful authentication, you should see the following page which means Solr is running successfully:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

Using Solr With TYPO3 On Debian Wheezy – Page 2

New Post has been published on http://mocco.sk/using-solr-with-typo3-on-debian-squeeze/

Using Solr With TYPO3 On Debian Squeeze

Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Follow me on Twitter Last edited 05/06/2013

TYPO3′s default search extension called “Indexed Search” is fine for small web sites, but if your web site is bigger (> 500 pages), it is getting very slow. Fortunately, you can replace it with a search extension that uses the ultra-fast Apache Solr search server. This tutorial explains how to use Apache Solr with TYPO3 on Debian Squeeze.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

In this tutorial I’m using two servers:

server1.example.com (IP: 192.168.0.100): web server where the TYPO3 4.7 Introduction package is installed (in the www.example.com vhost).

server2.example.com (IP: 192.168.0.101): separate server where I will install Apache Solr.

Of course, it’s possible to install Solr on the same system as the web server; however, I’d like to split up both services so that they do not impact each other’s performance.

2 Installing Solr

server2.example.com:

Open /etc/apt/sources.list…

vi /etc/apt/sources.list

… and make sure you have the contrib and non-free repositories enabled:

deb http://ftp.de.debian.org/debian/ squeeze main contrib non-free deb-src http://ftp.de.debian.org/debian/ squeeze main contrib non-free deb http://security.debian.org/ squeeze/updates main contrib non-free deb-src http://security.debian.org/ squeeze/updates main contrib non-free deb http://ftp.de.debian.org/debian/ squeeze-updates main contrib non-free deb-src http://ftp.de.debian.org/debian/ squeeze-updates main contrib non-free

Update your packages database…

apt-get update

… and install Java:

apt-get install sun-java6-bin sun-java6-jdk sun-java6-jre unzip

update-alternatives –config java update-alternatives –config javac

The TYPO3 project provides a Solr installation script which we download as follows:

wget http://forge.typo3.org/projects/extension-solr/repository/revisions/master/raw/resources/shell/install-solr.sh chmod 755 install-solr.sh

Now we install Solr. By default (if you don’t provide any languages as parameters), Solr is installed with support for the English language only; if you need support for more languages, just append them to the command, e.g. like this:

./install-solr.sh german english french

This installs a Tomcat server (where Solr is run on) and Solr. By default, Tomcat listens on 127.0.0.1 only; because we want to access Solr from a remote host, we must configure Tomcat to listen on all interfaces, therefore we replace 127.0.0.1 with 0.0.0.0 in /opt/solr-tomcat/tomcat/conf/server.xml:

vi /opt/solr-tomcat/tomcat/conf/server.xml

[...] <Connector port="8080" protocol="HTTP/1.1" maxHttpHeaderSize="65536" connectionTimeout="20000" redirectPort="8443" address="0.0.0.0" URIEncoding="UTF-8" /> [...]

Restart Tomcat:

/opt/solr-tomcat/tomcat/bin/shutdown.sh /opt/solr-tomcat/tomcat/bin/startup.sh

Next we can configure cores in Solr. By default, an English core is already configured; if you need more languages, you can add them to /opt/solr-tomcat/solr/solr.xml, e.g. like this:

vi /opt/solr-tomcat/solr/solr.xml

<?xml version="1.0" encoding="UTF-8" ?> <solr persistent="true"> <cores adminPath="/admin/cores" shareSchema="true"> <core name="core_en" instanceDir="typo3cores" schema="english/schema.xml" dataDir="data/core_en" /> <core name="core_de" instanceDir="typo3cores" schema="german/schema.xml" dataDir="data/core_de" /> <core name="core_fr" instanceDir="typo3cores" schema="french/schema.xml" dataDir="data/core_fr" /> </cores> </solr>

Restart Solr afterwards:

/opt/solr-tomcat/tomcat/bin/shutdown.sh /opt/solr-tomcat/tomcat/bin/startup.sh

Because we don’t want to start Tomcat manually each time the server is booted, we can add the Tomcat startup command to /etc/rc.local:

vi /etc/rc.local

[...] /opt/solr-tomcat/tomcat/bin/startup.sh [...]

2.1 Adding Authentication To Solr

Because Solr is listening on all interfaces, it is a good idea to add authentication to it. I will now configure the user user1 with the password secret for the English core.

Open /opt/solr-tomcat/tomcat/conf/web.xml…

vi /opt/solr-tomcat/tomcat/conf/web.xml

… and add the following section somewhere inside the <web-app> container:

[...] <security-constraint> <web-resource-collection> <web-resource-name>Solr authenticated application</web-resource-name> <url-pattern>/core_en/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>role1</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>Admin and Update protection</realm-name> </login-config> [...]

As you see, this is valid for the English core only (<url-pattern>/core_en/*</url-pattern>), and I’ve configured this for the role role1, so valid users must belong to that role. To add the user user1 with his password to that role, open /opt/solr-tomcat/tomcat/conf/tomcat-users.xml…

vi /opt/solr-tomcat/tomcat/conf/tomcat-users.xml

… and add the following section inside the <tomcat-users> container:

[...] <role rolename="role1"/> <user username="user1" password="secret" roles="role1"/> [...]

Restart Tomcat afterwards:

/opt/solr-tomcat/tomcat/bin/shutdown.sh /opt/solr-tomcat/tomcat/bin/startup.sh

You can now open a browser and visit Solr under http://192.168.0.101:8080/solr where you should see all configured cores:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

When you visit the English core (for which we have just configured authentication), you should be asked for a username and a password:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

After successful authentication, you should see the following page which means Solr is running successfully:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

Using Solr With TYPO3 On Debian Squeeze – Page 2

Full Script Available at AKT Developments

  One of the best uses of windows scripts is for installation and login scripts. Being able to dynamically create shortcuts on the fly, based on who is logged in or on what machine, etc. allows a system administrator to easily manage their systems and to provide usability directly to the user. This article will cover some of the basics of scripting and show how easy it is to create a shortcut via windows scripting, utilising the vbscript language.

This script was written to aid in making manula installations easier and assumes that the files are already on the machine, but could be easily adapted for making a installation script that automatically adds the shortcut at the end of the installation.

  Firstly we need to create a new shell object so that we can interact with the windows operating system and give windows commands to complete.

  Next we create two string values and assign them the input from a user dialog. The 'Inputbox' command shows the user a dialog box which has a text box that the user can fill in. The two values seperated by a comma are the 'message' the user sees in the dialog box, and the 'title' of the dialog box respectively.

Line 6 is getting the 'windows special folder' path of the 'all users desktop' folder. We could put in the direct path (usually something like "C:\Documents and Settings\All Users\Desktop\") as a string but if windows is not installed on C: drive or your using windows seven and windows xp installation your script is either going to put the file somewhere obscure or not be able to write the file and crash. So using windows to find the file path is alot easier to maintain and works better on more systems, and also makes you script usable on future versions of windows.

  Next is the actual creation of the shortcut. 

  And the shortcut is created!

We can now send a message to the user telling them the shortcut is created and quit the script, or if the script is part of an installation we could continue with other processes.