Home > Hosting Services

Hosting Services

Product Overview

To have a website hosted by Pulsant you will require the following:

Domain Hosting
Web Hosting
Web Space Account
Database (Optional)

Domain hosting points your domain name to the various services held on the web. It will point your email to the correct servers and also your website and any sub domains that you may have configured. If you have a domain registered with another provider you will still require the domain hosting service, we will keep the name servers to the current host and they will be authoritative for the domain.

Web hosting has two options, either Linux (RHEL5) or Windows (2k3 server). Both these platforms offer basic web hosting and functionality but differ in the way that they handle advanced hosting services. Typically you would choose the Linux platform unless you require FrontPage extensions, ASP or Microsoft .NET functionality.

Web Space is the physical space on our servers that will store the files of your website. You will receive a complimentary account with your Pulsant ADSL service or may purchase a web only account. This has a 1GB limit on storage space and a 500MB allowance on bandwidth. Additional storage can be purchased in 1GB units. It is not possible to purchase additional bandwidth in advance however Pulsant will only charge you for the amount that you use, based on 0.5GB increments. Customers with content rich sites and high bandwidth demands may prefer our Cloudburst billing option, which offers a greatly reduced tariff and becomes increasingly competitive as your bandwidth usage increases.

Database hosting is available to complement your Website. We offer the following services. MySQL 5.0, PostgreSQL 8.1 and Microsoft SQL server 2005.

Ordering Details

Hosting services may be ordered online via the customer area and can be ordered with a domain or as a separate service.

When ordering with a domain there are several options you can choose as follows :-

You can order a new domain and have it registered. This will then generate all of the services that are required for the hosting.
You can transfer a domain to our management. We will then transfer the domain to our control and create the relevant services for the hosting.
You can setup the domain with an unmanaged transfer. This will setup the services for the domain but will leave the domain with the current registrar.
The alternative is to keep all domain services with your current provider. You should then simply order the webspace account via the customer area. We will need to setup offsite domain hosting to enable your domain to point to your webspace.

Using custom error pages on the Windows 2003 web hosting platform

  1. Create the custom error page.
  2. Upload it to your webspace.
  3. Contact technical support stating the required error code (404, 501, etc.) and the location/name of the error page you would like to have displayed.

Using Java servlets and JSP on the Linux web hosting platform.

Java Servlets and JSP

As of December 2010 the current version is Tomcat 5.5.23 supporting Servlet 2.3 and JSP 1.2 standards as published by Sun.

Setup

To purchase Tomcat hosting, and use on your site, please send an email to [email protected] with the following information :-

  • username and hostname for your site to associate the hosting with
  • confirmation of acceptance of cost – £100 plus vat/annum

Hosting will be setup within 24 hours of your request.

Uploads

A web application directory will be created for you as ‘ejava’, in your home directory, and used to store HTML, JSP and class files. These maybe uploaded in the usual way, using ftp or the Pulsant shell server.

The basic directory structure is as follows:

ejava/WEB-INF/web.xml Tomcat configuration file
ejava/WEB-INF/classes/* Servlet and library .class files
ejava/WEB-INF/lib/* Servlet and library .jar files
ejava/* Static or JSP pages

The full directory layout and configuration file format is described in the Tomcat Application Developer’s Guide.

Access

Your uploaded Java files will be accessible using the following URLs (substitute <your domain> and <your user name> as appropriate).

http://<your domain>/ejava/<your user name>/servlet/*
http://<your domain>/ejava/<your user name>/*.jsp

Development

Standard libraries on the default classpath include the Servlet library, Xerces, PostgreSQL and MySQL drivers. When compiling class files, it may be necessary to copy these on to your local classpath i.e. take a copy of the Jar file(s) from the Pulsant Library and upload to
/ejava/WEB-INF/lib.

Using custom error pages on the Linux web hosting platform.

If you would like to use custom error pages for your site, you will need to:

  1. Create the custom error page.
  2. Upload it to your webspace.
  3. Contact technical support stating the required error code (404, 501, etc.) and the location/name of the error page you would like to have displayed.

Free CGI Scripts

Pulsant provides a couple of CGI scripts for customers wishing to add functionality to their website.

 

——————————————————————————————————————————————————–

Counter

This CGI adds a hit counter to a webpage. Each time the page is accessed, the counter is incremented. To add a counter to your page, firstly add the following line of HTML code into your index.html page or wherever you would like the counter to appear:

<img src=”http://www.lumison.net/cgi-bin/Count.cgi?user=<username>&df=countfile&dd=B”>

Remember to change <username> for your own Pulsant account username.

There are 9 display options for the counter, which you can control from the line of HTML code given above. The display is controlled by the &dd=B part of the string – in this case option B is selected. The range of display options can be described as follows:

&dd=A – green “calculator” digits against black background
&dd=B – white “alarm clock” digits against black background
&dd=C – white “italic” digits against black background
&dd=D – small green digits against black background
&dd=E – very small black “square” digits against white background
&dd=bang – black “dingbats” type display against white background (output not legible)
&dd=cd – black “hand-written” digits against white background
&dd=cdd – green “pixellated” digits against black background
&dd=cdr – red digits against black background

Secondly, you have to create a directory in your public_html folder called “log” ie “public_html/log”. This is where the countfile is kept which holds the number of hits your counter has received, not that you’d ever want to alter the file to indicate a higher hitcount, would you?. Please note if you wish to run on a windows hosted site that this must be created in the Linux account via ftp.lumison.net or the shell server and not in the Windows webspace as the script points to your Linux system account and not the Windows account

 

——————————————————————————————————————————————————–

Sendform

This is a form-to-email script which can be added to a webpage, so that enquiries, feedback or anything else that you want can be sent from a form on your website to email.

Here is some example code you can cut and paste into the source code of your webpage and then modify to create your form:

<form method=”post” action=”http://www.lumison.net/cgi-bin/sendform.pl”>
<input type=”hidden” name=”from” value=”[email protected]”>
<input type=”hidden” name=”to” value=”[email protected]” >
<input type=”hidden” name=”subject” value=”Sendform.pl example”>
Email address: <input type=”textfield” name=”email_address”>
Comment: <textarea name=”comments” cols=”25″ rows=”4″> </textarea>
<input type=”submit”>
</form>

Once you have the basic form on your page, you can customise it by adding lines to it in the form:

<input type=”hidden” name=”variable” value=”value”>

Email address:
Comment:

The sendform script requires that your end-users provide the HTTP REFERER field. The referer field lets us know which website was used with the sendform.pl script.

Normally the referer is sent automatically, however the end-user could have installed security software or otherwise taken steps to hide this field.

Without the referer field, we have no way of verifying that your website is authorised to use the sendform script. This would cause the mail to be rejected.

If this requirement is causing you problems, we can optionally whitelist the content of your “to” field, so that mail will always be allowed to your email address, regardless of the status of the referer field. To arrange whitelisting, please contact Pulsant support.

The to line as shown above must always be given or the errorpage (see below) will be shown. This can contain a single address or a comma separated list of addresses.

You can also choose from the following variables:

from When the email is received by the intended recipient, the mail is given as being from this address. Without this line, the script defaults to “[email protected]”.

subject The subject of the mail received by the recipient. Without this line, the script defaults to “Response to Web form”.

mailtitle a title that will be put at the top of the email body text. Without this line, the script does not add a title.

successpage This specifies the page the script loads when the form has been filled in and submitted successfully. Without this line, the script defaults to “http://www.lumison.net/templates/successpage.html”.

errorpage This specifies the page the script loads if the required form fields (see mandatory below) have not been filled in. Without this line the script defaults to “http://www.lumison.net/templates/errorpage.html”.

mandatory This is a list of fields that the user MUST fill in for the form submission to work. This list should be comma-separated only. Without this line, the script has no mandatory fields.

email_as_from If this is set to “yes” in the form, you can create a form field named emailfield and use the content of that field as the from address in the email sent out. This only works if the form has a field called email.

FTP

What is FTP?

FTP stands for File Transfer Protocol. It is the standard Internet protocol for transferring files from one computer to another. FTP is part of the TCP/IP protocol suite. TCP/IP is the basic protocol that runs the whole Internet. Whether you are checking your email, visiting a web site or downloading files, you are using TCP/IP. There are a number of smaller protocols that run on top of TCP/IP, such as email, HTTP, and Telnet. FTP is one of these. Its sole function is to move a file from a server to a client (download) or from a client to a server (upload).

What is a network protocol?

In order for two networked computers to communicate, they need a protocol, or “handshake”. A protocol is a mutually agreed set of rules that enable both parties to know:

* what to do to initiate an exchange
* what to expect next

If you pick up the telephone and say “hello”. You expect the person at the other end of the line to say “hello” as well. This is standard protocol for telephone conversations. The Internet runs on TCP/IP (Transport Control Protocol/Internet Protocol). As the name suggests it is actually two protocols. Internet Protocol (IP) is the low level protocol that routes packets from one node to the other, and concerns itself with such things as IP addresses (e.g. 192.168.1.254). TCP takes addressing for granted and concerns itself with higher level functions such as session management and data transfer. HTTP and FTP are both part of TCP.

How does FTP work?

FTP requires two computers, one running an FTP server, the other running an FTP client. The exchange is initiated by the client which logs in under an accepted user name and password. Once this occurs, a session is opened and stays open until closed by either the client or the server, or until it times out. While the session is open, the client may execute numerous FTP commands on the server. These include commands to change directories, list files, get files and put files.

Is FTP better than HTTP for downloading files?

Yes, as a matter of fact it is. HTTP is designed to fetch web pages. It is optimized for numerous repeated fetches of small items. FTP is designed for transferring files, and offers faster overall throughput and better error checking. It is not uncommon for a user to fail repeatedly to download a large file via HTTP using their browser, only to succeed on their first try using a dedicated FTP client. If you download large files frequently, and experience difficulties, get a dedicated FTP client software program.

What is the difference between passive and active FTP?

FTP is an unusual protocol in that it uses two ports, one for commands and the other for data. (This is one of the reasons it is superior to HTTP for transferring large files.) Active FTP was invented first. The client initiates a connection on the server’s command port. The server then initiates a connection with the client from its data port. In Passive FTP, the client initiates both connections with the server, which remains “passive”.

Active FTP may cause problems if your client is behind a firewall. From the firewall’s point of view, the FTP server that is trying to initiate a connection with your client looks like an intruder and is usually blocked. This is why many users have difficulty using FTP to download files from behind a firewall.

Passive FTP solves this problem, but creates other problems, notably where FTP server security is concerned. The server must listen on a large number of ports. This requires the firewall to let a lot of unqualified traffic through. Most firewall administrators do not like this.
As a rule, you do not need to be concerned about passive and active FTP unless you administer an FTP server or a firewall. If you experience difficulty using your FTP client from behind a firewall, this is likely the reason. Perhaps you should discuss the matter with your firewall administrator.

Using PHP on the Linux web hosting platform

PHP is a fast and versatile scripting language that allows quick and easy addition of interactivity to your website. For those of you used to using ASP, it is very similar, but faster and more efficient. You can make database calls, output text and random variables, simple field includes (e.g. current date), as well as call files and templates from your webspace at Pulsant.
<? echo (“this is a simple script\n”); ?>

<?php echo(“if you want to serve XML documents, do like this\n”); ?>

<script language=”php”>
echo (“some editors don’t like processing instructions”);
</script>

As of December 2010, the version of PHP is 5.1.6. and full details of the version, available modules and configuration can be found at http://rhel5phpinfo.lumison.net/phpinfo.php

Note that if the global settings are not as required it is possible to overide many by adding settings to a .htaccess file, see the PHP documentation at http://www.php.net/ for full details.

In order to use PHP in your webpages, insert the PHP code into your webpage and upload it to your web space using a .php extension. If you would like an alternative file extension used then add the following command to a .htaccess file in the affected web directory or one of it’s parents (The example shown will cause .html files to be parsed).

AddType application/x-httpd-php html

Using SSI ( Server Side includes) on the Linux webhosting platform.

Writing CGI in perl means you can quickly add interactivity or deal with web forms. Whilst you may call a CGI either from a FORM or directly from an HREF, you may wish to include script output, or html, directly into a webpage.

Our web server can parse your html, to include either output from a script or other templates, using SSI (Server Side Includes) but you need to enable this first.

To enable SSI, for the default .shtml files, add the following line to a .htaccess file in the affected web folder or one of it’s parents :-

Options +Includes

If you would like to parse files with other extensions you can enable this by adding the following to your .htaccess
file (.html in this example) :-

AddOutputFilter INCLUDES .html

Once you have enabled parsing you can add includes into your file text as detailed in the following examples :-

<!–#include virtual=”anotherfile.html”–>
<!–#include virtual=”/somedir/anotherfile.txt”–>
…and in order to run scripts:
<!–#include virtual=”/cgi-bin/user/someone/myscript.cgi”–>

For complete documentation please check the Apache web site: http://www.apache.org/docs/mod/mod_include.html

Using GPG on the Linux webhosting platform.

GPG (or GNU privacy guard) is an application that allows you to sign/encrypt your data for transmission, by email, across the internet.

In order to use GPG you will need to have secure keys, which you can generate on our server or elsewhere and import it.

To generate a key, use the ‘–gen-key’ flag:

$ gpg –gen-key (and follow the instructions. In most cases choosing the default answers will be sufficient)

Import the public key of the person you are sending email to:-

$ gpg –import <keyfile name>

To encrypt a text file, with a key you hold, use:

$ gpg –out <encrypted file name> –recipient <uid> –armour –encrypt <original file name>

There are numerous options for connecting to GPG using Perl so we would recommend an internet search to find something that suites your programming style (e.g. http://www.perlmonks.org/?node_id=152489)

GPG is also supported by PHP as detailed at http://www.php.net/manual/en/book.gnupg.php

For more info on GPG see the documentation section at www.gnupg.org.

Adding MIME types to Apache, using .htaccess, on the Linux webhosting platform.

The web server’s list of filename extension to mime type mappings can be added to or overridden by customers on a per-account or per-directory basis using .htaccess files.

The syntax is: AddType mime/type extension

e.g.
AddType image/gif .gif
AddType audio/x-mpegurl .m3u

For more information please see: http://httpd.apache.org/docs/mod/mod_mime.html#addtype

Password-protecting web pages, using .htaccess, on the linux web hosting platform

Most of the time, if Pulsant hosts your website, you want the whole world to be able to see it in all its glory. However, there may be occasions where you want to prevent the world at large from accessing certain pages, such as a page just for a certain client or a company intranet only for employees.

For websites hosted on our Apache (UNIX) webserver it is possible for you to protect areas of your website yourself in two simple steps. NB To follow these instructions, you require shell access to your Pulsant account. If you do not have this or would like to know more about it,take a look at our shell server FAQ.

Step 1: Creating an access list

For any website to which you want to restrict access, you need to have a list of users who are allowed access to parts of the site. You can do this by creating a password file. It goes without saying that this file should be protected from prying eyes, so a good place to put it is in your home directory.

If you do not already have an .htaccess password file, type the following command at the shell prompt:

htpasswd -c /home/<accountname>/<passwordfile> <username>

where <accountname> is your Pulsant account name, <passwordfile> is the name of the password file you’re creating, and <username> is the name of the user for whom you’re adding the password. You will then be prompted for a password for that username.

NB if you have already created a password file and are just adding more users then use the above command without the -c option.

Please note that standard password encryption methods can only encrypt up to 8 characters, so while you can use a password longer than 8 characters, the remainder of the characters will be ignored.

Please refer to the shell command “man htpasswd” for more information.

Step 2: Locking a directory

The way to prevent unauthorised access to web pages is to keep them in a locked sub-directory of your public_html directory. To lock a sub-directory, you need to create a file in that directory called .htaccess. Below is a bare-bones, working .htaccess file which may be copied and pasted into a text editor:

AuthName “Realm”
AuthType Basic
AuthGroupFile /dev/null
AuthUserFile /home/<accountname>/<passwordfile>
require valid-user

where Realm (which should be in quotes) is a label which appears in the password protection dialog box for the directory you’re protecting, <accountname> is your Pulsant account name, and <passwordfile> is the name of your .htaccess password file from Step 1.

NB the line require valid-user will allow anyone in the password file access to the protected directory. If you wish to allow only certain specific people from the password list into a directory, you can achieve this by replacing the line with:

require user user1 user2 user3. . .

for as many users as you wish to allow. This is most useful if you wish to protect more than one directory, each with different users, but wish to maintain only one password file.

After the file is created in the directory, you will not see it because it is hidden from normal view of the ls command. To see hidden files, you must use ls -a.

Finally you need to type the following command, at the shell prompt, in the directory containing the .htaccess file:

chmod 644 .htaccess

Once this is done, your directory and any web pages in it are protected.

Server details for the Linux web hosting platform

Our Linux web hosting platform uses a loadbalanced server farm and should be accessed using the following host names.

FTP access

ftp.lumison.net, on port 21,  using your Linux webspace username/password.

SSH/SFTP Shell access

shell.lumison.net, on port 22, using your Linux webspace username/password.

DNS

If you have your DNS hosted elsewhere you will need to point your hostname at the shared web platform using a CNAME record pointing to vweb.lumison.net or, where a CNAME is not permitted, an A record of 87.246.107.166

Using Java servlets and JSP on the Linux web hosting platform.

Java Servlets and JSP

As of December 2010 the current version is Tomcat 5.5.23 supporting Servlet 2.3 and JSP 1.2 standards as published by Sun.

Setup

To purchase Tomcat hosting, and use on your site, please send an email to [email protected] with the following information :-

  • username and hostname for your site to associate the hosting with
  • confirmation of acceptance of cost – £100 plus vat/annum

Hosting will be setup within 24 hours of your request.

Uploads

A web application directory will be created for you as ‘ejava’, in your home directory, and used to store HTML, JSP and class files. These maybe uploaded in the usual way, using ftp or the Pulsant shell server.

The basic directory structure is as follows:

ejava/WEB-INF/web.xml Tomcat configuration file
ejava/WEB-INF/classes/* Servlet and library .class files
ejava/WEB-INF/lib/* Servlet and library .jar files
ejava/* Static or JSP pages

The full directory layout and configuration file format is described in the Tomcat Application Developer’s Guide.

Access

Your uploaded Java files will be accessible using the following URLs (substitute <your domain> and <your user name> as appropriate).

http://<your domain>/ejava/<your user name>/servlet/*
http://<your domain>/ejava/<your user name>/*.jsp

Development

Standard libraries on the default classpath include the Servlet library, Xerces, PostgreSQL and MySQL drivers. When compiling class files, it may be necessary to copy these on to your local classpath i.e. take a copy of the Jar file(s) from the Pulsant Library and upload to
/ejava/WEB-INF/lib.

Is there a URL available to test uploaded content before making DNS changes.

There is no test URL available to allow testing, on the shared Windows platform, before changing your DNS. We therefore recommend temporarily overriding your current DNS.

See https://my.pulsant.com/node/800 for details of how to apply a local override.

Using FrontPage Extensions on the Windows 2003 web hosting platform.

Microsoft FrontPage extensions provide a quick and easy path for designing web pages with built-in functionality without the author having to write the ‘code’ him/herself, eg. for hit counters or searching.

To make use of FrontPage extensions you need to have Windows hosting and you need FrontPage extensions to be enabled. Please ask us to enable FrontPage extensions before you publish your website, if you haven’t already done so.

You can then publish your web. For FrontPage extensions features to work you must publish your web using HTTP to the website URL eg:

http://www.example.com

You will need to enter your username and password.

FrontPage extensions features will not work if you use FTP to upload your website, and doing this may break the FrontPage extensions. If this happens then Pulsant will need to re-enable FrontPage extensions for you and you will need to re-publish the website using HTTP.


Some customers have been experiencing problems using the web publishing wizard in Front Page 2002.

This is a known and documented problem, please see the article on the Microsoft support site to see how you can publish your site using Front Page 2002:

Using ASP on the Windows 2003 web hosting platform.

Web designers use ASP to provide dynamic and personalised content in their web pages. Active Server Pages can be written in either Visual Basic or Javascript programming languages. Once the designer has the pages working on his/her machine there should be no problems uploading the pages and running them on the site we host.
ASP pages can utilise a large amount of functionality built into the Microsoft Web Server(IIS) but in some cases a designer might want to use a third party module/plugin. Pulsant doesn’t support third party ASP plugins as they may contain security flaws and exploits that could compromise our systems and customers’ websites.

Two good sources of ASP sample code and help are www.asp101.com and www.15seconds.com

Using PHP on the Windows 2003 web hosting platform.

Please also see the Linux PHP Page

A comprehensive listing of the packages & functionality available on our Windows hosting platform kind be found at phpinfo.php

Server details for the Windows 2003 web hosting platform.

Our Windows web hosting platform uses a loadbalanced server farm and should be accessed using the following host names.

FTP access

winftp.lumison.net, on port 21,  using your Windows webspace username/password.

SSH/SFTP Shell access

shell.lumison.net, on port 22, using your Linux webspace username/password.

DNS

If you have your DNS hosted elsewhere you will need to point your hostname at the shared web platform using a CNAME record pointing to vweb-win2k3.lumison.net.

Connecting to MySQL using PHP.

PHP access to MySQL is available but access is restricted to the Pulsant web servers.

PHP provides specific support for MySQL:

$db = mysql_connect($servername, $username, $password);

You will need to set $servername, $username and $password to suit your database as detailed for MySQL

Both mysql_connect and mysql_pconnect should work, but pconnect will provide a persistent connection if required. For more details, have a look at: http://www.php.net/manual/en/ref.mysql.php

Connecting to MySQL using C#.

To open an ODBC connection from Windows 2003 to a MySQL database, use the following piece of C# code:-

string connString = “DRIVER={MySQL};SERVER=servername;DATABASE=dbname;UID=mysqlusername;PWD=mysqlpassword”;
System.Data.Odbc.OdbcConnection conn = new System.Data.Odbc.OdbcConnection(connString);
conn.Open();

You will need to set servername, dbname, mysqlusername and mysqlpassword to suit your database as detailed for MySQL

Please remember to call conn.Close(); to close the connection afterwards

MySQL access via the command line interace.

Command line access to MySQL is available but access is restricted to the Pulsant shell server. Shell access is available on all Pulsant webspace accounts but is disabled by default, if you would like this enabled simply email [email protected] and we will do this for you.

  1. Connect to shell.lumison.net, using SSH, and log in using your webspace username and password (Note that if using windows web hosting you will have 2 passwords and you will need to use the one associated with your email).
  2. Type ‘mysql -h mysql.lumison.net -u <user name> -p <database name>’ and press enter.

This will ask for your database password and will then take you to the MySQL command interface.

Note that <server name>, <user name> and <database name> should be substituted by the details specific to your database, see the MySQL server details.

Importing a MySQL database from the command line.

Command line access to MySQL is available but access is restricted to the Pulsant shell server. Shell access is available on all Pulsant webspace accounts but is disabled by default, if you would like this enabled simply email [email protected] and we will do this for you.

To import a MySQL database you must first have a file containing the required SQL (import.sql in our example), upload this to your web space account and then use the following command to save this into the database.

  • Upload your SQL file to your Linux webspace.
  • Connect to shell.lumison.net, using SSH, and log in using your webspace username and password (Note that if using windows web hosting you will have 2 passwords and you will need to use the one associated with your email).
  • Change directory to the location of the uploaded SQL file.
  • Type ‘mysql -h mysql.lumison.net -u <user name> -p <database name> < import.sql’ and press enter.

This will ask for your database password, will import the SQL file and return you to a command prompt.

Note that <server name>, <user name> and <database name> should be substituted by the details specific to your database, see the MySQL server details.

Exporting a MySQL database from the command

Command line access to MySQL is available but access is restricted to the Pulsant shell server. Shell access is available on all Pulsant webspace accounts but is disabled by default, if you would like this enabled simply email [email protected] and we will do this for you.

  • Connect to shell.lumison.net, using SSH, and log in using your webspace username and password (Note that if using windows web hosting you will have 2 passwords and you will need to use the one associated with your email).
  • Change directory to the location you would like to save your SQL file.
  • Type ‘mysqldump -h mysql.lumison.net -u <user name> -p <database name> > export.sql’ and press enter.

This will ask for your database password, will export the SQL file and return you to a command prompt. You will then be able to download the file from your Linux web space if required.

Note that <server name>, <user name> and <database name> should be substituted by the details specific to your database, see the MySQL server details.

Is there a web interface (e.g. phpmyadmin) provided for MySQL.

phpMyAdmin is available at http://www.lumison.net/phpmyadmin/ or simply append the path to your domain name, e.g. http://www.example.com/phpmyadmin/

Pulsant do not provide support for the use of this application but supplier documentation is available at http://www.phpmyadmin.net/home_page/docs.php

Note

The server is configured using directory Aliases for /phpmyadmin, /phpMyAdmin and /mysqladmin to allow phpmyadmin to be displayed on all hosted domains. This means that you will not be able to use these directory names for other applications.

MySQL – server details.

Note that the database server can only be accessed from the Pulsant web and shell servers.

  • hostname: mysql.lumison.net
  • username: as supplied by Pulsant. (This will consist of the
    associated account username and may have a suffix).
  • password: as supplied by Pulsant and will match the username.

Connecting to MySQL using perl.

Perl access to MySQL is available but access is restricted to the Pulsant web servers.

We support the use of DBI, the standard method for Perl:

use DBI;
$dbh = DBI->connect(‘dbi:mysql;database=DATABASE; host=$servername’, $username, $password);

You will need to set $servername, $username and $password to suit your database as detailed for MySQL

MySQL – Service overview

MySQL
Verson: 5.0.77
Website: http://www.mysql.com

Features and limitations:-

  • Access provided via TCP/IP but permitted only from Pulsant web, mail and shell servers.
  • Command line ‘mysql’, Perl DBI, PHP and JDBC clients are supported.
  • One login will be created per database which must be named after, or prefixed with, a valid system account name.
  • Standard MySQL commands (for the specified version) are permitted.
  • Server-side file access (e.g. LOAD DATA INFILE) is disabled.
  • 50MB disk allocation plus normal Pulsant ‘Storage allocation’ rates.

Uploading content to your webspace

f you are new to the concept of webhosting you may be unsure about the best method for uploading content to your Pulsant webspace, or perhaps you used to employ someone to do this for you and now have to manage an existing site yourself. In either case you will require an FTP client.

Pulsant recommend using Filezilla as your main FTP client. You can download the appropriate client version for your operating system here

Once you have installed the filezilla client, the simplest way to access your webspace is using the Quickconnect bar. Enter the appropriate hostname for the hosting type that you have purchased along with your username and password as provided by Pulsant. The port is 21 but entering the port is optional as 21 is the default port for FTP.

Linux webhosting

filezilla setup for linux

 

Windows webhosting

filezilla setup for windows

 

N.B. the windows host is “winftp.lumison.net”

Once you have connected to your webspace you will see the split screen view showing the contents of your PC on the left and the contents of your webspace on the right. To upload new content to your site simply highlight the files/folders in the left hand pane then right-click and select “upload”. To backup content from your webspace you need to highlight the files/folders in the right hand pane then right-click and select “download”. You will see the progress of the transfers displayed at the bottom of the screen.

N.B. In order for your site to work correctly you must upload your content to the correct path. The default path is “/public_html” unles you have more than one website hosted via your webspace in which case you must ensure that you have selected the correct path. If you are unsure about what the path should be please contact Pulsant Support on 0845 11 99 999 or email [email protected]

The supporting documentation and full userguides for Filezilla can be found here.