Support for Non-localhost Usage about oscal-editor-deployment HOT 3 CLOSED

Thanks for this report! I think this stems from the way the Viewer application is built. We specify the URL of the REST service as an environment variable during the build process; because the environment state is converted to a static JavaScript object during the build, we can't (currently) modify that value during runtime.

As a first step to fix this (within this bundled container image), we can set the configuration value to use a relative URL /oscal/v1 rather than including the host. This should work fine for the all-in-one container image.

In the longer term, we'll want to look into a means to actually configure the viewer application at runtime to support various backends (so that it doesn't have to be rebuilt for every backend). Then we'll want to find a way to make it easier to set that value when running the container.

from oscal-editor-deployment.

With #49 having been merged, the latest image should now work in an environment where the container is running on one machine and being accessed from another. @kkretsch before we close this, does the change that we've made properly support your use case?

from oscal-editor-deployment.

Yes, I just updated the image and can now access the oscal files of the installation. Great idea to just use a relative path.

from oscal-editor-deployment.