[Support] ImSkully - Vikunja

[ImSkully]

 

Vikunja is the to-do application to organize your life. The open-source, self-hostable to-do app - organize everything, on all platforms. Think of Vikunja like the notebook you have with all your things to keep track of. But with superpowers.

 

Website | Registry | Documentation | Template Repo

 

This application template is a single container that runs both the Vikunja API and frontend application in a one-click install with no configuration required to have Vikunja be up and running locally within a matter of seconds, or optionally adjust the configuration settings in the template options to customize your installation.

Vikunja Features

• Stay Organized
  Organize all of your tasks in projects. Create sub-projects, organize everything hierarchical and keep related stuff grouped together.
   
• Collaborate With Peers

  Vikunja lets you easily share a project with another user or a whole team! Assignments show who's working on what.

• Use it How You Need It
  You can view your tasks in the classic list view - or in a Gantt Chart, or Table view, or Kanban Board. Whatever you need!
   

• Built For Speed
  Vikunja is built with speed in mind - every interaction takes less than 100ms. No more loading spinners.
   
• Import Tasks From Todoist, Trello or Microsoft To-Do
  Because work does not happen in one tool only.

 

More information and screenshots can be found on the website.

Requirements

There are no requirements for this template!

Installation & Setup

1. Install Vikunja from community applications (ImSkully's Repository)
    
2. (Optional) Update template variables as required:
   1. Database: By default, the template runs using a SQLite database to store your data in the application directory - to use a separate database engine such as MySQL or Postgres, adjust the VIKUNJA_DATABASE_TYPE variable and other respective database variables with your details.
   2. Mailer: The Vikunja Mailer can send emails to users for certain actions such as reminders, to enable this feature set VIKUNJA_MAILER_ENABLED to true and configure the respective mailer variables with your details.
3. Done! Create the container and once it has started, the web UI should be available at the configured port and you will now be able to register and create your account.

Additional Configuration

There are a number of additional variables available to customize your Vikunja instance, simply edit the container and adjust the existing template variables to your liking. The currently available variables in the configuration is not an exhaustive list of all options, please see  the Configuration Options page in Vikunja's documentation for a full list of configuration options available.

Support

If you have any issues with the template or it has gone out of date, please let me know and I will update it - otherwise you are welcome to leave any support queries below.

Edited February 12 by ImSkully

[ImSkully]

Existing Vikunja (< v0.23.0) Users

If you are an existing user of Vikunja on Unraid (from A75G's repository) running separate containers for the API and frontend application, the new 0.23.0 release of Vikunja combines both applications into a single package (see changelog here for what's new in this version). This template aims to simplify the setup and configuration of Vikunja on Unraid and will automatically update with the latest application changes.

 

To migrate over to this template, you can simply stop your existing containers and install this template as normal and setup the database configuration to that of your previous settings from the vikunja-api container. Once the container has started and you have verified your existing account(s) and data are still present, then the old containers can safely be deleted.

Edited February 12 by ImSkully

[unn4m3d]

Does anyone have a working SWAG Config file for vikunja? 

 

I currently use this, which ends up in a 502 error: 

 

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name vikunja.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for Authelia
   # include /config/nginx/authelia-server.conf;

    location / {
        # enable for Authelia
        #include /config/nginx/authelia-location.conf;

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app vikunja;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

       # root   /;
       # try_files $uri $uri/ /;
       # index  index.html index.htm;
        
    }
    
    location ~* ^/(api|dav|\.well-known)/ {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $api_app  vikunja-api;
        set $api_port 3456;
        set $api_proto http;
        proxy_pass $api_proto://$api_app:$api_port;
        client_max_body_size 20M;
    }
}

 

Any help is greatly appreciated, thanks!