3 ms·
Hey, I feel really sorry for you that you did not have a good or accurate experience of this. It must seem like it does not respect your wishes, or would not if
by graderjs 6y ago
Hey, I feel really sorry for you that you did not have a good or accurate experience of this. It must seem like it does not respect your wishes, or would not if your tried it more.
Okay so...
The config is actually located in hidden file, here: https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a8383c0683501895603/args.js#L10 https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a838...
const pref_file = path.resolve(os.homedir(), '.22120.config.json');
And the port is fully configurable here https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a8383c0683501895603/args.js#L5 https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a838...
const server_port = process.env.PORT || process.argv[2] || 22120;
I don't agree with you about the name. And I get if you're saying you feel the name should not be linked to a port number, but i also don't agree.
I guess i can explain my thinking, but I'm not sure if they will help you understand or like it. Basically I like the name and I did consider changing it a few times but it just stuck for a number of reasons. And I can't remember exactly now but the port number might have come after the name. I think it's a good idea and cool if you have the server running on the same board that the name is but at the same time I know you might have something else running on that port so that's why I made it configurable. I guess she might also want to run more than one copy... But I'm pretty sure that we can't open two chrome windows with different debugging ports using the same user data directory.
Anyway, that might be more info than you want or care for, and it might not help, but hopefully you have a clearer picture at least. I get if you still don't like it, but i just feel sorry for you that you didn't have a good experience of this. I did not design it to annoy you.