Using remote includes
Using remote includes
Im wondering what is the minimal unrealircd.conf I need for the server. Before I can use remote includes for the rest? Is there any information for this or is it down to the good old try and error
Did some testing on test server I have. From what I can see I need the following
include "http://path.to/common.conf";
The rest of the config file can if you wish be included.
Ok this is not the best way to share a config file since it will most certainly be a bad idea.
I think that and correct me if im wrong that a better idea would be to have
loadmodule "/path/to/commands.so";
include "http://path.to/common.conf";
me {
}
admin {
}
Is there anything else that is serverbased that needs to be for the singel server and cannot be common among the servers.
include "http://path.to/common.conf";
The rest of the config file can if you wish be included.
Ok this is not the best way to share a config file since it will most certainly be a bad idea.
I think that and correct me if im wrong that a better idea would be to have
loadmodule "/path/to/commands.so";
include "http://path.to/common.conf";
me {
}
admin {
}
Is there anything else that is serverbased that needs to be for the singel server and cannot be common among the servers.
-
codemastr
- Former UnrealIRCd head coder
- Posts: 811
- Joined: Sat Mar 06, 2004 8:47 pm
- Location: United States
- Contact:
First thing, make sure you at least password protect that common file. Some of the "common" things can cause security problems (oper passwords, cloak keys, etc.) Second, I'd also recommend using encrypted passwords wherever possible so if someone does manage to steal the common config file, they can't get passwords. Also, consider (if you have the ability) to use https rather than http.
Other than the me {} and admin {} I guess it really depends. I mean, do you want all servers to have the same allow {} blocks? Same link {} blocks, etc.?
Anyway, I'd say the drpass {} should probably be unique. Having every server use the same /restart and /die pass sounds like a bad idea. set::dns is probably going to be unique as well (unless all servers use 127.0.0.1). That's all I can think of at the moment...
Other than the me {} and admin {} I guess it really depends. I mean, do you want all servers to have the same allow {} blocks? Same link {} blocks, etc.?
Anyway, I'd say the drpass {} should probably be unique. Having every server use the same /restart and /die pass sounds like a bad idea. set::dns is probably going to be unique as well (unless all servers use 127.0.0.1). That's all I can think of at the moment...
-- codemastr
Yes I started thinking of that too.
This is just a starting project to make it easier to maintain for me, right now I run my two servers on the same network and both comps are mine so its not that a big problem.
But I willmake sure I cahnge things along the way you said they are VERY GOOD points I think
This is just a starting project to make it easier to maintain for me, right now I run my two servers on the same network and both comps are mine so its not that a big problem.
But I willmake sure I cahnge things along the way you said they are VERY GOOD points I think
Password Auth
Code: Select all
include "http://username:[email protected]/file.conf";