TZUTC: -0800
MSGID: 4307.golded@1:103/705 2a4f524d
REPLY: 1:104/117 65e9c8c7
PID: Synchronet 3.20a-Linux master/632246a6b Mar 06 202 GCC 12.2.0
TID: SBBSecho 3.20-Linux master/632246a6b Mar 06 2024 23:50 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: CP437 2
NOTE: FSEditor.js v1.105
  Re: Re: Synchronet config change
  By: Vitaliy Aksyonov to Rob Swindell on Thu Mar 07 2024 06:55 am

 > Hello Rob.
 >
 > 06 Mar 24 12:05, you wrote to me:
 >
 >  RS> I'm attempting a reply using GoldEd+ here.
 >
 >  RS> One thing I noticed, the SBBS config points to the parent of the
 >  RS> Synchronet "control" directory rather than the ctrl directory itself
 >  RS> (which is normally represnted by the SBBSCTRL environment variable).
 >  RS> The control directory is not hard-coded to be "ctrl" anywhere, thought
 >  RS> that is the default/stock configuration that most sysops keep. I would
 >  RS> recommend that the GoldEd+ config file point to the path of the
 >  RS> Synchronet "control" directory and not its parent directory. Or read
 >  RS> this from the SBBSCRL env var.
 >
 > Currently you may use three different options for Synchronet AreaFile:
 >
 > 1) Path to Synchronet root. And then Golded would assume that config is is
 > ctrl directory.
 > 2) Path to Synchronet control directory.
 > 3) Path to msgs.ini itself.

Only methods 2 and 3 there would be valid. There's no real "Synchronet root".

 > And also GoldEd assumes that message bases located on the same level as
 > control directory in "data/subs" directory.

That would be incorrect. Each message base can actually be located anywhere
(that's what 'data_dir' is used for - but it's it's blank, then data/subs can
be assumed, but the location of the 'data' directory is also configurable in
the [dir] section of main.ini).

 > I didn't invent that logic. Just added parsing ini in addition to cnf file.
 >
 > I'm happy to change the way it configured. But I'm not an expert in
 > Synchronet design. Could you please describe how it may be configured?

SBBSCTRL (env var or other method of discovery) points to Synchronet "control"
directory (which could be named/located anywhere), where you can find main.ini
which in turn defines the relative path (from the "control" directory) to the
"data" directory.

Then parsing msgs.ini, each message area (sub) can have its own "data_dir"
defined (where to find the message base files themselves) - if the data_dir
isn't defined, then the "subs" sub-directory of the configured "data"
directory is where the message base files are expected to be found.

 > Maybe
 > would be better to parse main config file first and pull necessary
 > directories from there?

Yes, main.ini would need to be parsed as well (first).

Synchronet is open source and the most relevant source file, for reference,
would be: https://gitlab.synchro.net/main/sbbs/-/blob/master/src
sbbs3/scfglib1.c
-- 
                                            digital man (rob)

This Is Spinal Tap quote #10:
Dozens of people spontaneously combust each year... just not widely reported.
Norco, CA WX: 56.9øF, 70.0% humidity, 6 mph W wind, 0.57 inches rain/24hrs
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 15/0 18/200 90/1 103/705 105/81 106/201 124/5016 128/260
SEEN-BY: 129/305 135/225 153/757 7715 154/10 30 203/0 218/700 221/0
SEEN-BY: 226/30 227/114 229/110 112 113 206 307 317 400 426 428 470
SEEN-BY: 229/664 700 240/1120 5832 266/512 280/464 5003 5555 282/1038
SEEN-BY: 291/111 292/854 8125 301/1 310/31 320/219 322/757 341/66
SEEN-BY: 341/234 342/200 396/45 423/120 460/16 58 256 1124 5858 467/888
SEEN-BY: 633/280 712/848 770/1 5020/400 1042 5054/30
PATH: 103/705 280/464 460/58 229/426