Something went wrong. Try again.
[READ-ONLY] Mirror of https://github.com/VibeDevelopers/atheme. Modified fork of atheme IRC Services www.vibetalk.net
Something went wrong. Try again.
123456789101112131415161718192021222324252627282930313233343536373839Read this first---------------
As of version 2.2, Services no longer supports SQL databases. To useServices 2.2 or newer, you will need to switch to the flatfile backend.
The information on how to use the SQL backend has been removed asversions prior to 2.2 are extremely unsupported by Atheme and itis highly recommended to upgrade. The information on how to switchto a SQL backend (and vice-versa) is still left in this file in caseyou are upgrading from a old version to a newer version.
If you would like web integration with your Atheme Services setup,it is highly recommended to use the XML-RPC interface which alsohappens to be "live".
Switching to a SQL backend--------------------------
Switching to a SQL backend is relatively painless; just make surethat your database {} block is configured properly. Hint: /msg operserv rehash
Once you have a properly configured database{} block, you can simplyload the replacement backend via: /msg operserv modload ../backend/<replacement backend>
After the backend is loaded, you can export your data by usingOperServ's UPDATE command.
Once you have loaded the replacement backend, you are now onSQL. You will probably want to switch your backend module out inthe configuration file, as your flatfile database will no longerbe updated. You may want to restart Services to ensure that thetransition was successful after updating the config file.
Switching from a SQL backend to flatfile can be done similarly.