First thing - the exec js files in ./exec/ are they by definition "static" - they shouldnt be modified (unless you "upgrade")?
I need to puth the
"binaries" in the container, and the "data" outside the container and I thought settings SBBSCTRL would enable me to do that (ie: it would point to /opt/sbbs/data).
However, it seems the javascript files are found by the
SBBSCTRL path?
Right. The "mods" directory is where modified (or sysop-generated) .js and .src/bin files should be placed. That said, I think a lot of sysops modify the files in exec directly.
No, SBBSCTRL needs to point to the "ctrl" directory.
Everything (configuration, data, and executable files) is found based on the SBBSCTRL path.
Re: Executables for Docker
By: Digital Man to Deon on Tue Oct 16 2018 12:12 pm
Right. The "mods" directory is where modified (or sysop-generated) .js and .src/bin files should be placed. That said, I think a lot of sysops modify the files in exec directly.
OK, good, Docker can accommodate that scenario. So are things searched for in the mods dir first, before being attempted in the exec dir?
No, SBBSCTRL needs to point to the "ctrl" directory.
Ahh, you are correct, I have it pointing to /opt/sbbs/data/ctrl
Everything (configuration, data, and executable files) is found based on the SBBSCTRL path.
OK, this is problematic. I found references to SBBSEXEC on th wiki but it doesnt seem to do anything.
IE: I build with SBBSEXEC set, and I run with it
set (it points to /opt/sbbs/exec), however, I see in the logs it is look for everything in /opt/sbbs/data/exec - which I guess is calculated from '$SBBSCTRL/../exec'?
Is it easy to change that behaviour?
On 10-16-18 12:12, Digital Man wrote to Deon <=-
Right. The "mods" directory is where modified (or sysop-generated) .js
and .src/bin files should be placed. That said, I think a lot of sysops modify the files in exec directly.
That's one thing I really like about Synchronet - the ability to install modes without trashing the original files. I use it as designed and have my mods in mods/
On 10-17-18 00:25, echicken wrote to Tony Langdon <=-
I hope most sysops do it this way. Those who don't ... learn to do so eventually.
Occasionally I end up with stuff in mods/ and forget about it, only to realize I have changes that didn't make their way into CVS, or that I'm not benefitting from changes that have shown up there. Good to go
through that directory and weed it out once in a while. (Mine's a disaster right now with some 100+ files in it.)
Re: Executables for Docker
By: Deon to Digital Man on Wed Oct 17 2018 01:30 am
OK, this is problematic. I found references to SBBSEXEC on th wiki
but it doesnt seem to do anything.
It is optional and usually not necessary.
IE: I build with SBBSEXEC set, and I run with it
set (it points to /opt/sbbs/exec), however, I see in the logs it is
look for everything in /opt/sbbs/data/exec - which I guess is
calculated from '$SBBSCTRL/../exec'?
I don't think there's any behavior that needs to change, but if you do, please elaborate.
Re: Executables for Docker
By: Digital Man to Deon on Tue Oct 16 2018 06:51 pm
Re: Executables for Docker
By: Deon to Digital Man on Wed Oct 17 2018 01:30 am
OK, this is problematic. I found references to SBBSEXEC on th wiki
but it doesnt seem to do anything.
It is optional and usually not necessary.
IE: I build with SBBSEXEC set, and I run with it
set (it points to /opt/sbbs/exec), however, I see in the logs it is
look for everything in /opt/sbbs/data/exec - which I guess is
calculated from '$SBBSCTRL/../exec'?
I don't think there's any behavior that needs to change, but if you do, please elaborate.
Here is what I'm trying to do. The "Application" can live anywhere - I'm choosing to install it in /opt/sbbs (so it is from /opt/sbbs, I run the make install after downloading the makefile from here).
Once the build is complete, in /opt/sbbs I have the sbbs "application" files in /opt/sbbs/exec (and standard web pages in ./web, doors in ./xtrn).. Everything else in /opt/sbbs is considered "configuration" (how SBBS works) or "data" (message, files, menus, etc)... I want to move those files to be under /opt/sbbs/data/{node1,node2,ctrl,text,mods...}.
I set SBBSCTRL to /opt/sbbs/data/ctrl, and with PATH set to /opt/sbbs/exec "scfg" works no problems. However, when I start sbbs /opt/sbbs/exec/sbbs, it starts looking for stuff in /opt/sbbs/data/exec. Now the kludge fix would be to symlink that back, but I would rather fix it properly. (I have executables looked for in /opt/sbbs/exec.) I thought SBBSEXEC would enable that but it appears to not be effective.
Does this make sense?
That's one thing I really like about Synchronet - the ability to install modes without trashing the original files. I use it as designed and have my mods in mods/
I hope most sysops do it this way. Those who don't ... learn to do so eventually.
while this isn't exactly about using docker, it brings me to ask if my modified 404.ssjs that you helped me with should be in /mods and i should restore the original 404.ssjs??
Re: Executables for Docker
By: Deon to Digital Man on Wed Oct 17 2018 12:58 pm
Why? So then you'd have /opt/sbbs/data/data/... seems potentially confusing.
The path to the exec directory (and others) is configured in SCFG->System->Advanced Options. The default (for exec) is "../exec",
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 25 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 34:53:51 |
| Calls: | 1,890 |
| Calls today: | 1 |
| Files: | 11,074 |
| Messages: | 933,562 |