Bitnami ProcessWire

    ProcessWire is a free PHP5 content management system and framework (open source CMS/CMF) built to save you time and work the way you do. ProcessWire gives simpler and stronger control over your pages, fields, templates and markup at any scale. And it provides a powerful template system that works the way you already do.

    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.

    manager-servers.png

     

    manager-osx.png

     

     

     

     

     

     

     

     

     


    win_platform.png

    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 "ctlscript.sh" utility from the command line. This script is in the installation directory.

    linux_platform.png

    On Virtual Machines and Cloud images:

    $ sudo /opt/bitnami/ctlscript.sh start

    A native installer on Linux:

    $ cd ~/application-version
    $ ./ctlscript.sh start
    

    mac_platform.png

     

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

    host:~ user$ cd /Applications/application-version
    host:~ user$ ./ctlscript.sh 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 Bitnami Configuration Tool (bnconfig).

    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 "/processwire" you can remove the prefix from the URL executing the following command:

    $ sudo /opt/bitnami/apps/processwire/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/processwire.

    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/processwire

    sudo /opt/bitnami/apps/processwire/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/processwire/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/processwire/bnconfig" file.

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

     

    Native Installer

    Remember to use your actual installation directory instead of installdir.

    Moving the application to /

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

    On Linux,

    installdir/apps/processwire/bnconfig --appurl /
    

    On Mac OS X, 

    installdir/apps/processwire/bnconfig.app/Contents/MacOS/installbuilder.sh --appurl /
    

    On Windows,

    installdir/apps/processwire/bnconfig.exe --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/processwire.

    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/processwire.

    installdir/apps/processwire/bnconfig --machine_hostname NEW_DOMAIN
    

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

    installdir/apps/processwire/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/processwire/bnconfig" file.

    mv installdir/apps/processwire/bnconfig installdir/apps/processwire/bnconfig.disabled
    

    Tabs end

    Manual Approach

    If you want to change the default URL from http://your_domain/processwire to http://your_domain, you should add a "DocumentRoot" entry in your application conf file. Edit the installdir/apps/processwire/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/processwire/htdocs"
    # Alias /processwire/ "/installdir/apps/processwire/htdocs/"
    # Alias /processwire "/installdir/apps/processwire/htdocs"
    
    (...)
    

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


    In the ProcessWire case, appart from the changes done before, you have to modify the htaccess.conf file (change the path to your own installation directory, we use /opt/bitnami as it's done in our VM and in Bitnami Cloud Hosting). Edit the file

    sudo nano /opt/bitnami/apps/processwire/conf/htaccess.conf
    

    And comment the line which includes the RewriteBase directive

    ...
    #RewriteBase /processwire/
    ...
    

    Finally, restart the Apache server

    sudo /opt/bitnami/ctlscript.sh restart apache
    

    How to create a full backup of ProcessWire?

    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/ctlscript.sh stop

    mac_platform.png

    On OS X:

    $ cd installdir
    $ ./ctlscript.sh 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 application-backup.zip 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/ctlscript.sh start

    On OS X:

    $ cd installdir
    $ ./ctlscript.sh 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 ProcessWire?

    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 ProcessWire case, the upgrade is quite easy.

    First of all, if you have 3rd party modules installed, confirm that they are compatible with the ProcessWire version you are upgrading to. If you cannot confirm compatibility, uninstall the 3rd party modules before upgrading, when possible. You can attempt to re-install them after upgrading.

    Then, you just have to replace these files from your old version with those from the new:

    ```
    /htdocs//wire/

    /htdocs/index.php

    /conf/htaccess.conf

    ```

    Replacing the above directory/files is typically the primary thing you need to do in order to upgrade. But please see the version-to-version specific upgrade notes documented in the official ProcessWire site http://processwire.com

    Replacing the wire directory

    When you replace the /wire/ directory, make sure that you remove or rename the old one first. If you just copy or FTP changed files into the existing /wire/ directory, you will end up with both old and new files, which will cause an error.

    Replacing the index.php file

    This file doesn't change often between minor versions. As a result, you don't need to replace this file unless it has changed. But when in doubt, you should replace it.

    Replacing the htaccess.conf file

    This is also a file that does not always change between versions. But when it changes, it is usually important for security that you are up-to-date. When in doubt, replace your old htaccess.conf file with the content of the htaccess.txt file from the new version. In Bitnami Stacks, we move the content of the .htaccess files to htaccess.conf, as explained here http://wiki.bitnami.com/Components/Apache/htaccess_configuration

    Be sure that any modification done in the htaccess.conf file are done too in the new htaccess before replacing it, so that everything works properly. By default, we wrap the content of the htaccess.txt file in a Directory directive, and we add a RewriteBase directive too. It means, something like this:

     

    <Directory "/opt/bitnami/apps/processwire/htdocs">
    ...
    ...
    RewriteBase /processwire/
    ..
    ..
    </Directory>
    

    How to install a plugin on ProcessWire?


    You can install ProcessWire modules in the Bitnami ProcessWire stack. To download them you can go to the official site http://modules.processwire.com/ where you will find a bunch of modules.


    To install them, the steps are

    1. Place the .module file in your /site/modules/ directory. If the module contains more than one file (like supporting .css or .js files for example), it should be created in it's own directory under /site/modules/ with the same name as the module. For instance, the AdminBar module and supporting files should be placed in /site/modules/AdminBar/.
    2. Login to your ProcessWire admin and click on the Modules tab. Click the check for new modules button. Click the install button next to any of the new modules that you want to install.

    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 ProcessWire 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/ctlscript.sh : httpd started
    

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


    About ProcessWire, you have the log files under the directory installdir/apps/processwire/htdocs/site/assets/logs

    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
    

    If you have enabled PHP-FPM (enabled by default in Cloud Images and VMs) you need to restart PHP-FPM running the following command:

    sudo /opt/bitnami/ctlscript.sh restart php-fpm
    

    Note: For native installers replace /opt/bitnami with your current installation directory.

    Tag page (Edit tags)
    • No tags
    Page statistics
    6740 view(s), 12 edit(s) and 6224 character(s)

    Comments

    You must login to post a comment.

    Attach file

    Attachments