EPONA WIN32 INSTALLATION INSTRUCTIONS ===================================== Table of contents ----------------- 1. Installing Epona 2. Upgrading Epona 3. Setting up the IRCd 4. Starting Epona 5. Win32 Limitations You should also read the README and FAQ files! 1. Installing Epona ------------------- IMPORTANT NOTE: it is not recommended to use (and therefore install) Epona as the superuser. Use an unprivilegied user instead -- the one you're using for the ircd or a dedicated one will be good enough. The very first thing you need to do is to get the Epona setup (epona-1.x.x.exe -- if not already done). You may found it at the following places: PegSoft (France) (always updated) ftp://ftp.pegsoft.net/epona/ ViaIRC (Brazil) (updated every day) ftp://ftp.viairc.com/epona/ LeCentre (France) (updated once a week) ftp://ftp.lecentre.net/mirror/ftp.pegsoft.net/epona/ AtomicFault (USA) (updated every day) ftp://ftp.atomicfault.com/mirror/epona/ Brazil Marketing Services (USA) (updated every day) ftp://ftp.brmarket.net/epona/ Now run the setup file and follow the instructions. You MUST install it in C:\Epona, or it won't work. Now go into the data directory (by default, ~/services). Copy the example.conf file to services.conf, and open the latter with your favourite text editor. It contains all the configuration directives Epona will use at startup. Read the instructions contained in the file carefully. Using the default values is NOT a good idea, and will most likely not work! If you need help, you should subscribe to the Epona mailing list and mail there to get help from other users. See the README file for more information. DON'T ask for help directly to me, as there are 99.99% chances you won't get an answer. 2. Upgrading Epona ------------------ To upgrade Epona, just follow the installation instructions described in section 1. There are however a few specific guidelines: * IMPORTANT: Back up your old databases! * If you are upgrading to a new major release, ALWAYS restart a fresh configuration file from example.conf. Version 1.3.0 merges the AKILL database with the OperServ database. This is an automatic process and you have nothing to do (just ensure that AutoKillDB in services.conf is set correctly and maybe remove the AKILL database after the conversion). 3. Setting up the IRCd ---------------------- Services are acting as an IRC server with pseudo-clients on it. To link them to your network, you'll need to add some lines in the ircd.conf of their hub server (as stated in the RemoteServer configuration directive). For samples below we'll take Services.LocalHost.Net as the name of the Services (as stated in the ServerName configuration directive). First, the C/N lines, that allow Services to link. They also need a Y:line to work correctly. Y:27:180:0:0:4000000 C:127.0.0.1:mypass:Services.LocalHost.Net::30 N:127.0.0.1:mypass:Services.LocalHost.Net::30 mypass is the same password you mentionned in the RemoteServer configuration directive. 127.0.0.1 is the IP from which Services connect from (linking in localhost is the most efficient way to run Services). Then, you have to set-up an U:line, that will allow Services to change channel modes, topics, and much more without being opped in the channel. U:Services.LocalHost.Net:*:* NOTE: if you have more than one server in your network, this line MUST be added on ALL servers, or things won't work. Finally, you'll need to add an H:line, to make the OperServ JUPE command work correctly. H:*::Services.LocalHost.Net Don't forget to /rehash to apply changes. 4. Starting Epona ----------------- Run services.exe to launch Epona. If there are syntax errors in the configuration file they will be displayed on the screen. Correct them until there are no errors anymore. A successful startup won't generate any message. Give to Services at least one minute to link to your network, as certain IRCds on some OSes may be really slow for the link process. If nothing happens then, it is probably a configuration problem. Try to launch Epona with services.exe -debug -nofork to see any errors that it encounters, and try to correct them. If you need help to resolve errors, feel free to subscribe to the Epona mailing list and ask there. See the README file for details. 5. Win32 Limitations -------------------- * The proxy detector currently doesn't work on Win32, so don't ask. * Other doc files were not specifically updated for Win32, so you may have problems to understand them completely. 6. Credits ---------- * Epona for Win32 is provided courtesy of Maxou . Complaints about issues specific to the Win32 version should be sent directly to him.