bbs/sbbs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added more instructions for mystic usage

Browse Source
This commit is contained in:
Deon George 2019-01-29 14:41:37 +11:00
parent d1412ccac9
commit 957174eaee
No known key found for this signature in database
GPG Key ID: 7670E8DC27415254
1 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
source/_posts/mysticbbs.md
View File

@ -28,6 +28,22 @@ To make sure your data is kept between re-creations of your docker container, yo
2. Start your subsequent containers with `--volumes_from=[ORIG CONTAINER]`.
In this case, you might want to rename your old container if you want to use the same container name.
You could even use this image to have our containers in a docker swarm (as I do).
You need to map some IP ports into the container when it starts, so use `-p HOST_PORT:CONTAINER_PORT`, where **HOST_PORT** is the IP port on the host that you want the services to listen on (it can be the same as the container's ports).
The services you'll probably use are:
<table><tr><th width="20%">Service</th><th width="20%">Port</th><th>Description</th><th>Suggested Mapping</th></tr><tr><td>ssh</td><td>22</td><td>SSH port for incoming SSH connections</td><td>22 (or any port number)</td></tr><tr><td>telnet</td><td>23</td><td>Telnet port for incoming telnet connections</td><td>23 (or any port number)</td></tr><tr><td>binkp</td><td>24554</td><td>BINKP port for incoming BBS Mail/File Transfers</td><td>24554 (or any port number)</td></tr></table>
For example, if you wanted to map telnet to port 10023, ssh to port 10022, and leave binkp as it, and use */srv/docker/mystic* on the host as your persistant storage inside the container, you would use:
```
docker run -it -v /srv/docker/mystic:/mystic data -p 10022:22 -p 10023:23 -p 24554:24554 registry.leenooks.net/leenooks/mysticbbs:1.12a39-armv7l
```
when it starts, it will output the container ID.
Once your container is running, you can run the mystic utils by running: `docker exec -it <CONTAINER_ID> [COMMAND]` where **COMMAND** is the command you wanted to run, eg `./mystic -cfg`, or `./fidopoll ...`.
You can also attach to the console to see what mystic is showing `docker attach <CONTAINER_ID>`, and to detach, you'll need to press **CTRL-PQ** (which is ctrl p, ctrl q). (**NOTE**: You might need to press a key, to refresh the screen - using your arrows is safe.)
You could even use this image to have your containers in a docker swarm (as I do).
If you need any help, [login](/2018/08/31/chinwag/) to my BBS and send me a message, or if you use another BBS, or a Sysop of a BBS and connected to one of the networks I'm connected to, you can send me a Netmail. See the list of [networks](/networks) that I'm already connected to.