For use in restricted/disconnected environments, we need to document how to *Set up a workspace if it needs access to an asset registry like Maven does*.

From rhopp@redhat.com:

• As for "starting" our default devfiles from devfile registry - They should work out of the box. Only issue is that the devfiles are referencing project from github, which is obviously not available in airgap. May have issue associated with it -> could be mentioned in known issues in docs. This issue does not exist yet AFAIK (need to check)

• As for using any workspace with some project - users need to configure they build tools to point to their internal registries etc. (for example, when using maven - they need to configure settings.xml to download artifacts from their internal maven repository) – I would say, "normal stuff" for any development in restricted environment... even if they were previously developing on their own machines inside the restricted network, they would have this already configured in their projects

• As for creation of new devfiles - users just need to make sure, that all the (docker) images they are using in the devfile are in their internal image registry. – should be mentioned in docs imo

• Not sure how much we will support usage of custom plugins, as that's where the situation will be more complicated - and we even didn't test that - we just tried the default plugins we are bundling in CRW's plugin registry – I have no idea, if that's something we want/need to document