Java'o'Fido: continued

More than a year has passed since I started writing the jNode project, and now it's time for the first release. This does not mean that all this time the project was unused, not at all - only in the Russian region at least 5 nodes use jNode. But all this time the project was in the unstable stage. If you want to use - download the sources, compile them, set up the configuration file and fill the database with initial values. And nothing else.

But now (finally!) It is time to restore justice and give everyone the opportunity to raise their knot in Fido simply and without problems with minimal effort. By the way, I know that Fido is dead, all polymers are long gone, and we are a bunch of old (and young) marazmatik.

Technical process

Fidonet is interesting to me because it lacks so many simple and familiar things that are present on the Internet. It's like being in the jungle with a knife and one match. Do you want to post from RSS - write software! Want to make reading mail through the web - write software! Want $ feature - write software! Well, or persuade someone else to write it.

Actually, it is for this reason that jNode, which initially arose “with nothing to do”, became a full-fledged platform for developing an FTN system of any complexity. Even the basic (“core”) part of the system already covers 100% of the needs of a regular host — it can receive, send and store mail, supports robots, scripts, timer start-up and other useful things.
')
And in order to make everything quite convenient, the module mechanism was introduced, which allows to implement any feature using the API provided by the kernel. So, for ease of use, my teammate General_Manjago made a control module via XMLRPC, and I wrote a Jabber bot for myself. Of course, as the modules evolved, the API developed as well - the necessary and useful features from the modules fell into the kernel. So, recently suddenly and completely one of the main parts of the program was rewritten - implementation of the Binkp protocol . Finally figured out java.nio. *

At the same time, everyone in jNode does not have a drop of "Enterprise". It quietly runs on a router with Linux on board, and my 30+ links and 44 threads in the pool use only 12 megabytes of RAM. Net Java SE and no factories for you.

Opportunities

• Work wherever there is 15 megabytes of memory and jre 1.7
• Support for all basic functions of the FTN system: mailer, tosser, tracker
• Module support: both your own and third-party
• Built-in JavaScript scripts, built-in scheduler
• Support for most relational DBMSs for which there are jdbc drivers
• WEB-UI for node management
• With successfully established stars, unfolding a full node takes about 3-5 minutes.

Release

And those stars that are from the previous point, so successfully formed that today we released the first stable release available for download. In fact, for me this is the first public rather large opensource project. Most of these projects were scattered in the form of sources in different corners until the next death of the hard drive did not send them to the paradise for programs. So you can congratulate, thank you.

In general - here: github.com/annmuor/jnode/releases/tag/1.0

H2 is built into this package, so nothing but jre 1.7 is needed to run.
Installation instructions are in the docs folder.
A typical usage scenario involves installing jNode on a VDS / VPS / other server and remote control using a technical point and a web interface.

Who needs

If you once had a node in Fido , this can help you return to the network without sticking tricky configs in DOS.
If you have aka aka - you can quickly install the node and become a member of the network.
And if there is nothing like that - you can write a comment “Fido is dead”, or try to get a point.

UPD: Updated the main release, laid out the assembly under 1.6: github.com/annmuor/jnode/releases/tag/1.0-jre6
UPD # 2: And still give points here , on my site.