search

bjorngranvik / reudd

REgarding User Driven Development - a user centric "data in/report out" web site using Neo4j.
Apache License 2.0
1 stars 0 forks source link

How to setup ip to run as a server accessed from another computer #7

Closed bjorngranvik closed 10 years ago

bjorngranvik commented 10 years ago

Using Reudd will land you in localhost as ip number in the current setup. Using an web browser from another will not work. How to specify this?

matsjonas commented 10 years ago

I am unable to reproduce this on my computers. Using another computer I am able to browse to the IP of my dev machine and use reudd from there.

You could try to change the "environments > development > grails.serverURL" variable to something like grails.serverURL = "http://192.168.1.1:8080/${appName}" and then relaunch the app.

But don't commit your changes since I bet that we will all have different IPs on our dev machines.

sarmbruster commented 10 years ago

you can also run grails -Dserver.host=<myhostname>, see http://www.grails.org/doc/latest/ref/Command%20Line/run-app.html

bjorngranvik commented 10 years ago

I tried the -Dserver command and also set the port to something different. Still the same problem on submitting a new node. It directed to old port and localhost.

bjorngranvik commented 10 years ago

Rewriting the serverUrl as Jonas suggest above seem to work. But isn't there a better way than to hard code an ip?

matsjonas commented 10 years ago

I believe to have solved this by updating the Config.groovy file to the format used on new Grails 2.2.4 applications (5a0a077). I think it was caused by different usages of the grails.serverURL between Grails version.

@bjorngranvik: Can you verify?

bjorngranvik commented 10 years ago

Seems to work fine now.

/Björn

Written on a mobile. Please excuse brevity and errrs

30 aug 2013 kl. 21:02 skrev Jonas Andersson notifications@github.com:

I believe to have solved this by updating the Config.groovy file to the format used on new Grails 2.2.4 applications (5a0a077). I think it was caused by different usages of the grails.serverURL between Grails version.

@bjorngranvik: Can you verify?

— Reply to this email directly or view it on GitHub.