Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: UPDATE 1.8 to 2.8  (Read 113 times)

0 Members and 1 Guest are viewing this topic.

Manu

  • Anope User
  • Offline Offline
  • Posts: 1
UPDATE 1.8 to 2.8
« on: October 09, 2020, 11:47:20 AM »

Hello, i need help. Now i want update Anope 1.8 to Anope 2.0, but update data not work.

This is old services config encript

#     Plain Text                -  enc_none
#     Previous (broken) MD5     -  enc_old
#     MD5                       -  enc_md5
#     SHA1                      -  enc_sha1
#



EncModule "enc_none"



This is new config encript for save all database

  * [REQUIRED] Database configuration.
 *
 * This section is used to configure databases used by Anope.
 * You should at least load one database method, otherwise any data you
 * have will not be stored!
 */

/*
 * [DEPRECATED] db_old
 *
 * This is the old binary database format from late Anope 1.7.x, Anope 1.8.x, and
 * early Anope 1.9.x. This module only loads these databases, and will NOT save them.
 * You should only use this to upgrade old databases to a newer database format by loading
 * other database modules in addition to this one, which will be used when saving databases.
 */
module
{
   name = "db_old"

   /*
    * This is the encryption type used by the databases. This must be set correctly or
    * your passwords will not work. Valid options are: md5, oldmd5, sha1, and plain.
    * You must also be sure to load the correct encryption module below in the Encryption
    * Modules section so that your passwords work.
    */
   hash = "plain"
}

/*
 * [RECOMMENDED] db_flatfile
 *
 * This is the default flatfile database format.
 */
module
{
   name = "db_flatfile"

   /*
    * The database name db_flatfile should use
    */
   database = "anope.db"

   /*
    * Sets the number of days backups of databases are kept. If you don't give it,
    * or if you set it to 0, Services won't backup the databases.
    *
    * NOTE: Services must run 24 hours a day for this feature to work.
    *
    * This directive is optional, but recommended.
    */
   keepbackups = 3

   /*
    * Allows Services to continue file write operations (i.e. database saving)
    * even if the original file cannot be backed up. Enabling this option may
    * allow Services to continue operation under conditions where it might
    * otherwise fail, such as a nearly-full disk.
    *
    * NOTE: Enabling this option can cause irrecoverable data loss under some
    * conditions, so make CERTAIN you know what you're doing when you enable it!
    *
    * This directive is optional, and you are discouraged against enabling it.
    */
   #nobackupokay = yes

   /*
    * If enabled, services will fork a child process to save databases.
    *
    * This is only useful with very large databases, with hundreds
    * of thousands of objects, that have a noticeable delay from
    * writing databases.
    *
    * If your database is large enough cause a noticeable delay when
    * saving you should consider a more powerful alternative such
    * as db_sql or db_redis, which incrementally update their
    * databases asynchronously in real time.
    */
   fork = yes
}

/*
 * db_sql and db_sql_live
 *
 * db_sql module allows saving and loading databases using one of the SQL engines.
 * This module loads the databases once on startup, then incrementally updates
 * objects in the database as they are changed within Anope in real time. Changes
 * to the SQL tables not done by Anope will have no effect and will be overwritten.
 *
 * db_sql_live module allows saving and loading databases using one of the SQL engines.
 * This module reads and writes to SQL in real time. Changes to the SQL tables
 * will be immediately reflected into Anope. This module should not be loaded
 * in conjunction with db_sql.
 *
 */
#module
{
   name = "db_sql"
   #name = "db_sql_live"

   /*
    * The SQL service db_sql(_live) should use, these are configured in modules.conf.
    * For MySQL, this should probably be mysql/main.
    */
   engine = "sqlite/main"

   /*
    * An optional prefix to prepended to the name of each created table.
    * Do not use the same prefix for other programs.
    */
   #prefix = "anope_db_"

   /* Whether or not to import data from another database module in to SQL on startup.
    * If you enable this, be sure that the database services is configured to use is
    * empty and that another database module to import from is loaded before db_sql.
    * After you enable this and do a database import you should disable it for
    * subsequent restarts.
    *
    * Note that you can not import databases using db_sql_live. If you want to import
    * databases and use db_sql_live you should import them using db_sql, then shut down
    * and start services with db_sql_live.
    */
   import = false
}

/*
 * db_redis.
 *
 * This module allows using Redis (https://redis.io/) as a database backend.
 * This module requires that m_redis is loaded and configured properly.
 *
 * Redis 2.8 supports keyspace notifications which allows Redis to push notifications
 * to Anope about outside modifications to the database. This module supports this and
 * will internally reflect any changes made to the database immediately once notified.
 * See docs/REDIS for more information regarding this.
 */
#module
{
   name = "db_redis"

   /*
    * Redis database to use. This must be configured with m_redis.
    */
   engine = "redis/main"
}

/*
 * [RECOMMENDED] Encryption modules.
 *
 * The encryption modules are used when dealing with passwords. This determines how
 * the passwords are stored in the databases, and does not add any security as
 * far as transmitting passwords over the network goes.
 *
 * Without any encryption modules loaded users will not be able to authenticate unless
 * there is another module loaded that provides authentication checking, such as
 * m_ldap_authentication or m_sql_authentication.
 *
 * With enc_none, passwords will be stored in plain text, allowing for passwords
 * to be recovered later but it isn't secure and therefore is not recommended.
 *
 * The other encryption modules use one-way encryption, so the passwords can not
 * be recovered later if those are used.
 *
 * The first encryption module loaded is the primary encryption module. All new passwords are
 * encrypted by this module. Old passwords stored in another encryption method are
 * automatically re-encrypted by the primary encryption module on next identify.
 *
 * enc_md5, enc_sha1, and enc_old are deprecated, and are provided for users
 * to upgrade to a newer encryption module. Do not use them as the primary
 * encryption module. They will be removed in a future release.
 *
 */

#module { name = "enc_bcrypt" }
module { name = "enc_sha256" }

/*
 * When using enc_none, passwords will be stored without encryption. This isn't secure
 * therefore it is not recommended.
 */
#module { name = "enc_none" }

/* Deprecated encryption modules */
#module { name = "enc_md5" }
#module { name = "enc_sha1" }

/*
 * enc_old is Anope's previous (broken) MD5 implementation used from 1.4.x to 1.7.16.
 * If your databases were made using that module, load it here to allow conversion to the primary
 * encryption method.
 */
#module { name = "enc_old" }

Any help is appreciated.

Thanks

Logged
Pages: [1]   Go Up