Hetzner - DokuWiki

Installation gängiger Software (Managed Server)/en


Customers install and use the following programs at their own risk. The user is not granted the right to support services related to these programs. If customers have questions regarding KonsoleH or about server configurations, we will be happy to assist them.


Inhaltsverzeichnis

PEAR

Having your own PEAR is sometimes necessary, for example, when you would like to install your own PEAR packages without any fuss or if you would like to use a version of PHP which is does not support the PEAR version on the server.

Requirements

Pre-Installation

  • [REQUIRED] SSH access (Webhosting Level 19 or all managed servers)

This guide describes the process using SSH access and assumes that you already are connected via SSH using your access details.

PEAR Setup:

wget http://pear.php.net/go-pear.phar
php go-pear.phar

Change the following entries for the installation (LOGIN = FTP login for the account):

2. Temporary directory for processing            : /usr/home/LOGIN/.tmp
3. Temporary directory for downloads             : /usr/home/LOGIN/.tmp

When you are asked if the php.ini should be changed, choose [n].

Set the PATH variable so you can use the local PEAR

echo 'export PATH="~/pear/bin:$PATH"' >> ~/.bashrc
echo 'export PHP_PEAR_PHP_BIN="/usr/bin/php"' >> ~/.bashrc
source ~/.bashrc

(Note: The path /usr/bin/php always points to the newest version of PHP available on the server. If you would like to use a specific version of PHP, edit the path, for example PHP 5.5 => /usr/bin/php55 )

Use PEAR

pear

List packages

pear list-all

Install new packages

pear install <package>

Using your own PEAR in PHP scripts

Annotate the .htaccess file:

php_value include_path /usr/home/LOGIN/pear/share/pear/:.:/usr/local/lib/php/

Composer

Requirements

Pre-Installation

  • [REQUIRED] SSH access (Level 19 or managed servers)

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Composer setup:

With the commands below, you can download the newest version and validate the signature. An important parameter on our managed servers is "-d allow_url_fopen=On". Without this, you will get error messages.

php -d allow_url_fopen=On -r "readfile('https://getcomposer.org/installer');" > composer-setup.php
php -d allow_url_fopen=On composer-setup.php
php -r "unlink('composer-setup.php');"

Using Composer:

php -d allow_url_fopen=On composer.phar

Sources

https://getcomposer.org/

https://getcomposer.org/download/


NewRelic Sysmond

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed servers)

Post-Installation

  • [REQUIRED] Request approval to use "nrsysmond". Please open a support request via the customer interface KonsoleH to get permission to use "nrsysmond".
  • [REQUIRED] To use Sysmond, you will need a license key, which you can get from the New Relic operators at newrelic.com.

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Download and extract the installation files (SSH)

First, select the desired directory. This can be the home directory for the account (/usr/home/<USERNAME>/). Insert the version number into the format X.X.X.XXX (for example: 2.3.0.129).

wget -O- https://download.newrelic.com/server_monitor/release/newrelic-sysmond-X.X.X.XXX-linux.tar.gz > newrelic.tar.gz
tar xzf newrelic.tar.gz

Structure the package files

mkdir sysmon
mkdir sysmon/log
touch sysmon/log/nrsysmond.log
mv newrelic-sysmond-X.X.X.XXX-linux/daemon/nrsysmond.x64 sysmon/nrsysmond
mv newrelic-sysmond-X.X.X.XXX-linux/nrsysmond.cfg sysmon/nrsysmond.cfg

Modify the configuration file nrsysmond.cfg

The lines with "license_key=" and "logfile=" should be modified along the following lines:

license_key=<YOUR LICENSE KEY>
logfile=/usr/home/<USERNAME>/sysmon/log/nrsysmond.log

Start daemon

/usr/home/<username>/sysmon/nrsysmond -c /usr/home/<username>/sysmon/nrsysmond.cfg

@reboot Cronjob

You will need to set up a cronjob so that the daemon will not have to be manually started after the server has been restarted. To do this, go to KonsoleH and select the desired account domain. Then go to the menu "Services"->"Cronjob manager"->"Advanced view". Then insert the following lines at the end and, finally, click on "Save":

@reboot /usr/home/<USERNAME>/sysmon/nrsysmond -c /usr/home/<USERNAME>/sysmon/nrsysmond.cfg

Source

https://discuss.newrelic.com/t/how-do-i-install-and-run-the-server-monitor-without-root-privileges/270


node.js

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed servers)

Post-Installation

  • [OPTIONAL] You will also need approval to use "node" if you intend on running a "node" process for an extended period of time. You can request us to provide one of these to you by sending a support request via the user interface KonsoleH.

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Installation

Create a directory for the installation:

mkdir nodejs
cd nodejs

Download the current binaries (You need to replace the X with the downloaded version number.):

wget https://nodejs.org/download/release/latest/node-vX.X.X-linux-x64.tar.gz

You need to determine the exact download link by going to the website nodejs.org/download. (For example: https://nodejs.org/download/release/latest/node-v8.1.2-linux-x64.tar.gz)

Extract binaries:

tar -xzf node-vX.X.X-linux-x64.tar.gz

Customize .bashrc

echo 'export PATH=/usr/home/<USERNAME>/nodejs/node-vX.X.X-linux-x64/bin:${PATH}' >> ~/.bashrc

To make the .bashrc settings work - please restart your SSH session.

Use node.js

/usr/home/<USERNAME>/node/bin/node YourScript.js

or:

node YourScript.js

The second variant is only possible with entries in the .bashrc file.

Source

https://nodejs.org/


Redis

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed servers)
  • [REQUIRED] A compiler is required for Redis. You can request us to provide one of these to you by sending a support request via the user interface KonsoleH. Please ask for the Hetzner Development Package (hos-dev)

Post-Installation

  • [OPTIONAL] Request that we add "redis-server" to the configuration of our process monitoring system. Please write a support ticket via the user interface KonsoleH.
  • [OPTIONAL] Request an open port (optional; standard port 6379) - Please request an open port by sending a support request via the user interface KonsoleH. If you have changed the port in the file "redis.conf", please enter your port in place of the default value in your support request. Please note that additional open ports are generally not necessary and represent a considerable safety risk!

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Download and extract Redis

First, please select the project directory in which you would like to install Redis.

wget http://download.redis.io/releases/redis-stable.tar.gz
tar xzf redis-stable.tar.gz
cd redis-stable

Installation

Enter the following commands in this order for the installation:

make
make test
cd src
chmod ug+x redis-server

Start Redis

./redis-server

You can start this in a screen session, or you can start the command in the background:

./redis-server &

Check that Redis is running

./redis-cli

The output of the prompt has now changed to "redis 127.0.0.1:6379>". If you enter a "ping", you should receive a "pong" in return if Redis is running properly.

Redis-CLI: Example for how to manually set a key

redis 127.0.0.1:6379> set mykey somevalue
OK
redis 127.0.0.1:6379> get mykey
"somevalue"

@reboot Cronjob

You will need to set up a cronjob so that the daemon will not have to be manually started after the server has been restarted. To do this, go to KonsoleH and select the desired account domain. Then go to the menu "Services"->"Cronjob manager"->"Advanced view". Then insert the following lines at the end and, finally, click on "Save":

@reboot /usr/home/<USERNAME>/redis-stable/src/redis-server

If necessary, adjust the path to match yours.

Hint

As a key value databank (NoSQL), which is used to store data in RAM, Redis can be an good alternative to using "Memcached".

Source and helpful links

http://redis.io

http://devdocs.magento.com/guides/m1x/ce18-ee113/using_redis.html (Use Redis with Magento)

https://github.com/nrk/predis (Redis Client)

https://wordpress.org/plugins/redis-cache/ (Wordpress Plugin - Redis Object Cache)


Elasticsearch

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed servers)

Post-Installation

  • [OPTIONAL] Request that we add "java" to the configuration of our process monitoring system. Please write a support ticket via the user interface KonsoleH.
  • [OPTIONAL] Request an open port (standard port 9200) - Please request an open port by sending a support request via the user interface KonsoleH. If you have changed the port, please enter your port in place of the default value in your support request. Please note that additional open ports are generally not necessary and represent a considerable safety risk!

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Download and install

Download link from: https://www.elastic.co/de/downloads/elasticsearch

mkdir elasticsearch
cd elasticsearch
curl -L -O https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-X.Y.Z.tar.gz
tar xvf elasticsearch-X.Y.Z.tar.gz

If necessary, please replace the version number (X.Y.Z) with the number of your preferred version, preferably with the most recent version number. The download URL, path names, and file names may thus vary.

Start Elasticsearch

cd elasticsearch-X.Y.Z/bin/
./elasticsearch

Test Elasticsearch

curl 'localhost:9200/_cat/indices?v'

If Elasticsearch is successfully running, then it will output the following:

health status index pri rep docs.count docs.deleted store.size pri.store.size

This output means that we don't have any indexes in this cluster yet.

Sources

https://www.elastic.co

https://www.elastic.co/guide/en/elasticsearch/reference/


GlassFish

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed servers)

Post-Installation

  • [OPTIONAL] Request that we add "java" to the configuration of our process monitoring system. Please write a support ticket via the user interface KonsoleH.
  • [OPTIONAL] Request an open ports for ports 4848 and 8080 - Please request an open port by sending a support request via the user interface KonsoleH. Please note that additional open ports are generally not necessary and represent a considerable safety risk!

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Download and extract

wget http://download.java.net/glassfish/4.1.1/release/glassfish-4.1.1.zip
unzip glassfish-4.1.1.zip
cd glassfish4
wget https://glassfish.java.net/downloads/quickstart/hello.war

If necessary, please switch out the download link to obtain the most current version of GlassFish.

Start GlassFish

cd bin
./asadmin start-domain

GlassFish testen

./asadmin deploy ../hello.war

You should see the following output:

Application deployed with name hello.
Command deploy executed successfully.

Alternatively, you can access "<your-domain.tdl>:8080" in your browser, and you will receive a reply when the process is running.

Administrator web interface

The web interface administrator is optional. It is deactivated due to security concerns and must be activated when it is required. To do this, you must first create a password (and a user):

./asadmin change-admin-password

The standard user is "admin", and no password is provided. After the last command, a password is provided, and with that you can access the web interface:

./asadmin enable-secure-admin

You will be asked to enter the user and password that you have just finished creating. Then you will be able to use the web interface administrator.

Source

https://glassfish.java.net/


MongoDB

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed servers)

Post-Installation

  • [OPTIONAL] Request that we add "mongod" to the configuration of our process monitoring system. Please write a support ticket via the user interface KonsoleH.
  • [OPTIONAL] Request an open port/port forwarding (optional) Please note that additional open ports are generally not necessary and represent a considerable safety risk!

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Installation

 Note: Please replace the version numbers X.Y.Z with the version you want to install.
curl -O https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-X.Y.Z.tgz
tar xvf mongodb-linux-x86_64-X.Y.Z.tgz
mv mongodb-linux-x86_64-X.Y.Z mongodb
rm -f mongodb-linux-x86_64-X.Y.Z.tgz
cd mongodb

Start MongoDB

You can start MongoDB as a daemon (which will run in the background) using the following command. You can omit the parameter "--port" if the databank will only be used locally.

./bin/mongod --dbpath /usr/home/<USERNAME>/mongodb/data/db/ --port 27017 --fork --logpath /usr/home/<USERNAME>/mongodb/log.txt

(The command must be all one line.)

Alternative:

./bin/mongod --dbpath /usr/home/<USERNAME>/mongodb/data/db/

Test MongoDB

./bin/mongo

If this can be successfully started, then the installation was also performed successfully. You now have a shell similar to what is available with databank systems like MySQL. You can use the command "exit" to leave this program.

Sources

https://docs.mongodb.com/manual/tutorial/install-mongodb-on-linux/

https://docs.mongodb.com/manual/mongo/

https://www.mongodb.com/mongodb-security-best-practices

https://github.com/mongodb/mongo/blob/master/rpm/mongod.conf (Examples of configurations)


FFmpeg

Requirements

Pre-Installation

  • [OPTIONAL] SSH access (managed servers) - SSH access is not entirely necessary. It is possible to also do the installation via FTP.

Post-Installation

  • [OPTIONAL] Request approval - This is only necessary if you plan on processing very large files.

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Download and extract FFmpeg

 Note: Replace X.Y with the version you want to install
wget http://johnvansickle.com/ffmpeg/releases/ffmpeg-release-64bit-static.tar.xz
tar xJf ffmpeg-release-64bit-static.tar.xz
mv ffmpeg-X.Y-64bit-static ffmpeg

Use FFmpeg

Examples of command lines/commands:

./ffmpeg/ffmpeg -i MeinLied.mp3 MeinLied.wav
./ffmpeg/ffmpeg -i MeinVideo.avi MeinVideo.mp4

Installation via FTP (without SSH)

  1. Start downloading the static builds from http://johnvansickle.com/ffmpeg/ (64-bit Linux) onto your local computer.
  2. You need to extract the downloaded file before you do the upload. To extract the .tar.xz file, we recommend that you use the program at 7-Zip.
  3. Using WebFTP (KonsoleH) or another FTP program (for example, FileZilla), upload the necessary binaries (for example, ffmpeg) onto the server.
  4. You need to set the permissions for the uploaded files to "755" using Filezilla or WebFTP, for example.
  5. You can now include the downloaded scripts in your programming.

Source

http://johnvansickle.com/ffmpeg/


Apache-Tomcat

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed servers)

Post-Installation

  • [OPTIONAL] Request an open port for the port that you have configured - Please request an open port by sending a support request via the user interface KonsoleH. Please note that additional open ports are generally not necessary and represent a considerable safety risk!
  • [OPTIONAL] Request that we add "java" to the configuration of our process monitoring system. Please write a support ticket via the user interface KonsoleH.

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Download und Installation

You need to use binary core code in .tar.gz format because a Linux Debian system will be running. The current download link is available at: tomcat.apache.org/download-90.cgi Please replace <VERSION> in the following steps with the version you have downloaded.

wget http://mirror.netcologne.de/apache.org/tomcat/tomcat-9/<VERSION>/bin/apache-tomcat-<VERSION>.tar.gz
tar -xzf apache-tomcat-<VERSION>.tar.gz
mv apache-tomcat-<VERSION> tomcat

If you adjust "bashrc", you will prevent long paths. To do this, open the file ".bashrc" with an editor or your choice. For example:

nano .bashrc

Insert the following line and save the file:

export CATALINA_HOME='/usr/home/<USERNAME>/tomcat/'
export JAVA_HOME='/usr/'
alias tomcat_start='$CATALINA_HOME/bin/startup.sh'
alias tomcat_stop='$CATALINA_HOME/bin/shutdown.sh'

In order to implement these changes, you will need to disconnect the SSH connection once (log out) and then start a new connection.

Start Tomcat

tomcat_start

To test whether Tomcat is running, you just need to go to the website of the account via the selected port. For example: http://ihre-domain.de:8080/ Tomcat also deploys a "Hello world" project that you can go to: http://ihre-domain.de:8080/examples/servlets/servlet/HelloWorldExample

Additional configuration (optional)

If Tomcat is meant to sit behind an Apache proxy, you will need to adjust the files .htaccess and server.xml. The following must be amended/inserted in the .htaccess in the document root for the account:

RewriteEngine on
RewriteRule   ^(.*)  http://localhost:8080/$1 [P]

The pre-built "connector" must be extended by a few lines in the Tomcat file server.xml (tomcat/conf/server.xml):

URIEncoding="UTF-8"
proxyPort="80"

The block should look like the one below in its entirety:

<Connector port="8080" protocol="HTTP/1.1"
              connectionTimeout="20000"
              URIEncoding="UTF-8"
              proxyPort="80"
              redirectPort="8443" />

Sources

tomcat.apache.org

tomcat.apache.org/download-90.cgi


Apache-Solr

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed servers)

Post-Installation

  • [OPTIONAL] Request that we add "java" to the configuration of our process monitoring system. Please write a support ticket via the user interface KonsoleH.
  • [OPTIONAL] Request an open port for the port that you have configured - Please request an open port by sending a support request via the user interface KonsoleH. Please note that additional open ports are generally not necessary and represent a considerable safety risk!

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Download

You will need the newest version of Apache-Solr for the next couple steps of the installation. You can find the newest version here: http://lucene.apache.org/solr/mirrors-solr-latest-redir.html Please select the source of your choice. Each source offers several different downloads; you will need the link address to the ZIP version, which you can find by right-clicking on the link. Insert the link in the following command and run it on the server.

wget http://mirror.23media.de/apache/lucene/solr/X.Y.Z/solr-X.Y.Z.zip
unzip solr-X.Y.Z.zip
mv solr-X.Y.Z solr

Add configuration to .bashrc file

You can add a configuration to the .bashrc file by using the following command:

echo 'export PATH=/usr/home/<USERNAME>/solr/bin:${PATH}' >> ~/.bashrc

To activate this setting, disconnect the SSH connection and then log back in.

Use Solr

Start Aprache-Solr using the following command:

solr start

The monitor output should look like this:

Waiting up to 30 seconds to see Solr running on port 8983 [/]
Started Solr server on port 8983 (pid=19302). Happy searching!

You can now access the Solr admin using your browser via http://IhreDomain.tld:8983. Important note: The port that you use must be opened in advance.

Additional configuration (optional)

If Solr is meant to sit behind an Apache proxy, you will need to adjust the file .htaccess. The following must be amended/inserted in the .htaccess in the document root for the account:

RewriteEngine on
RewriteRule   ^(.*)  http://localhost:8983/$1 [P]

Source and helpful links

http://lucene.apache.org/solr/

http://www.solrtutorial.com/solr-in-5-minutes.html

http://yonik.com/solr-4-tutorial/


Subversion (SVN)

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed servers)

Post-Installation

  • [OPTIONAL] Request that we add "svnserve" to the configuration of our process monitoring system. Please write a support ticket via the user interface KonsoleH.

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

SVN is already installed, and therefore it must only be set up and used. SVN can be operated with multiple users, but it cannot be used with multiple SSH users.

Preparation

First, create a main folder for the repositories to help you manage your data in an orderly way. This folder should not be located in the "public_html" directory for security reasons. Create a main folder in the home directory:

mkdir ~/subversion

Create repository

It is recommendable to create a new repository for every new project.

mkdir ~/subversion/testprojekt
svnadmin create ~/subversion/testprojekt

(optional) Create user

To do this, open the configuration folder with the editor of your choice:

nano ~/subversion/testprojekt/conf/svnserve.conf

Write the following lines in this file:

anon-access = none
auth-access = write
password-db = passwd

Now you need to define the user. This user must match the SSH user (FTP main user); the password should also match. For this, you can open the password file with the editor of your choice:

nano ~/subversion/testprojekt/conf/passwd

In the following format, insert your username and password:

<USERNAME> = <PASSWORT>

Start Subversion as a Daemon

svnserve -d

Use SVN

Now you can use SVN as usual via SSH.

svn co svn+ssh://sshhosteintrag/usr/home/<FTP-USERNAME>/subversion/testprojekt

Sources

https://civicactions.com/blog/how-to-set-up-an-svn-repository-in-7-simple-steps/

https://subversion.apache.org/


Resilio Sync (BTSync)

Requirements

Pre-Installation

  • [REQUIRED] ssh access (managed servers)

Post-Installation

  • [OPTIONAL] Request that we add "btsync" to the configuration of our process monitoring system. Please write a support ticket via the user interface KonsoleH.
  • [OPTIONAL] Request an open port for port 8888 - Please request that this port be opened by sending a support request via the user interface KonsoleH. Please note that additional open ports are generally not necessary and represent a considerable safety risk!

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details.

Installation

You can find the download link for the latest version for Linux x64 (glibc 2.3) at: https://getsync.com/platforms/desktop/ Use the following command to download the necessary files and then extract them:

wget https://download-cdn.getsync.com/stable/linux-glibc-x64/BitTorrent-Sync_glibc23_x64.tar.gz
tar xzf BitTorrent-Sync_glibc23_x64.tar.gz

Start Resilio Sync / BTSync

Using the following command, set the IP address for the managed server and then execute it.

./btsync --webui.listen <server_ip>:8888

Once the port has been opened, you can then access the administration interface via http://<SERVER-IP>:8888/gui With the following command, you can access Help for all BTSync funcitons:

./btsync --help

Normally you need to create a configuration file and one folder in which to save the data.

Sources

https://getsync.com/

https://wiki.archlinux.org/index.php/BitTorrent_Sync#Configuration

https://wiki.ubuntuusers.de/BitTorrent_Sync/#Manuell


wkhtmltopdf

Installation without SSH access

  1. Download onto your PC the appropriate package (Debian 9 (stretch) amd64) from the developer's website http://wkhtmltopdf.org/downloads.html
  2. Extract the file using the tool of your choice (for example ]http://7-zip.org/ 7-Zip])
  3. Within the archives, or in extraction folder, you will find the necessary program in the path wkhtmltox/bin/.
  4. Tranfer this file (wkhtmltopdf) to the server via FTP.
  5. You will be able to execute the file by assigning it the permission "755". You can change the permission of the file via the FTP program that you used, or you can use the WebFTP interface in KonsoleH.
  6. Now you can open the tool directly from the application by entering the complete path.

Installation with SSH access

This guide describes an approach that uses SSH access and assumes that you already are connected via SSH with your access details. The provided download link may need to be replaced with a current link. You can find the most current version at: http://wkhtmltopdf.org/downloads.html

wget https://downloads.wkhtmltopdf.org/0.12/0.12.5/wkhtmltox_0.12.5-1.stretch_amd64.deb
dpkg -x wkhtmltox_0.12.5-1.stretch_amd64.deb wkhtmltopdf

You will now find the required program "wkhtmltopdf" at wkhtmltopdf/usr/local/bin/ and you can open the tool directly from the application by entering the complete path.

Source

http://wkhtmltopdf.org


Ruby

Requirements

Pre-Installation

  • [REQUIRED] SSH access (managed server)

Post-Installation

  • [OPTIONAL] Request that we set the memory limit for "gem" to 500MB for Rails (Ruby On Rails). Please write a support ticket via the user interface KonsoleH.
  • [OPTIONAL] If you would like to use Ruby with FCGI, please request the Debian software package "libfcgi-dev". Please write a support ticket via the user interface KonsoleH.

How to use package management RubyGems (or "Gems")

You will not be able to install additional Gems for Ruby globally. But you can install it in a local environment. For this method you do not need root permissions. The package management "gem" needs to be used like this example:

gem install --user-install <gem-name>

Ruby over FCGI

If you would like to run Ruby with FCGI, the Gem "fcgi" needs to be installed.

gem install --user-install fcgi

You need a FCGI script and settings in your .htaccess file. It is recommended that you store your own Ruby application in a sub-directory of "public_html" and define this one as document root.

FCGI script This script needs do be stored in a directory which is accessable by Apache (e.g.: public_html). That is why your application should be stored in a sub-directory. Insert the following lines into the file "ruby_handler.fcgi" - you need to create this file.

#!/bin/dash
export GEM_HOME="$HOME/.gem/ruby/2.3.0/"
export GEM_PATH="$GEM_HOME:/var/lib/ruby/gems/1.8"
exec /usr/bin/ruby /usr/www/users/<FTP-USER>/<PROJECT-DIRECTORY>/index.rb

With the two "export" settings you define the directory which is indexed by Ruby for searching Gems. In this example it is the default directory for Gems which you have installed with the parameter "--user-install". It allows you to install Gems. In the line "exec" you need to set the path to an executeable script.

.htaccess settings

FcgidWrapper /usr/www/users/<FTP-USER>/ruby_handler.fcgi .rb
  SetHandler fcgid-script

In this example it shows you the settings if your FCGI script is stored in "public_html"

Sources

https://rubygems.org/

http://guides.rubygems.org/faqs/#user-install

http://www.binarytides.com/quick-tip-installing-ruby-gems-in-the-users-home-directory/



© 2018. Hetzner Online GmbH. Alle Rechte vorbehalten.