BitNami Tracks

    Tracks is a Ruby on Rails web-based application to help you implement David Allen’s Getting Things Done methodology. Tracks is Open Source and licensed under the GNU GPL.

    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?

    If you want to change Tracks to the root url you should follow the next next section. In this section you can see how to replace the URL "/tracks" with "/new_url".

    linux_platform.png  mac_platform.pngOn Linux and OS X, you should modify the following options in the "installdir/apps/tracks/config/tracks.conf" file. Note if you are using the Virtual Appliacne or the AMI, replace installdir with "/opt/bitnami" by default.

    <Location /new_name>
      SetEnv RAILS_RELATIVE_URL_ROOT "/new_name"
      RackBaseURI /new_name
    </Location>                                                    
    ...                                              
    PassengerPreStart http://127.0.0.1/new_name
    

    It is also necessary to update the symbolic link that you can find in /installdir/apache2/htdocs folder:

    $ cd /installdir/apache2/htdocs
    $ ln -s ../apps/tracks/htdocs/public new_name
    

    Then, restart the server:

    $ ./ctlscript.sh restart apache
    


    win_platform.pngOn Windows it is necessary to modify the Apache configuration. Edit "installdir/apps/tracks/conf/tracks.conf" the file to modify the "/tracks" setting:

    ProxyPass /tracks balancer://trackscluster
    ProxyPassReverse /tracks balancer://trackscluster
    
    <Proxy balancer://trackscluster>
      BalancerMember http://127.0.0.1:3001/tracks
    </Proxy>

    You should modify the "installdir/apps/tracks/scripts/serviceinstall.bat" and change the prefix entry "--prefix /tracks".  You should also update the prefix in the "installdir/apps/tracks/htdocs/config/additional_environment.rb" file.

    Then run the following command from a command prompt with Admin privileges:

    > cd “C:\bitnami\Tracks-2.2.1-2\apps\tracks\scripts”
    > serviceinstall.bat UNINSTALL
    > serviceinstall.bat INSTALL
    

    Then restart the Apache server using the Manager graphical application.

    How to change the default URL to the root?

    To do so, first step is comment the subdir property in the installdir/apps/tracks/htdocs/config/site.yml file:

    # subdir = '/tracks'

      mac_platform.pngOn Linux and OS linux_platform.pngX, you can change the "installdir/apps/tracks/conf/tracks.conf" file to modify the "/tracks" url to the root url. You can find below a configuration example. Please take into account that your current tracks.conf file may be a little bit different. You should modify the "installdir/apps/tracks/config/tracks.conf" file according to the changes that you can see in bold:

    DocumentRoot /installdir/apps/tracks/htdocs/public
    
    <Directory "/installdir/apps/tracks/htdocs/public">
        Options -MultiViews
        <IfVersion < 2.3 >
        Order allow,deny
        Allow from all
        </IfVersion>
        <IfVersion >= 2.3>
        Require all granted
        </IfVersion>
    </Directory>
    
    PassengerPreStart http://127.0.0.1:8080/
    

    Then restart the Apache server.

    win_platform.pngOn Windows it is necessary to modify the Apache configuration. Edit "installdir/apps/tracks/conf/tracks.conf" the file to remove the "/tracks" setting:

    <VirtualHost *:80>
      ServerAdmin user@example.com
      ServerName example.com
      RewriteEngine On
      # Redirect non-static requests to cluster                                     
      RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
      RewriteRule ^/(.*)$ balancer://trackscluster%{REQUEST_URI} [P,QSA,L]
    </VirtualHost>
    
    #ProxyPass / balancer://trackscluster
    #ProxyPassReverse / balancer://trackscluster
    
    <Proxy balancer://trackscluster>
      BalancerMember http://127.0.0.1:3001
      BalancerMember http://127.0.0.1:3002
    </Proxy>
    

     

    You should modify the "installdir/apps/tracks/scripts/serviceinstall.bat" and remove the prefix entry "--prefix /tracks". You should also remove the "installdir/apps/tracks/htdocs/config/additional_environment.rb" file which ships the prefix too. Then run the following command from a command prompt with Admin privileges:

    > cd “C:\bitnami\Tracks-2.2.1-2\apps\tracks\scripts”
    > serviceinstall.bat UNINSTALL
    > serviceinstall.bat INSTALL 
    

    Then restart the Apache server. You can use the Manager graphical tool to restart it. Do not forget to refresh the web page to clean the cache.

     

    In both cases, before restarting the Apache server, you should precompile the assets again. To do so:

    cd /installdir/
    ./use_tracks
    cd apps/tracks/htdocs
    ruby bin/rake assets:clean RAILS_ENV=production
    ruby bin/rake assets:precompile RAILS_ENV=production RAILS_RELATIVE_URL_ROOT='/'
    

    How to create a full backup of Tracks?

    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 Tracks?

    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.

    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?

    Tag page (Edit tags)
    • No tags
    Page statistics
    8774 view(s), 3 edit(s) and 7480 character(s)

    Comments

    You must login to post a comment.

    Attach file

    Attachments