• Node dir

    From deon@1:103/705 to Digital Man on Sunday, November 22, 2020 21:27:18
    Hey DM,

    How is the "first" main.cnf created?

    I know this may be breaking, but would you consider a patch to change the nodes directories to be created in a "nodes/" sub dir? (And I guess that initial main.cnf should be updated as well - hence my question.)

    Some folks may like it because its a little cleaner, but I'd like it because its easier to share it in a multi host scenario, if I dont want to share /opt/sbbs.

    ...ëîåï

    ... Honeymoon - the morning after the knot before.

    ---
    þ Synchronet þ Alterant | an SBBS in Docker on Pi!
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to deon on Sunday, November 22, 2020 13:21:51
    Re: Node dir
    By: deon to Digital Man on Sun Nov 22 2020 09:27 pm

    Hey DM,

    How is the "first" main.cnf created?

    Not sure I follow. A sysop should always start with the main.cnf from the source repo.

    I know this may be breaking, but would you consider a patch to change the nodes directories to be created in a "nodes/" sub dir? (And I guess that initial main.cnf should be updated as well - hence my question.)

    Some folks may like it because its a little cleaner, but I'd like it because its easier to share it in a multi host scenario, if I dont want to share /opt/sbbs.

    Those folks can change the node directories. A change was recently introduced to make sure that works.
    --
    digital man

    Synchronet/BBS Terminology Definition #88:
    XPDEV = Cross-platform Development
    Norco, CA WX: 75.9øF, 29.0% humidity, 6 mph NNE wind, 0.00 inches rain/24hrs --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From deon@1:103/705 to Digital Man on Monday, November 23, 2020 10:30:16
    Re: Node dir
    By: Digital Man to deon on Sun Nov 22 2020 01:21 pm

    Howdy,

    How is the "first" main.cnf created?
    Not sure I follow. A sysop should always start with the main.cnf from the source repo.

    Is there a way it can be "recreated" programmatically?

    I'm trying to build my docker container so that the "nodes" points to /opt/sbbs/nodes/xxx, not /opt/sbbs/nodesX/.

    Sure, I get after the image starts, I can personalise the configuration (that is then stored in the persistent store), so that future invocations of the container (with that config) points to /opt/sbbs/nodes/, but I'm trying to improve the first start for a new environment by reducing the number of steps that need to be done (that really should be done programmatically).

    I could add my customised main.cnf to the image (with the right path) - but then if you make any upstream changes to main.cnf, I'd have to remember to rebuild my customised one.

    I can work around it, but looking for a less manual path.

    ...ëîåï

    ... Free the indianapolis 500.

    ---
    þ Synchronet þ Alterant | an SBBS in Docker on Pi!
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to deon on Sunday, November 22, 2020 16:25:32
    Re: Node dir
    By: deon to Digital Man on Mon Nov 23 2020 10:30 am

    Re: Node dir
    By: Digital Man to deon on Sun Nov 22 2020 01:21 pm

    Howdy,

    How is the "first" main.cnf created?
    Not sure I follow. A sysop should always start with the main.cnf from the source repo.

    Is there a way it can be "recreated" programmatically?

    I'm trying to build my docker container so that the "nodes" points to /opt/sbbs/nodes/xxx, not /opt/sbbs/nodesX/.

    Sure, I get after the image starts, I can personalise the configuration (that is then stored in the persistent store), so that future invocations of the container (with that config) points to /opt/sbbs/nodes/, but I'm trying to improve the first start for a new environment by reducing the number of steps that need to be done (that really should be done programmatically).

    I could add my customised main.cnf to the image (with the right path) - but then if you make any upstream changes to main.cnf, I'd have to remember to rebuild my customised one.

    I can work around it, but looking for a less manual path.

    Take a look at exec/load/cnflib.js, That's how we programmatically (from JS anyway) modify .cnf files these days.
    --
    digital man

    Synchronet "Real Fact" #20:
    Michael Swindell was directly responsible for Synchronet's commercial success. Norco, CA WX: 68.2øF, 56.0% humidity, 7 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)