If you'd like to run your very own weinre server on the big ol' internets, this project is for you.
You'll need some basic familiarity with heroku.
Here are the basic instructions:
$ git clone git://github.com/pmuellr/weinre-heroku.git
Cloning into 'weinre-heroku'...
remote: Counting objects: 11, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 11 (delta 0), reused 11 (delta 0)
Receiving objects: 100% (11/11), done.
$ cd weinre-heroku
$ heroku create
Creating aaa-bbb-666... done, stack is cedar
http://aaa-bbb-666.herokuapp.com/ | [email protected]:aaa-bbb-666.git
Git remote heroku added
$ git push heroku master
Counting objects: 11, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (10/10), done.
Writing objects: 100% (11/11), 1.23 KiB, done.
Total 11 (delta 0), reused 11 (delta 0)
-----> Heroku receiving push
-----> Node.js app detected
-----> Resolving engine versions
Using Node.js version: 0.8.14
Using npm version: 1.1.65
-----> Fetching Node.js binaries
-----> Vendoring node into slug
-----> Installing dependencies with npm
... npm junk elided ...
Dependencies installed
-----> Building runtime environment
-----> Discovering process types
Procfile declares types -> web
-----> Compiled slug size: 8.6MB
-----> Launching... done, v4
http://aaa-bbb-666.herokuapp.com deployed to Heroku
To [email protected]:aaa-bbb-666.git
* [new branch] master -> master
$ heroku ps:scale web=1
Scaling web processes... done, now running 1
$ heroku ps
=== web: `node node_modules/.bin/weinre --httpPort $PORT --boundHost -all- --verbose`
web.1: up 2012/11/28 11:52:45 (~ 10s ago)
$ heroku open
Opening aaa-bbb-666... done
At this point, a browser has opened to your instance of weinre on the big ol' internets.
Enjoy!
It's even easier to run weinre on Cloud Foundry than it is on Heroku!
Assumes you have an account on a Cloud Foundry-based PaaS, and have the
cf tool installed.
If you're not currently using Cloud Foundry, you can try out IBM's BlueMix for free.
Here are the basic instructions:
- note that you should substitute your own desired hostname in the
-noption of thecf push weinreinvocation below.
$ git clone git://github.com/pmuellr/weinre-heroku.git
Cloning into 'weinre-heroku'...
remote: Counting objects: 11, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 11 (delta 0), reused 11 (delta 0)
Receiving objects: 100% (11/11), done.
$ cd weinre-heroku
$ cf push weinre -n some-name-here
Creating app weinre in org [your-id-here] / space dev as [your-id-here]...
OK
Creating route some-name-here.ng.bluemix.net...
OK
Binding some-name-here.ng.bluemix.net to weinre...
OK
Uploading weinre...
Uploading from: ~/Projects/bluemix/weinre-heroku
27.2K, 26 files
OK
Starting app weinre in org [your-id-here] / space dev as [your-id-here]...
OK
[staging messages elided]
1 of 1 instances running
App started
Showing health and status for app weinre in org [your-id-here] / space dev as [your-id-here]...
OK
requested state: started
instances: 1/1
usage: 1G x 1 instances
urls: some-name-here.ng.bluemix.net
state since cpu memory disk
#0 running 2014-03-14 05:44:56 PM 0.0% 30.7M of 1G 42.7M of 1G
At this point, you can open your browser on your new site at http://some-name-here.ng.bluemix.net
running on the big ol' internets.
Enjoy!