• Re: XTRN.CNF

    From Ragnarok@1:103/705 to Nightfox on Fri Jan 5 22:45:43 2024
    El 28/12/23 a las 18:49, Nightfox escribió:
    Re: XTRN.CNF
    By: Tim Whitson to All on Wed Dec 27 2023 08:12 pm

    TW> Is there a way to export or print this file in a way it's easy to read?

    If you upgrade to Synchronet 3.20, xtrn.cnf (along with all the .cnf files) will become .ini files, which are human-readable.

    http://wiki.synchro.net/install:dev http://wiki.synchro.net/history:newcfgfiles

    From a post by Digital Man a while ago:
    If you upgrade to v3.20a (the current master development code) either via source build or by downloading pre-built binaries, you'll need to run 'jsexec update' to upgrade your user base and configuration files to their new formats.
    See docs/newuserbase.txt and docs/newcfgfiles.txt for more details.


    I ran the upgrade at some point when I moved to version 3.20 (I usually
    update from git on a regular basis)
    So I already have the migrations to .ini from that time

    1) is it safe/necessary to run the upgrade script again? I understand
    that if the .ini already exist, they will not be recreated from the .cnf
    and overwrite the current ones, right?

    2) if I already have the .ini respectively the .cnf (for example I
    already have xtrn.ini), can I delete xtrn.cnf? I'm just asking as a way
    to clean unnecessary files.

    thank you
    ---
    ï¿­ Synchronet ï¿­ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Ragnarok on Fri Jan 5 19:17:44 2024
    Re: Re: XTRN.CNF
    By: Ragnarok to Nightfox on Fri Jan 05 2024 10:45 pm

    I ran the upgrade at some point when I moved to version 3.20 (I usually update from git on a regular basis)
    So I already have the migrations to .ini from that time

    1) is it safe/necessary to run the upgrade script again? I understand
    that if the .ini already exist, they will not be recreated from the .cnf
    and overwrite the current ones, right?

    You should run 'jsexec update.js' pretty much after every update/rebuild/upgrade, no matter what.

    2) if I already have the .ini respectively the .cnf (for example I
    already have xtrn.ini), can I delete xtrn.cnf?

    Yes, you should not need the .cnf files, but keeping a backup isn't a bad idea. --
    digital man (rob)

    This Is Spinal Tap quote #31:
    Viv Savage: Quite exciting, this computer magic!
    Norco, CA WX: 57.7øF, 34.0% humidity, 0 mph N wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)