You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Platform project contains a pretty long list of steps to go through to install and test the XTC Platform. The Platform project ported to use the XTC Plugin makes this list significantly shorter, for example, by including the entire frontend stack the project needs as part of the Gradle build.
A large adoption threshold for the XDK platform is that it requires manual setup, which also contaminates system wide machine settings, and it is doubtful that a user would go through all these steps, and just at point 2 "sudo pfctl...", rest assure that there will be a significant number of nope-opts for any half curious XDK adopter to be.
If I recall it correctly, and this may have changed, the XDK platform also runs with special DNS settings for xqiz.it domain, to "fake" local host forwarding. Modifying DNS settings so that an app should run, is probably the ultimate system wide machine setting, even if it just affects the XDK domain. The wanted semantics should be replaceable with a trivial synthetic network configuration in Docker. It actually seems like a scenario where pretty much the only proper way to do it is through containerisation.
I'll state with some confidence that pretty much everyone who wants to evaluate the XTC platform would clone the repo, take a look at the README.md and the installation steps, and immediately start looking for the Dockerfile instead.
The text was updated successfully, but these errors were encountered:
The Platform project contains a pretty long list of steps to go through to install and test the XTC Platform. The Platform project ported to use the XTC Plugin makes this list significantly shorter, for example, by including the entire frontend stack the project needs as part of the Gradle build.
A large adoption threshold for the XDK platform is that it requires manual setup, which also contaminates system wide machine settings, and it is doubtful that a user would go through all these steps, and just at point 2 "sudo pfctl...", rest assure that there will be a significant number of nope-opts for any half curious XDK adopter to be.
If I recall it correctly, and this may have changed, the XDK platform also runs with special DNS settings for xqiz.it domain, to "fake" local host forwarding. Modifying DNS settings so that an app should run, is probably the ultimate system wide machine setting, even if it just affects the XDK domain. The wanted semantics should be replaceable with a trivial synthetic network configuration in Docker. It actually seems like a scenario where pretty much the only proper way to do it is through containerisation.
I'll state with some confidence that pretty much everyone who wants to evaluate the XTC platform would clone the repo, take a look at the README.md and the installation steps, and immediately start looking for the Dockerfile instead.
The text was updated successfully, but these errors were encountered: