Lavagna HELP
  1. 1About
  2. 2Install
    1. 2.1Database
      1. 2.1.1MySql
      2. 2.1.2MariaDB
      3. 2.1.3PostgreSQL
      4. 2.1.4HSQLDB
    2. 2.2Configuration
      1. 2.2.1Self contained
      2. 2.2.2Servlet container
    3. 2.3Setup
      1. 2.3.1Step 1, Base url or import
      2. 2.3.2Step 2, Login provider configuration
        1. 2.3.2.1Demo provider
        2. 2.3.2.2Ldap provider
        3. 2.3.2.3Oauth provider
        4. 2.3.2.4Preconfigured oauth providers
        5. 2.3.2.5Custom oauth providers
      3. 2.3.3Step 3 Insert administator
      4. 2.3.4Step 4 Confirm
  3. 3Configuration and Administration
    1. 3.1Configuration parameters
    2. 3.2Login
      1. 3.2.1Anonymous user access
      2. 3.2.2Login providers
        1. 3.2.2.1Demo
        2. 3.2.2.2Ldap
        3. 3.2.2.3Oauth
        4. 3.2.2.4Preconfigured oauth providers
        5. 3.2.2.5Configurable oauth providers
    3. 3.3SMTP configuration
    4. 3.4Users
      1. 3.4.1Create a user
      2. 3.4.2Import users from a file
    5. 3.5Roles and permissions
      1. 3.5.1Roles
      2. 3.5.2Permissions
    6. 3.6Import/Export data
      1. 3.6.1Exporting
      2. 3.6.2Importing
  4. 4User Manual
    1. 4.1Get Started
    2. 4.2Project
      1. 4.2.1Create a project
      2. 4.2.2Create a board
      3. 4.2.3Project statistics
      4. 4.2.4Project milestones
    3. 4.3Board
      1. 4.3.1Columns
        1. 4.3.1.1Create a new column
        2. 4.3.1.2Change the name of a column
        3. 4.3.1.3Column menu
      2. 4.3.2Archive, Backlog, and Trash
      3. 4.3.3Card menu
      4. 4.3.4Interact with the board
      5. 4.3.5Bulk operations
      6. 4.3.6Create a Card
    4. 4.4Card
      1. 4.4.1Card
        1. 4.4.1.1View and manage a single card
        2. 4.4.1.2Card header
        3. 4.4.1.3Left column
        4. 4.4.1.4Quick action panel
        5. 4.4.1.5Dates
        6. 4.4.1.6People
        7. 4.4.1.7Milestones
        8. 4.4.1.8Center column
        9. 4.4.1.9Description
        10. 4.4.1.10Comments Tab
        11. 4.4.1.11Files Tab
        12. 4.4.1.12Activity Tab
        13. 4.4.1.13Right column
        14. 4.4.1.14Labels
        15. 4.4.1.15Action lists
      2. 4.4.2Comments
        1. 4.4.2.1Add a new comment
        2. 4.4.2.2Link to a single comment
        3. 4.4.2.3Update a comment
        4. 4.4.2.4Delete a comment
      3. 4.4.3Files
        1. 4.4.3.1Upload files
        2. 4.4.3.2Delete files
      4. 4.4.4Manage lists
        1. 4.4.4.1Create a new action list
        2. 4.4.4.2Move and sort
        3. 4.4.4.3Update
        4. 4.4.4.4Delete
    5. 4.5User
      1. 4.5.1User page
      2. 4.5.2Change user settings
    6. 4.6Search
      1. 4.6.1Filters
        1. 4.6.1.1label
        2. 4.6.1.2to
        3. 4.6.1.3by
        4. 4.6.1.4created
        5. 4.6.1.5watched
        6. 4.6.1.6updated
        7. 4.6.1.7due
        8. 4.6.1.8updated by
        9. 4.6.1.9milestone
        10. 4.6.1.10status
        11. 4.6.1.11location
        12. 4.6.1.12Free text search
      2. 4.6.2Single board search
      3. 4.6.3Global and project specific search
    7. 4.7Project Administration
      1. 4.7.1Project and boards settings
      2. 4.7.2Manage milestones
      3. 4.7.3Manage Access
      4. 4.7.4Manage labels
        1. 4.7.4.1Creation
        2. 4.7.4.2Update
          1. 4.7.4.2.1Update List
        3. 4.7.4.3Delete
      5. 4.7.5Customize status color
      6. 4.7.6How to import your data from Trello

2.1Database

Lavagna support the following databases:

  • MySQL version 5.1 or later
  • MariaDB version 10.0 or later
  • PostgreSQL version 9.2 or later
  • embedded HSQLDB version 2.3.1

If it’s not possible to use MySql or Postgresql and the full text search feature is not important, the HSQLDB backend can be used with a file backend. See the HSQLDB section below.

2.1.1MySql

When using MySql, for ensuring a good full text search experience, it’s advisable to set in the MySql configuration file:

[mysqld]
ft_min_word_len=3

The default 4 minimal word length can be problematic for searching 3 letters acronyms.

Additionally, when creating the database, it must ensured that utf-8 is used everywhere:

CREATE DATABASE lavagna CHARACTER SET utf8 COLLATE utf8_bin;

2.1.2MariaDB

Unit tests are run also on MariaDB and as a general rule everything that must be done for MySql must be done also for MariaDB.

2.1.3PostgreSQL

When using PostgreSQL, ensure that the database/schema is in utf-8.

For the full text search support, the unaccent extension must be present. In general it’s already included in the PostgreSQL
installation. If it’s not present, an error will be launched when running lavagna the first time.

2.1.4HSQLDB

It’s the default development database. But it’s possible to use it a persistent way: when configuring the jdbc url, the file backend can be used: -Ddatasource.url=jdbc:hsqldb:file:lavagna.