-
Notifications
You must be signed in to change notification settings - Fork 5
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
Mode for no config file/all defaults for testing #47
Comments
I guess |
How about 7070? Makes me think about how for similar purposes HTTP daemons will use port 8080. I've been personally using port 7070 for testing.
|
Contrary to 8080 with http, 7070 has another protocol than gopher assigned to it, so it makes for a bad default. Maybe the solution is to allow specifying a subset of the configuration via command line flags. |
I don't think it'd be bad to be some preconfigured port number for testing and an option to set a flag too! |
Feature request.
It would be great if I could arbitrarily launch
spacecookie
when I build random gopherholes as a test and I just want to see what the product looks like after I build it, without having to create a config file to test locally.I want to, for testing purposes, be able to use
spacecookie
without specifying a config file.The text was updated successfully, but these errors were encountered: