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.)because
Some folks may like it because its a little cleaner, but I'd like it
its easier to share it in a multi host scenario, if I dont want to share /opt/sbbs.
source repo.How is the "first" main.cnf created?Not sure I follow. A sysop should always start with the main.cnf from the
Re: Node dirof
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
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 59:22:08 |
Calls: | 6,653 |
Calls today: | 5 |
Files: | 12,200 |
Messages: | 5,331,279 |