My other idea is to just treat it as a “stand alone” application, running on it’s own server and hitting the laravel application as the backend API. This is less then ideal, will require another URL, and ripple all kinds of issues during staging and deployment. Also I’d have to figure out how to handle auth.
Golly solution 1 (add destination variables) sure would be the easiest solution (from my perspective, I’m not a maintainer of quasar though )
My hacks work fairly well. Maybe there is a way to make a new build target? (like instead of “quasar dev met”, I could make “quasar linux-dev met” and “linux-build”). This would be an attempt to keep framework updates from clobbering my build modifications.