Basically every time you export a webshare 2 go project, it bundles the project data with chromium portable and all of the html partials and whatnot to run the webshare 2 go platform. It also includes the interface bits for the webshare cloud platform, but not all the back-end bits that you actually need to run a server version of webshare cloud.
Anyways, you need to use either something like XAMPP with an apache host, or even the "Web Server for Chrome" extension. Point the root directory at the folder in which your webshare 2 go project is stored. Then you need to ensure that your port forwarding/static IP/Dynamic DNS settings are correct to allow internet users to access the web app. If you've set up a SCENE 5.5 era Webshare server then this will be no stranger to you.
So now you have a webshare 2 go instance that can be accessed over the internet.
You still don't have logins, or the extra cloud functionalities, but this is acceptable for public project access and marketing efforts.
It isn't too hard to add login functionalities if you modify one of the html partials and can handle a little php/sql. The easiest approach is to run one instance of webshare 2 go for each desired user, and segregate the data in that method. There are better ways to accomplish this, but if you don't want to dig into the code too much, this is the easiest.
When you need to add projects to the webshare 2 go server data files, drop the data folder of the generated project (its in the ws2go data folder) into the data folder of the project that is being used by the server, and append the projects.json to include the new folder name so that it will show up on the interface when accessed.
If you need a more thorough step by step walk through, you can call me at 803-528-0649.
You can my version at:http://webshare.bcengineeringanddesign.com/