#Wunderlist login full#
#Wunderlist login password#
#Wunderlist login free#

The maximum size clients will be able to request for user avatars. This setting will not affect the cli commandsĮnvironment path: VIKUNJA_SERVICE_ENABLEUSERDELETION maxavatarsize # It may be required to coordinate with them in order to delete the account. When using external authentication methods If true, will allow users to request the complete deletion of their account. If enabled, vikunja will send an email to everyone who is either assigned to a task or created it when a task reminderĮnvironment path: VIKUNJA_SERVICE_ENABLEEMAILREMINDERS enableuserdeletion # You should never use this unless you know exactly what you’re doingĮnvironment path: VIKUNJA_SERVICE_TESTINGTOKEN enableemailreminders # Because this is quite a dangerous feature allowing for lots of harm,Įach request made to this endpoint neefs to provide an Authorization: header with the token from below. Used to reset the db before frontend tests. If not empty, this will enable /test/ endpoints which allow to put any content in the database. If not empty, enables logging of crashes and unhandled errors in sentry.Įnvironment path: VIKUNJA_SERVICE_SENTRYDSN testingtoken # In most cases you want to leave that enabled.Įnvironment path: VIKUNJA_SERVICE_ENABLETOTP sentrydsn # Whether task comments should be enabled or notĮnvironment path: VIKUNJA_SERVICE_ENABLETASKCOMMENTS enabletotp # UTC or GMT offsets won’t work.Įnvironment path: VIKUNJA_SERVICE_TIMEZONE enabletaskcomments # Please note that time zones have to use the official tz database names. Whether to enable task attachments or notĮnvironment path: VIKUNJA_SERVICE_ENABLETASKATTACHMENTS timezone # Whether to let new users registering themselves or notĮnvironment path: VIKUNJA_SERVICE_ENABLEREGISTRATION enabletaskattachments # Set the motd message, available from the /info endpointĮnvironment path: VIKUNJA_SERVICE_MOTD enablelinksharing #Įnvironment path: VIKUNJA_SERVICE_ENABLELINKSHARING enableregistration # The max number of items which can be returned per pageĮnvironment path: VIKUNJA_SERVICE_MAXITEMSPERPAGE enablecaldav #Įnable the caldav endpoint, see the docs for more detailsĮnvironment path: VIKUNJA_SERVICE_ENABLECALDAV motd # Set to the path of the frontend files to host frontend alongside the api.Įnvironment path: VIKUNJA_SERVICE_STATICPATH maxitemsperpage # Path on the file system to serve static files from. With a config file which will then be used.Įnvironment path: VIKUNJA_SERVICE_ROOTPATH staticpath # Vikunja will also look in this path for a config file, so you could provide only this variable to point to a folder The base path on the file system where the binary and assets are.

The URL of the frontend, used to send password reset emails.Įnvironment path: VIKUNJA_SERVICE_FRONTENDURL rootpath #

0o660Įnvironment path: VIKUNJA_SERVICE_UNIXSOCKETMODE frontendurl # Note that octal values must be prefixed by “0o”, e.g. If set, it will be created and used instead of tcpĮnvironment path: VIKUNJA_SERVICE_UNIXSOCKET unixsocketmode # The interface on which to run the webserverĮnvironment path: VIKUNJA_SERVICE_INTERFACE unixsocket # The default is 2592000 seconds (30 Days).Įnvironment path: VIKUNJA_SERVICE_JWTTTLLONG interface #

The long param set, the token returned will be valid for this period. The duration of the “remember me” time in seconds. The duration of the issed JWT tokens in seconds.Įnvironment path: VIKUNJA_SERVICE_JWTTTL jwtttllong # (This means all already issued tokens will be invalid once you restart vikunja)Įnvironment path: VIKUNJA_SERVICE_JWTSECRET jwtttl # This token is used to verify issued JWT tokens.ĭefault is a random token which will be generated at each startup of vikunja. To better grasp how the nesting looks like. The docs below aim to reflect that leveling, but please also have a lookt at the default config file Most config variables are nested under some “higher-level” key.įor example, the interface config variable is a child of the service key. If you don’t provide a value in your config file, their default will be used.

You can find a full example configuration file in here. The following explains all possible config variables and their defaults.

In the service.rootpath location set in a config (remember you can set config arguments via environment variables)ĭefault configuration with explanations #.

Vikunja will search on various places for a config file: Vikunja provides a default config.yml file which you can use as a starting point.

We reccomend yaml or toml, but you’re free to use whatever you want. Vikunja supports using toml, yaml, hcl, ini, json, envfile, env variables and Java Properties files.

#Wunderlist login password#

#Wunderlist login full#

#Wunderlist login free#