K
Hi! (Vikunja dev here)
As @girish correctly pointed out, you don't need to enable openid to use the api. In fact, when you're using the Vikunja Frontend or Desktop app it already uses the api. The login endpoint is your way to go to get the api token.
I hope to build "classic" api tokens in the future you may know from other websites (like github) where you can create a long-lived token in the user settings and use it without a login.
That's actually the default setting for new users on their first day. I've increased the limit.
Hi!
As others have already said, it's a good idea to bring these discussions in Vikunja's forum. For a quick glance at what's coming, there are the roadmaps for the frontend and api.
@timconsidine No worries about the name.
My process in deciding the name was pretty much "llamas are nice animals, can I find something fancy around llamas that justifies buying an .io domain?" and the rest was searching around a bit and finding out that Vikunja's are a relative to the llama who live in south-america. The more common name for them is actually "Vicuña", something I didn't know at the time.
No special meaning there, a lot more random. Looks like it definitely catches the attention of people.
@scooke It's always amazing to see how other people use Vikunja. Glad it is working so well for you!
@scooke That sounds a lot like a bug - if it happens again, could you ping me so that I can try to reproduce it?
0.14.0 is a pretty old version. The frontend and the api are only guaranteed to work if they are the same version - current latest cloudron is 0.17.0, so you should use the frontend in that version as well.
@scooke That redis error is a problem in the caching layer provided by the orm I'm using for Vikunja. A few more details here.
The only solution right now is to disable the cache. If you're not running a very large installation, you won't notice the difference. I found that using redis can even slow down the overall speed because of the network overhead it has.
There should be logs from Vikunja somewhere too, the logs you posted are only the ones from the cloudron runtime if I understood that correctly. Maybe @girish can help with that?
Hey there, creator of Vikunja here.
It's really awesome to see people using Vikunja 
I'm not very familiar with cloudron so this is probably a noob question, but is there a special reason you're creating seperate docker images instead of using the official ones? This feels a bit like doubled effort.
Maybe we could even officially support cloudron with releases automatically published through our ci.
Also, please don't hesitate to ping me if you have any questions about Vikunja, either here or in Vikunja's Forum or through other ways.
