BitNami Weblate

     
    Weblate is a web based translation tool with tight Git integration. It features simple and clean user interface, propagation of translations across subprojects, consistency checks and automatic linking to source files. Weblate is written in Python and powered by the Django application framework.

    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?

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

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

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

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

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

     

    Native Installer

    Remember to use your actual installation directory instead of installdir.

    Moving the application to /

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

    On Linux,

    installdir/apps/weblate/bnconfig --appurl /
    

    On Mac OS X, 

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

    On Windows,

    installdir/apps/weblate/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/weblate.

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

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

    mv installdir/apps/weblate/bnconfig installdir/apps/weblate/bnconfig.disabled
    

    Tabs end

    Manual Approach

    If you want to change the default URL from "http://your_domain/weblate" to "http://your_domain you need to follow the steps below.

    1. Stop the servers

    2. Edit installdir/apps/weblate/conf/weblate.conf to point to / instead of /weblate

      WSGIScriptAlias / "/home/bitrock/weblate-1.3-0/apps/weblate/scripts/weblate.wsgi" 
      Alias /media/ "/home/bitrock/weblate-1.3-0/apps/weblate/weblate/media/"
      Alias /static/ "/home/bitrock/weblate-1.3-0/apps/django/lib/python2.7/site-packages/django/contrib/admin/static/"
      
    3. Take a look at the settings.py file in installdir/apps/weblate/weblate and modify the line below removing /weblate :

      URL_PREFIX = ''
      
    4. Start the servers

    Now your Weblate instance should be available in http://your_domain

    How to create a full backup of BitNami Weblate Stack?

    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 BitNami Weblate Stack?

    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

    First of all stop your servers and copy the installdir/apps/weblate directory in case something fails and you need to restore it. (In fact, you can copy all installdir, that would be better in case during the upgrade the database get inconsistent).

    Now if you are on linux or in mac you should execute the use_weblate script.

    In the console execute:

    cd installdir/apps/weblate/weblate/
    python manage.py syncdb
    python manage.py migrate
    

    More information can be found in the official documentation at: https://weblate.readthedocs.org/en/latest/install.html#upgrading.

    How to start a project in BitNami Weblate Stack?

    To create a project in Weblate, you have to access to the administrator interface. To do so, just go to http://your_domain/weblate/admin and log in. Afterwards, create a project. In order to begin translating a project, you also have to create a subproject and at least one translation from the admin interface too.

    In the creation of the subproject, you will be asked to introduce two mandatory parameters, the url to the repository and the pattern of the language files.

    Due to the multiple possible combinations we recommend to read de official documentation at http://weblate.readthedocs.org/en/latest/

    How to configure the email settings of BitNami Weblate Stack?

    You can configure the email settings my editing the file global-settings.py file in installdir/apps/django/lib/python2.7/site-packages/django/conf. For instance, using GMail:

    EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
    EMAIL_HOST = 'smtp.gmail.com'
    EMAIL_PORT = 587
    EMAIL_HOST_USER = 'your_account@gmail.com'
    EMAIL_HOST_PASSWORD = 'your_password'
    EMAIL_USE_TLS = True
     
    Do not forget to restart the Apache server everytime you change the globlal-settings.py file.

    How to enable SSL?

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

    Tag page (Edit tags)
    • No tags
    Page statistics
    9650 view(s), 8 edit(s) and 5879 character(s)

    Comments

    You must login to post a comment.

    Attach file

    Attachments