Ideas, new features and today's news


Dr.silnt HilL File Manager

darkshadow File Manager

Current Path : /opt/bitnami/apps/product/htdocs/
Upload File :
Current File : /opt/bitnami/apps/product/htdocs/INSTALL.txt


 * Requirements and notes
 * Optional server requirements
 * Installation
 * Building and customizing your site
 * Multisite configuration
 * More information


Drupal requires:

- A web server. Apache (version 2.0 or greater) is recommended.
- PHP 5.2.4 (or greater) (
- One of the following databases:
  - MySQL 5.0.15 (or greater) (
  - MariaDB 5.1.44 (or greater) ( MariaDB is a fully
    compatible drop-in replacement for MySQL.
  - PostgreSQL 8.3 (or greater) (
  - SQLite 3.4.2 (or greater) (

For more detailed information about Drupal requirements, including a list of
PHP extensions and configurations that are required, see "System requirements"
( in the online documentation.

For detailed information on how to configure a test server environment using a
variety of operating systems and web servers, see "Local server setup"
( in the online documentation.

Note that all directories mentioned in this document are always relative to the
directory of your Drupal installation, and commands are meant to be run from
this directory (except for the initial commands that create that directory).


- If you want to use Drupal's "Clean URLs" feature on an Apache web server, you
  will need the mod_rewrite module and the ability to use local .htaccess
  files. For Clean URLs support on IIS, see "Clean URLs with IIS"
  ( in the online documentation.

- If you plan to use XML-based services such as RSS aggregation, you will need
  PHP's XML extension. This extension is enabled by default on most PHP

- To serve gzip compressed CSS and JS files on an Apache web server, you will
  need the mod_headers module and the ability to use local .htaccess files.

- Some Drupal functionality (e.g., checking whether Drupal and contributed
  modules need updates, RSS aggregation, etc.) require that the web server be
  able to go out to the web and download information. If you want to use this
  functionality, you need to verify that your hosting provider or server
  configuration allows the web server to initiate outbound connections. Most web
  hosting setups allow this.


1. Download and extract Drupal.

   You can obtain the latest Drupal release from -- the files
   are available in .tar.gz and .zip formats and can be extracted using most
   compression tools.

   To download and extract the files, on a typical Unix/Linux command line, use
   the following commands (assuming you want version x.y of Drupal in .tar.gz

     tar -zxvf drupal-x.y.tar.gz

   This will create a new directory drupal-x.y/ containing all Drupal files and
   directories. Then, to move the contents of that directory into a directory
   within your web server's document root or your public HTML directory,
   continue with this command:

     mv drupal-x.y/* drupal-x.y/.htaccess /path/to/your/installation

2. Optionally, download a translation.

   By default, Drupal is installed in English, and further languages may be
   installed later. If you prefer to install Drupal in another language

   - Download a translation file for the correct Drupal version and language
     from the translation server:

   - Place the file into your installation profile's translations
     directory. For instance, if you are using the Standard install profile,
     move the .po file into the directory:


   For detailed instructions, visit

3. Create the Drupal database.

   Because Drupal stores all site information in a database, you must create
   this database in order to install Drupal, and grant Drupal certain database
   privileges (such as the ability to create tables). For details, consult
   INSTALL.mysql.txt, INSTALL.pgsql.txt, or INSTALL.sqlite.txt. You may also
   need to consult your web hosting provider for instructions specific to your
   web host.

   Take note of the username, password, database name, and hostname as you
   create the database. You will enter this information during the install.

4. Run the install script.

   To run the install script, point your browser to the base URL of your
   website (e.g.,

   You will be guided through several screens to set up the database, add the
   site maintenance account (the first user, also known as user/1), and provide
   basic web site settings.

   During installation, several files and directories need to be created, which
   the install script will try to do automatically. However, on some hosting
   environments, manual steps are required, and the install script will tell
   you that it cannot proceed until you fix certain issues. This is normal and
   does not indicate a problem with your server.

   The most common steps you may need to perform are:

   a. Missing files directory.

      The install script will attempt to create a file storage directory in
      the default location at sites/default/files (the location of the files
      directory may be changed after Drupal is installed).

      If auto-creation fails, you can make it work by changing permissions on
      the sites/default directory so that the web server can create the files
      directory within it for you. (If you are creating a multisite
      installation, substitute the correct sites directory for sites/default;
      see the Multisite Configuration section of this file, below.)

      For example, on a Unix/Linux command line, you can grant everyone
      (including the web server) permission to write to the sites/default
      directory with this command:

        chmod a+w sites/default

      Be sure to set the permissions back after the installation is finished!
      Sample command:

        chmod go-w sites/default

      Alternatively, instead of allowing the web server to create the files
      directory for you as described above, you can create it yourself. Sample
      commands from a Unix/Linux command line:

        mkdir sites/default/files
        chmod a+w sites/default/files

   b. Missing settings file.

      Drupal will try to automatically create a settings.php configuration file,
      which is normally in the directory sites/default (to avoid problems when
      upgrading, Drupal is not packaged with this file). If auto-creation fails,
      you will need to create this file yourself, using the file
      sites/default/default.settings.php as a template.

      For example, on a Unix/Linux command line, you can make a copy of the
      default.settings.php file with the command:

        cp sites/default/default.settings.php sites/default/settings.php

      Next, grant write privileges to the file to everyone (including the web
      server) with the command:

        chmod a+w sites/default/settings.php

      Be sure to set the permissions back after the installation is finished!
      Sample command:

        chmod go-w sites/default/settings.php

   c. Write permissions after install.

      The install script will attempt to write-protect the settings.php file and
      the sites/default directory after saving your configuration. If this
      fails, you will be notified, and you can do it manually. Sample commands
      from a Unix/Linux command line:

        chmod go-w sites/default/settings.php
        chmod go-w sites/default

5. Verify that the site is working.

   When the install script finishes, you will be logged in with the site
   maintenance account on a "Welcome" page. If the default Drupal theme is not
   displaying properly and links on the page result in "Page Not Found" errors,
   you may be experiencing problems with clean URLs. Visit to troubleshoot.

6. Change file system storage settings (optional).

   The files directory created in step 4 is the default file system path used to
   store all uploaded files, as well as some temporary files created by
   Drupal. After installation, you can modify the file system path to store
   uploaded files in a different location.

   It is not necessary to modify this path, but you may wish to change it if:

   - Your site runs multiple Drupal installations from a single codebase (modify
     the file system path of each installation to a different directory so that
     uploads do not overlap between installations).

   - Your site runs on a number of web servers behind a load balancer or reverse
     proxy (modify the file system path on each server to point to a shared file

   - You want to restrict access to uploaded files.

   To modify the file system path:

   a. Ensure that the new location for the path exists and is writable by the
      web server. For example, to create a new directory named uploads and grant
      write permissions, use the following commands on a Unix/Linux command

        mkdir uploads
        chmod a+w uploads

   b. Navigate to Administration > Configuration > Media > File system, and
      enter the desired path. Note that if you want to use private file storage,
      you need to first enter the path for private files and save the
      configuration, and then change the "Default download method" setting and
      save again.

   Changing the file system path after files have been uploaded may cause
   unexpected problems on an existing site. If you modify the file system path
   on an existing site, remember to copy all files from the original location
   to the new location.

7. Revoke documentation file permissions (optional).

   Some administrators suggest making the documentation files, especially
   CHANGELOG.txt, non-readable so that the exact version of Drupal you are
   running is slightly more difficult to determine. If you wish to implement
   this optional security measure, from a Unix/Linux command line you can use
   the following command:

     chmod a-r CHANGELOG.txt

   Note that the example only affects CHANGELOG.txt. To completely hide all
   documentation files from public view, repeat this command for each of the
   Drupal documentation files in the installation directory, substituting the
   name of each file for CHANGELOG.txt in the example.

   For more information on setting file permissions, see "Modifying Linux,
   Unix, and Mac file permissions" ( or
   "Modifying Windows file permissions" ( in the online documentation.

8. Set up independent "cron" maintenance jobs.

   Many Drupal modules have tasks that must be run periodically, including the
   Search module (building and updating the index used for keyword searching),
   the Aggregator module (retrieving feeds from other sites), and the System
   module (performing routine maintenance and pruning of database tables). These
   tasks are known as "cron maintenance tasks", named after the Unix/Linux
   "cron" utility.

   When you install Drupal, its built-in cron feature is enabled, which
   automatically runs the cron tasks periodically, triggered by people visiting
   pages of your site. You can configure the built-in cron feature by navigating
   to Administration > Configuration > System > Cron.

   It is also possible to run the cron tasks independent of site visits; this is
   recommended for most sites. To do this, you will need to set up an automated
   process to visit the page cron.php on your site, which executes the cron

   The URL of the cron.php page requires a "cron key" to protect against
   unauthorized access. Your site's cron key is automatically generated during
   installation and is specific to your site. The full URL of the page, with the
   cron key, is available in the "Cron maintenance tasks" section of the Status
   report page at Administration > Reports > Status report.

   As an example for how to set up this automated process, you can use the
   crontab utility on Unix/Linux systems. The following crontab line uses the
   wget command to visit the cron.php page, and runs each hour, on the hour:

   0 * * * * wget -O - -q -t 1

   Replace the text "" in the
   example with the full URL displayed under "Cron maintenance tasks" on the
   "Status report" page.

   More information about cron maintenance tasks is available at, and sample cron shell scripts can be found in the
   scripts/ directory. (Note that these scripts must be customized like the
   above example, to add your site-specific cron key and domain name.)


A new installation of Drupal defaults to a very basic configuration. To extend
your site, you use "modules" and "themes". A module is a plugin that adds
functionality to Drupal, while a theme changes the look of your site. The core
of Drupal provides several optional modules and themes, and you can download
more at and

Do not mix downloaded or custom modules and themes with Drupal's core modules
and themes. Drupal's modules and themes are located in the top-level modules and
themes directories, while the modules and themes you add to Drupal are normally
placed in the sites/all/modules and sites/all/themes directories. If you run a
multisite installation, you can also place modules and themes in the
site-specific directories -- see the Multisite Configuration section, below.

Never edit Drupal's core modules and themes; instead, use the hooks available in
the Drupal API. To modify the behavior of Drupal, develop a module as described
at To modify the look of Drupal, create a
subtheme as described at, or a completely new
theme as described at


A single Drupal installation can host several Drupal-powered sites, each with
its own individual configuration.

Additional site configurations are created in subdirectories within the 'sites'
directory. Each subdirectory must have a 'settings.php' file, which specifies
the configuration settings. The easiest way to create additional sites is to
copy the 'default' directory and modify the 'settings.php' file as appropriate.
The new directory name is constructed from the site's URL. The configuration for could be in 'sites/' (note that 'www.'
should be omitted if users can access your site at

Sites do not have to have a different domain. You can also use subdomains and
subdirectories for Drupal sites. For example,,, and can all be defined as independent Drupal sites. The setup
for a configuration such as this would look like the following:


When searching for a site configuration (for example,
Drupal will search for configuration files in the following order, using the
first configuration it finds:


If you are installing on a non-standard port, the port number is treated as the
deepest subdomain. For example: could be loaded
from sites/ The port number will be removed according to
the pattern above if no port-specific configuration is found, just like a real

Each site configuration can have its own site-specific modules and themes in
addition to those installed in the standard 'modules' and 'themes' directories.
To use site-specific modules or themes, simply create a 'modules' or 'themes'
directory within the site configuration directory. For example, if has a custom theme and a custom module that should not be
accessible to other sites, the setup would look like this:


NOTE: for more information about multiple virtual hosts or the configuration
settings, consult

For more information on configuring Drupal's file system path in a multisite
configuration, see step 6 above.


- See the online documentation:

- For a list of security announcements, see the "Security advisories" page at (available as an RSS feed). This page also
  describes how to subscribe to these announcements via e-mail.

- For information about the Drupal security process, or to find out how to
  report a potential security issue to the Drupal security team, see the
  "Security team" page at

- For information about the wide range of available support options, visit and click on Community and Support in the top or bottom

darkshadow File Manager Version 1.0, Coded By Fallag darkshadow-tn

Stratus Summer Play List

We've been in scarves and coats for too long here at Stratus Towers.

It's been a good thing as a whole range of new features and functionality are ready to ship. Improved DLE, 70:20:10 alignments Live Virtual Training and upgrades smoothly progressing for our customers. Exciting times continue to happen.

We're still enjoying our Winter tunes, but here is something new and unique for Summer.

So, our summer listening choice is all about Mediterranean summers, about music on the beach, in the shade, with friends, invoking happy memories and new invigorating ideas. Put together by Nancy Noise for our friends over at we hope it sound tracks your summer and memories of it when the evenings start to close in again.

Stratus Presenter Module

Stratus Presenter Module, an optional module that delivers Live Online Webinars, briefings, meetings or any 'happening' that your organisation needs to conduct.

It's simple, schedule the event and invite your attendees.

Within Stratus attendees see the event in their diary, they can access all delegates materials and enjoy full voice and video interaction.

No need to fiddle about with seperate telephone calls, one simple integrated tool.

Once underway your delegates will be part of a fully interactive training online session with questions alerts and everything they are familiar with when they go to a training course.

Did we mention if the event has a pre-course reading list attendees will be able access that too?

So, your Trainers and Delegates are now happy. We think your Finance Team and budget holders should be too.

Stratus Presenter Module allows you to control your budget. A 25 seat, unlimited license costs £5000 per annum and that is it; no further bills which mean simple costing and streamlined administration.

  • Your trainees can reach you where ever they're based.
  • Your customers will not have to factor travel costs.
  • Your tests and materials are online.
  • You administer your schedule and sessions.
  • As a training provider you will be able to charge for these events.
  • One annual bill.
  • "Live online training has been a service many Stratus customers have wanted us to integrate. Blended learning is something we are all familiar with but enabling elearning and live online to be managed within the same system creates a more cohesive and therefor accessible programme for our customers learners."

    — Ruth Davidison, Stratus Enablement Team

    We're booking demonstrations now - contact us now to arrange yours.

    Presenter ModuleGo_to_training

    February Stratus Play List

    There's been no time to ease into the New Year for the Stratus Team.

    The latest reporting and customer branding new features are now due for release with more functionality to follow. Exciting times.

    You'll be hearing more about that so, as something new for 2013 we thought it would be interesting to share what's being heard here!

    This months listening choice is all about musical tranquilty and focus put together by Apiento over at ; a mix of old and new, some obvious some little known - Satie and Debussy through to the modern sounds of Max Richter and Simon Jeffes.

    The Stratus Enablement Team go Wild!

    The Stratus Enablement Team have been extremely busy in the run up to the Christmas break.

    The Team have been aiding our new and existing Stratus Enterprise License holders with the consolidation and updating of their eLearning, and all of the Look & Feel amendments that follow, working to deliver these changes for launch and readiness for 2013.

    As soon as the customer provides us with their eLearning, the Team then first, works with the Customer to ensure the eLearning content is of optimal standard and efficiency, then, the Design Team step in to ensure the layout of the Stratus Virtual Learning Environment (VLE) is bespoke to the needs of the customer.

    Once the customer is then happy with the outcome of their Stratus VLE, it will Go Live, but our Enablement and Design Teams will always be on hand and available to be of assistance.

    With Stratus live customers use the SCORM importer to upload their course libaries however as part of their migration clients often use the process to update and improve content or assessments. The integrated Stratus Content Developer Tool and Assessment Builder are the natural choice for customers elearning developers, and once again our Enablement and Design Teams remain on hand and available to be of assistance - especially with tight timescales in mind.

    "Customers have realised migrating to Stratus enables consolidation of the multitude of eLearning tools and platforms their organisations are using. The move brings both their elearning development and learning environments together to provide a more coherent learning & development strategy whilst streamlining and reducing licensing costs. Great news as we keep both the Learning & Development and Finance Departments of our clients happy!"

    — Ruth Davidison, Stratus Enablement Team

    Cost savings made from consolidation have been used by some customers to fund updates and redesigns of their course suites to obtain better content, on a consolidated platform with reduced forward cost of ownership.

    StratusConsolidateLook and Feel.

    World-Wide Access to Stratus

    Stratus is constantly growing as a market leading, Corporate eLearning Tool.

    We have noticed that many of Stratus' competitors distribute their software by, firstly signing customers up to a 1 month trial, and then approaching the customer to instigate a purchase for the full product software when the trial period has ended. We have come up with a different solution to make Stratus available to anyone in the World, and also, even more consumer friendly.

    Stratus is available to anyone in the world for FREE!!!. Thats right. Anyone can Register and Login to Stratus and create eLearning. The FREE edition of Stratus will allow customers to create small pieces of basic eLearning. There are NO FREE eLearning tools on the market today.

    We understand that some customers will want more out of Stratus. The FREE edition of Stratus is designed mainly for small group training. To allow Stratus to really stretch it's legs, customers can purchase a license for Stratus Enterprise. This is an easy to use, intelligently designed, totally customisable and sustainable way of creating company-wide eLearning.

    Our main goal is for Stratus to be the best. With these two versions; Stratus and Stratus Enterprise, we have catered the needs for customers that want to make a few small pieces of eLearning for FREE and corporate customers who want to make company wide, professional, detailed, adaptable eLearning.


    Stratus Assessments

    Assessments, eLearning

    One of the key features of Stratus is it Assessment Builder tool. It allows users to create assessments and embed them within their Stratus eLearning and to provide on-line certification.

    Surveys show that the vast majority of eLearning assessment based tools and systems do not provide full certification. Stratus addresses this problem by providing a certified registration and tracking solution for certification agencies directly within the eLearning. You can connect your courses and learning with certified bodies to ensure that students complete their training with recognised and certified qualifications and certificates.

    Being a Market-Leading product, Stratus needs to stay ahead of it's competitors. Below is a table showing which Online eLearning Tools do and don't create assessment certificates.


    eLearning Tool Yes No











    Stratus is one of the few if not the only tool on the market that supplies company delegates with certificates if they successfully complete the assessments on their Stratus sites and connnects these with full certification agencies. Please enquire with our support team for further details and to determine if your accreditation needs can be supported by Stratus.


    New Stratus Look and Feel!

    Stratus Look and Feel

    We are delighted to announce an upgrade to the Stratus Look and Feel suite.

    Upon launching the new Look and Feel (LAF) suite which allows customers to fully customise their Stratus eLearning sites to match their company branding, we have received excellent feedback from our Corporate Enterprise Customers. We are now launching the Stratus Public Community Themes Pack allowing users to select from a range of exciting themes and "skins". These have all been developed using the new Stratus Look and Feel suite.

    The Stratus Look and Feel suite allows users to:

    • Insert a Company Logo
    • Change the Background Colour of the page
    • Apply a different colour for the main Toolbars
    • Use different colours for the Header text, the Normal text, and the Link text, and to apply different fonts
    • Change the background colour on the Toolbar tabs that have been selected
    • Apply a different colour to the menu boxes on the page
    • Change the colour of the borders on the menu boxes

    The new range of features are fully supported with new Stratus functionality:

    • Company and User Level LAF Definitions
    • Real-time Preview and Publishing
    • Google Font Support
    • Public Theme Development and Publishing
    • Private Theme and Brand Management (Enterprise)

    This new update has given Stratus' world-wide users more flexibilty on the type of design they want on their sites. It ensures that Stratus is a tool than can be adapted to suit the Look and Feel functionality of any company that uses this Market-Leading tool.

    Look and FeelStratuseLearningNews

    Bureau Veritas goes Live

    Market leaders in Testing, Inspection and Certification Services, Bureau Veritas have worked together with iTrain to create a suite of 8 interactive online eLearning courses covering a range of Health & Safety and compliance related topics.

    Stratus developers have created bespoke Bureau Veritas branded login screens and site pages to enhance the user experience, and reinforce the company identity.

    "This is just the sort of course content Stratus is designed for. It is perfect for the implementation of company wide training."

    — Martin Brown, CEO of iTrain


    Subscribe to News