Bitnami ResourceSpace

    ResourceSpace is a digital asset management system that has been designed to give content creators easy and fast access to print and web ready assets. It is focused on the improvement of collaboration between users when assembling resources together for a project.

    Please, take a look to the Quick Start Guide to know the basic use of this Stack.

    How to start/stop the servers?

    Graphical tool

    The Stacks include a graphical tool to manage the servers easily. You can find the "manager-windows.exe", "manager-osx" or "manager-linux" tool in your installation directory. Using this tool, you can Start, Stop or Restart the servers and check the log files. You can click on the icon to start it.














    On Windows: You can also start the Manager tool from shortcuts: Start -> Program Files -> BitNami Stack -> Manager tool

    Command line tool

    If you prefer, you can use the "" utility from the command line. This script is in the installation directory.


    On Virtual Machines and Cloud images:

    $ sudo /opt/bitnami/ start

    A native installer on Linux:

    $ cd ~/application-version
    $ ./ start



    On OS X: You can start the Manager tool from the installation directory or you can use the "" utility from a Terminal.

    host:~ user$ cd /Applications/application-version
    host:~ user$ ./ start

    How to change the default URL?

    This approach describes how to configure your application to run in the root URL directly. Also, you will be able to modify the URL to a NEW_DOMAIN using the bnconfig tool. The details are described below.

    Automatic Approach

    This approach is based on the bnconfig tool. For more information about the Bitnami Configuration tool, please take a look in this wiki entry

    Bitnami Cloud Hosting

    The best way to change your URL in BCH is to go to your application tab and modify it there. In the Bitnami Cloud Hosting console, select Servers, choose your server, Manage and go to the Applications tab. Press there the pencil next to the application which URL you want to modify and choose .

    Cloud Images and Virtual Machines

    Moving the application to /

     If your application is running in "/resourcespace" you can remove the prefix from the URL executing the following command:

    $ sudo /opt/bitnami/apps/resourcespace/bnconfig --appurl /

    (use --help to check if that option is available for your application)

    Now you will be able to access to the application at http://YOUR_DOMAIN instead of http://YOUR_DOMAIN/resourcespace.

    Updating the IP or hostname

    Some applications require to update the IP/domain if the machine IP/domain changes. The bnconfig tool also has an option which updates the IP automatically during boot, called machine_hostname (use --help to check if that option is available for your application). Note that this tool changes the URL to http://NEW_DOMAIN/resourcespace

    sudo /opt/bitnami/apps/resourcespace/bnconfig --machine_hostname NEW_DOMAIN

    If you already moved your application to the root URL you should include both options at the same time.

    sudo /opt/bitnami/apps/resourcespace/bnconfig --appurl / --machine_hostname NEW_DOMAIN


    If you have configured your machine to use an static domain name or IP, you should rename or remove the "/opt/bitnami/apps/resourcespace/bnconfig" file.

    sudo mv /opt/bitnami/apps/resourcespace/bnconfig /opt/bitnami/apps/resourcespace/bnconfig.disabled


    Native Installer

    Using bnconfig tool you will be able to configure the URL automatically. Some applications include an option to remove the "/resourcespace" prefix from the URL (use --help to check if that option is available for your application). If you want to modify that you can run the following command (substitute installdir with your actual installation directory):

    On Linux,

    installdir/apps/resourcespace/bnconfig --appurl /

    On Mac OS X, 

    installdir/apps/resourcespace/ --appurl /

    On Windows,

    installdir/apps/resourcespace/bnconfig.exe --appurl /

    The bnconfig tool also has an option which updates the IP automatically during boot, called machine_hostname (use --help to check if that option is available for your application). Note that this tool changes the URL to http://NEW_DOMAIN/resourcespace. If you have your application in the root URL you should include both options at the same time.

    sudo /opt/bitnami/apps/resourcespace/bnconfig --machine_hostname NEW_DOMAIN

    If you have configured your application to use an static domain name or IP, you should rename or remove the "installdir/apps/resourcespace/bnconfig" file.

    Tabs end

    Manual Approach

    If you want to change the default URL from http://your_domain/resourcespace to http://your_domain, you should add a "DocumentRoot" entry in your application conf file. Edit the installdir/apps/resourcespace/conf/httpd-prefix.conf file to add this line and commenting the "Alias" entries. Modify the

    httpd_prefix.conf file content (substitute installdir with your actual installation directory, which is /opt/bitnami in Cloud Images and Virtual Machines):

    DocumentRoot "/installdir/apps/resourcespace/htdocs"
    # Alias /resourcespace/ "/installdir/apps/resourcespace/htdocs/"
    # Alias /resourcespace "/installdir/apps/resourcespace/htdocs"

    Some applications also require changes in their configuration files or in the database.

    Moreover, you have to modify the baseurl value in the ResourceSpace configuration file (substitute /opt/bitnami path for your installation directory if you are not using a Virtual Machine or a Cloud instance), removing /resourcespace/ in the URL.

    nano /opt/bitnami/apps/resourcespace/htdocs/include/config.php

    config.php file content

    # Base URL of the installation                                                                                                                           
    $baseurl = 'http://YOUR_IP:YOUR_PORT';

    How to create a full backup of ResourceSpace?

    Because BitNami stacks are self-contained, the simplest option for performing your backups is to copy or compress the BitNami Stack installation directory. To do so in a safe manner, you will need to stop all servers, so this method may not be appropriate if you have people accessing the application continously.

    linux_platform.pngOn Virtual Machines and Cloud Images:

    sudo /opt/bitnami/ stop


    On OS X:

    $ cd installdir
    $ ./ stop
    $ cp -r installdir application-backup

    Or you can create a tarball:

    $ tar -czvf application-backup.tar.gz installdir

    Or a zip file:

    $ zip -r installdir/*

    To restore this backup you only need to uncompress the backup in the same location. It is important to use the same path that was used when the stack was originally installed.

    For example if you have a backup in a Red Hat machine, you can copy it to an Ubuntu Linux machine (a different distro!) in the same location. Then start the servers and that’s all.

    On Virtual Machines and Cloud Images:

    $ sudo /opt/bitnami/ start

    On OS X:

    $ cd installdir
    $ ./ start

    You just need to be carefull to keep the same permissions for the files and folders. If you installed as root make sure that in the new machine you copy the files also as root. And this case, if you are also moving MySQL or PostgreSQL, you will need to create those users in the new machine (if they don't exist yet).

    win_platform.png On Windows you should follow the same process. Stop the servers using the shortcuts and copy the whole installation directory. To restore the system, copy the directory to a different Windows machine in the same location and follow these steps from a command prompt:

    $ cd installdir
    $ serviceinstall.bat INSTALL

    You can access your BitNami Application at the usual URL.

    If you want to create only a database backup, check the following link for MySQL /Components/MySQL#How_to_create_a_database_backup or for PostgreSQL /Components/PostgreSQL#How_to_create_a_database_backup.3f

    How to upgrade ResourceSpace?

    It is strongly recommended that you create a backup before starting the update process. If you have important data, it is advisable that you create and try to restore a backup to ensure that everything works properly.

    There are two different ways to upgrade your application.

    1. If you want to upgrade the application and all Stack components PHP, Ruby, MySQL, Apache… You can follow the steps described at How to upgrade the full Stack migrating the data?
    2. In case you only want to upgrade the application code without modifying any other Stack components,  you should follow the guide which is in the application page itself.


    In the ResourceSpace case, here are the steps to upgrade the stack. The steps described here are related to Virtual Machines and Cloud Hosting, so if you are using an installer, you have to change /opt/bitnami for your actual installation path.

    1. As said above, take a backup of your whole stack, so that if anything goes wrong, you can restore it. The most important file is config.php, which stores all the ResourceSpace configuration settings (/opt/bitnami/apps/resourcespace/htdocs/include/config.php).
    2. Stop all the services
      sudo /opt/bitnami/ stop
    3. Download the ResourceSpace version from the official website
      cd /home/bitnami
    4. Copy all files from the new version over the top of the old files, which are located in /opt/bitnami/apps/resourcespace/htdocs. Alternatively, remove existing files first (except /filestore) and copy the new files in htdocs, so that if for example files have changed location, duplications can be prevented.
      cd /opt/bitnami/apps/resourcespace/htdocs
    • When executing the command below select A [overwrite all files] when you are prompted with the message if you want to overwrite.


      unzip /home/bitnami/
    1. Replace any files you had changed locally from your backup copy, for example config.php, title.gif etc.
    2. Restart the services
      sudo /opt/bitnami/ start

    How to install a plugin on ResourceSpace?

    Custom plugins can be uploaded as .rsp file through the web interface, in Team Center->Manage Plugins. There you will find a list with the plugins installer and information about them, as well as a button to upload the plugin .rsp file. The plugins folder must be writable by the web server.

    How to configure the email settings of ResourceSpace?

    You can configure the SMTP  of your email provider by copying the email section in the /installdir/apps/resourcespace/htdocs/include/config.default.php into the /installdir/apps/resourcespace/htdocs/include/config.php file, modifying what you need with your actual data. For instance, if you want to configure it using Gmail as SMTP server, you have to do something like this.

    # Use an external SMTP server for outgoing emails (e.g. Gmail).
    # Requires $use_phpmailer.
    # SMTP settings:
    $smtp_secure='tls'; # '', 'tls' or 'ssl'. For Gmail, 'tls' or 'ssl' is required.
    $smtp_host=''; # Hostname, e.g. ''.
    $smtp_port=587; # Port number, e.g. 465 for Gmail using SSL.
    $smtp_auth=true; # Send credentials to SMTP server (false to use anonymous access)
    $smtp_username=''; # Username (full email address).
    $smtp_password='your_password'; # Password.

    How to enable SSL?

    You can see how to configure Apache to enable SSL connections at How to enable SSL to access through https?

    How to debug ResourceSpace errors?

    Once Apache starts, it will create two log files, the access_log and the error_log /installdir/apache2/logs directory or in /var/log/httpd if you are using Amazon Linux or Red Hat Enterprise cloud images.

    In Virtual Machines, Cloud Images and Ubuntu based Bitnami Cloud Hosting images installdir is /opt/bitnami.

    The access_log file is used to track client requests. When a client requests a document from the server, Apache records several parameters associated with the request in this file, such as: the IP address of the client, the document requested, the HTTP status code, and the current time.

    The error_log file is used to record important events. This file includes error messages, startup messages, and any other significant events in the life cycle of the server. This is the first place to look when you run into a problem when using Apache.

    If no error is found, you will see a message similar to:

    Syntax OK
    /installdir/ : httpd started

    The main MySQL log file is created at /installdir/mysql/data/mysqld.log file.

    How to increase the allowed size of the uploaded files?

    You can modify the following option in the php.ini file to increase the allowed size for uploads:

    ; Maximum size of POST data that PHP will accept.
    post_max_size = 16M
    ; Maximum allowed size for uploaded files.
    upload_max_filesize = 16M

    Tag page (Edit tags)
    • No tags
    Page statistics
    6849 view(s), 15 edit(s) and 5988 character(s)


    You must login to post a comment.

    Attach file