Allow custom 'publicPath' config

[chrismayer]

This introduces an ENV VAR WGU_PUBLIC_PATH in order to change the publicPath Vue CLI configuration, which is used to create the production build, without modifying the Wegue code base.

Also changes the default for publicPath from '/' to './', since the relative notation './' works for most cases, e.g. if the app is deployed at the root of a domain and for a deployment under a certain path. For any other special case use the WGU_PUBLIC_PATH as stated above.

See https://cli.vuejs.org/config/#publicpath

[JakobMiksch]

I am not sure how to test that.
I ran WGU_PUBLIC_PATH=foo npm run build , but it is not clear to me on which URL this is supposed to run. I ran a webserver both inside the build directory and one level higher. In both cases I could not open the webmap.

[sronveaux]

Hi @JakobMiksch,

The idea to test this here is to define the ENV_VAR inside a file called .env.production as explained in the Vue-CLI official documentation.

By defining it in this file, you should be able to test this PR.

Regards,
Sébastien

[sronveaux]

Hi @chrismayer,

I made some tests here, defining the new environment variable and NOT defining it and managed to run a WebServer to make a complete app to run thoroughly in all cases. So yes, I think this works as expected.

However, for this new environment variable to be fully understandable, shouldn't it be documented somewhere ? This is not easy as there are no documentation section concerning potential environment variables and all what is related to configuration is linked to the app-conf.json files, so I don't really see where it could fit nicely for now... perhaps, like what is done for application contexts, a little note inside the workshop in the build for production part could do the trick ?

[chrismayer]

Thanks for your feedback and testings @sronveaux and @JakobMiksch. I totally agree that a little documentation of the ENV VAR would be really helpful. So I added it to the README in the section Production Build and to the workshop in the section Build for production as suggested by @sronveaux. If necessary we could extend and improve those documentations.

Thnaks again. I am going to merge now...