Closed RidleyLarsen closed 8 years ago
That's an issue I still need to work out. For now, just ignore it (go to the correct URL and ignore the one it suggests) and change the config file to the host you are using. grind should use the host in your config file once it has been set.
On Fri, Jul 8, 2016 at 12:40 PM, Ridley Larsen notifications@github.com wrote:
The grind init command will only request a user's cookie from dorking.cs.dixie.edu - It doesn't check for a config file before relying on defaultHost.
Plus, after running grind init, your config file will be overwritten with host: defaultHost anyway. Perhaps it could be a two-step process? Enter your CodeGrinder server hostname --> Enter your cookie.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/russross/codegrinder/issues/1, or mute the thread https://github.com/notifications/unsubscribe/AAD_lMTd5HW1PTJ2hc06tEBwSzReFkWYks5qTpmFgaJpZM4JIShy .
Here's a potential solution: codechangers/codegrinder@3b7493212a64b347e1da81b6e533966ddef9e3f0
I changed this a while back. Now the host name is required when you run "grind init". There are no more hard-coded assumptions about hostnames.
The
grind init
command will only request a user's cookie from dorking.cs.dixie.edu - It doesn't check for a config file before relying ondefaultHost
.Plus, after running
grind init
, your config file will be overwritten withhost: defaultHost
anyway. Perhaps it could be a two-step process? Enter your CodeGrinder server hostname --> Enter your cookie.