-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test server running wsmc for use with voxel-clientmc #22
Comments
To look into: https://github.com/mhsjlw/minecraft-buildpack
|
Vanilla minecraft server (Spigot/Glowstone/Sponge/Forge can come later): https://github.com/jkutner/heroku-buildpack-minecraft |
Setup Heroku and Ngrok using instructions at https://github.com/jkutner/heroku-buildpack-minecraft - works! Available vanilla minecraft 1.8.3 server: 0.tcp.ngrok.io:12155 Now it only needs the wsmc proxy. Probably best to run it through Sponge, since that'll stress-test both Forge handshake support, and the Sponge plugin integration. To do:
|
The Heroku dynos spin down after a while - this resets the world, which is ok for a test server (build pack creator suggests backing up to and restoring from AWS). Spins back up again when visiting the Heroku web app site (my subdomain is warm taiga, appropriately enough), which in the sample build pack only shows you various information. Including the ngrok host and port, changed on each launch. So I'm thinking instead of hosting the demo voxel-clientmc web app on gh-pages, or the Sponge/Bukkit ngrok-forwarded HTTP server, it could be hosted on Heroku. Therefore visiting the site will start the backend mc server and wsmc proxy, hopefully in time for the web app to load and initialize client-side. |
Would be awesome to have a live server accessible with voxel-clientmc (e.g., running wsmc), to make a better public demonstration (where anyone could simply click a link to try out voxel-clientmc).
The text was updated successfully, but these errors were encountered: