Hey, loved the demo and figured I’d try to deploy Vikunja at home to help my family get a bit more organized.
I got the back and front ends installed, but I must’ve gotten wires crossed. I get the web interface but cannot register. Any idea where I might have gone wrong?
This is the console error report pulled from Opera.
Microsoft Edge gives a different set: (maybe the same causes?)
- Unhandled promise rejection Error: Network Error
- CONSOLE21301: serviceWorker.register is rejected due to unsecure context or host restriction in http://192.168.102.13/login.
- Error during service worker registration: SecurityError
RewriteRule ^/?(config.json|favicon.ico|css|fonts|images|img|js) - [L]
RewriteRule ^(.)$ /index.html [QSA,L]
$This token is used to verify issued JWT tokens.
$Default is a random token which will be generated at each startup of vikunja.
$ (This means all already issued tokens will be invalid once you restart vikunja)
$ The interface on which to run the webserver
$ The URL of the frontend, used to send password reset emails.
$ The base path on the file system where the binary and assets are.
$ Vikunja will also look in this path for a config file, so you could provide only this variable to point to a folder
$ with a config file which will then be used.
$ The max number of items which can be returned per page
$ If set to true, enables a /metrics endpoint for prometheus to collect metrics about the system
$ You’ll need to use redis for this in order to enable common metrics over multiple nodes
$ Enable the caldav endpoint, see the docs for more details
$ Set the motd message, available from the /info endpoint
$ Enable sharing of lists via a link
$ Whether to let new users registering themselves or not
$ Whether to enable task attachments or not
$ The time zone all timestamps are in
$ Whether task comments should be enabled or not
$ Database type to use. Supported types are mysql, postgres and sqlite.
$ Database user which is used to connect to the database.
$ Databse password
$ Databse host
$ Databse to use
$ When using sqlite, this is the path where to store the data
$ Sets the max open connections to the database. Only used when using mysql and postgres.
$ Sets the maximum number of idle connections to the db.
$ The maximum lifetime of a single db connection in miliseconds.
$ Secure connection mode. Only used with postgres.
$ (see https://pkg.go.dev/github.com/lib/pq?tab=doc#hdr-Connection_String_Parameters)
$ If cache is enabled or not
$ Cache type. Possible values are memory or redis, you’ll need to enable redis below when using redis
$ When using memory this defines the maximum size an element can take
$ Whether to enable redis or not
$ The host of the redis server including its port.
$ The password used to authenicate against the redis server
$ 0 means default database
$ Whether to enable or disable cors headers.
$ A list of origins which may access the api.
$ How long (in seconds) the results of a preflight request can be cached.
$ Whether to enable the mailer or not. If it is disabled, all users are enabled right away and password reset is not possible.
$ SMTP Host
$ SMTP Host port
$ SMTP username
$ SMTP password
$ Wether to skip verification of the tls certificate on the server
$ The default from address when sending emails
$ The length of the mail queue.
$ The timeout in seconds after which the current open connection to the mailserver will be closed.
$ A folder where all the logfiles should go.
$ Whether to show any logging at all or none
$ Where the error log should go. Possible values are stdout, stderr, file or off to disable error logging.
$ Where the normal log should go. Possible values are stdout, stderr, file or off to disable standard logging.
$ Whether or not to log database queries. Useful for debugging. Possible values are stdout, stderr, file or off to disable database logging.
$ Whether to log http requests or not. Possible values are stdout, stderr, file or off to disable http logging.
$ Echo has its own logging which usually is unnessecary, which is why it is disabled by default. Possible values are stdout, stderr, file or off to disable standard logging.
$ whether or not to enable the rate limit
$ The kind on which rates are based. Can be either “user” for a rate limit per user or “ip” for an ip-based rate limit.
$ The time period in seconds for the limit
$ The max number of requests a user is allowed to do in the configured time period
$ The store where the limit counter for each user is stored. Possible values are “memory” or “redis”
$ The path where files are stored
basepath: ./files # relative to the binary
$ The maximum size of a file, as a human-readable string.
$ Warning: The max size is limited 2^64-1 bytes due to the underlying datatype
$ These are the settings for the wunderlist migrator
$ Wheter to enable the wunderlist migrator or not
$ The client id, required for making requests to the wunderlist api
$ You need to register your vikunja instance at https://developer.wunderlist.com/apps/new to get this
$ The client secret, also required for making requests to the wunderlist api
$ The url where clients are redirected after they authorized Vikunja to access their wunderlist stuff.
$ This needs to match the url you entered when registering your Vikunja instance at wunderlist.
$ This is usually the frontend url where the frontend then makes a request to /migration/wunderlist/migrate
$ with the code obtained from the wunderlist api.
$ Note that the vikunja frontend expects this to be /migrate/wunderlist