In the future, if you want to set variables to be pulled through the code base during configuration, you can add the define key in configuration and reference env. So, this is future looking by…
OK. I think I landed on a full, final approach to supporting VIKUNJA_FRONTEND_SUBPATH
and having it properly set throughout the code base.
There are two ways of setting the base path…
I've updated the documentation PR to not be WIP. I'm working on the loading of the environment file and setting the base via that method.
Can you make it work?
I think I can. Now the question is, should that be included in the scope of this PR?
I think, if it is possible, that I'd like to put the env expansion work in…
Can you make it work?
I think I can. Now the question is, should that be included in the scope of this PR?
Awesome! Can you remove the
pnpm workbox copyLibraries dist/
line and replacepnpm vite build
withpnpm run build
. Because the [build task](https://kolaente.dev/vikunja/frontend/src/branch/…
Thanks a lot! :)
The only thing I'm missing now is a line in that newly merged .env.local.example filling out…
Patch updated and pushed. The PR's message has been updated.
The base path is now set from VIKUNJA_FRONTEND_SUBPATH
. This correctly sets all paths. This is also future facing as when you…