Actually I think I mistyped about the e is undefined error, the api logs just said permission denied on that one. I can still open the issue on that one if it appears again, but I'm guessing it was probably caused by the permissions.
Works fine after docker execing into the container and chowning the files folder with chown -R vikunja:vikunja files, so somehow my permissions got out of whack in my api container. Most likely a side effect of some other kind of troubleshooting I did at some point earlier.
When uploading attachments, I get "e is undefined", both in the frontend and api logs.
Yup I copy pasted the proxy docker-compose because it ended up being exactly the same minus the proxy section which I just forgot to remove. Oops! Gimme a few minutes I'll get that cleaned up.
I'll look into it as soon as I have time. Thanks for being the rubber ducky for my Caddy config and fixing the frontend bug we found! I'll go ahead and close this since its resolved.
Deleted my earlier message, forgot to run docker-compose pull first...
It works! I'm going to see about a pull request for the docs to append a Caddy configuration to the Full Docker example, in case anyone sees this before then, my Caddy configuration ended up being even simpler, didn't actually need the handle directives at all.
tasks.{$MY_DOMAIN} {
reverse_proxy /api/* vikunja-api:3456
reverse_proxy vikunja-frontend:80
}
Ah OK, the whole "not loading assets" thing gave me a better hint of what could actually be happening. If I change the handle directives in Caddy to the following:
tasks.{$MY_DOMAIN} {
handle /api/* {
reverse_proxy vikunja-api:3456
}
handle /* {
reverse_proxy vikunja-frontend:80
}
}
Basically the /css wasn't getting handled by anything, just /, changing the match string to /* allowed that handle tag to match anything (other than /api/*, which gets grabbed by the first handle directive). When I change it to that I get to a login screen. However, when I try to register, I just get a blank red box, which looks like there should be an error but no text. The javascript console then just says "uncaught exception: undefined" I'll investigate more on my end in the meantime, but do you have any potential clues?