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

Updates to about

This commit is contained in:
Deon George 2022-01-05 01:16:13 +11:00
parent 847869911f
commit 2f720d6c26
1 changed files with 17 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
resources/views/about.blade.php
View File

@ -17,13 +17,14 @@
So FCH was created to help address that.
</p>
<p>Building this software is driven by two main goals:</p>
<p>Building this software is driven by three main goals:</p>
<ul>
<li>Self Service - so that users can setup and re-jig their configuration themselves, or new users can join a network with the minimum of effort.</li>
<li>Automation - so that repetitive tasks can be done with minimal effort</li>
<li>High Availability - So if one hub goes down, users can automatically connect to an alternate hub to keep mail flowing. Furthermore, as hubs retire, new hubs can assume the role of the retiring hub with minimal effort.</li>
</ul>
<p>So that you can send your time playing on your BBS rather than managing messages/fails or keeping an FTN network running.</p>
<p>So that you can spend your time playing on your BBS rather than managing messages, failures or keeping an FTN network running.</p>
<h3>For the BBS Sysop</h3>
<p>For the BBS sysop, the FTN Clearing House has the following features (or planned ones):</p>
@ -46,7 +47,7 @@ If you have more than 1 BBS, then the Clearing House can receive all your mail f
<li>Supports PING and TRACE responses <sup>To be implemented</sup></li>
<li>Nodelist Management <sup>To be implemented</sup></li>
<li>Network Applications <sup>To be implemented</sup></li>
<li>Dynamic mail bundling for upstream and downstream nodes <sup>To be implemented</sup></li>
<li>Dynamic mail bundling for upstream and downstream nodes</li>
<li>Automatic delisting of idle nodes <sup>To be implemented</sup></li>
</ul>
@ -61,8 +62,20 @@ If you have more than 1 BBS, then the Clearing House can receive all your mail f
<p>To get started, please <a href="{{ url('login') }}">login</a>.</p>
<h4>Open Source</h4>
<p>FTN Clearing House is build with Open Source software. At it's core, PHP drives this web UI and the interaction with nodes.</p>
<p>FTN Clearing House is built with Open Source software. At it's core, PHP drives this web UI and the interaction with nodes.</p>
<p>This web UI has been inspired by the great work at <a href="https://int10h.org">int10h.org</a>. If you have ideas to make it even better, please send me a message, or submit your comments in <a href="https://dev.leenooks.net/bbs/clrghouz">gitlab</a></p>
<h4>Other technology that drives the Clearing Houz</h4>
<p>FCH is made availabe by these technologies:</p>
<ul>
<li>Docker - taking the effort out of building, deploying and easing the effort of upgrading.</li>
<li>CockroachDB - a high available, geodispersable database, that enables accessing configuration and data from multiple locations. CockroachDB enables the FCH to appear as the same hub from multiple locations, providing a high available environment for Sysops to drop off and collect mail</li>
<li>Memcached - to take some of the pressure off CockroachDB</li>
<li>PHP/Laravel - the coding framework used to create this UI, and to enable the transfer of mail between systems</li>
<li>jQuery - to help with the web UI</li>
<li>Highcharts - to render the graphs</li>
</ul>
<span class="float-end"><strong class="highlight">clrghouz</strong> <small>[<strong class="gray">{{ gethostname() }}</strong>@if (File::exists('../VERSION')) @ <strong class="success">{{ chop(File::get('../VERSION')) }}</strong>@endif]</small></span>
@endsection