This is a simple Bitmessage server application made with Jabit. It can be used as a trusted node for the Abit, both for simple synchronization and ‘server proof-of-work’. https://dissem.ch/jabit-server/
Go to file
Christian Basler 701282099a 🤪 Various improvements 2018-06-13 19:19:30 +02:00
classes/artifacts/jabit-server/exploded/server-0.0.1-SNAPSHOT.war/META-INF Initial commit 2015-09-30 18:06:58 +02:00
frontend Some frontend improvements, versioned the backend API 2017-12-10 20:43:24 +01:00
gradle/wrapper Migrated project to Kotlin and created a new frontend 2017-12-08 07:27:42 +01:00
src 🤪 Various improvements 2018-06-13 19:19:30 +02:00
.gitignore Migrated project to Kotlin and created a new frontend 2017-12-08 07:27:42 +01:00
.travis.yml added .travis.yml 2015-11-20 21:45:23 +01:00
LICENSE gradle module and build 2015-10-03 09:05:53 +02:00
README.md Refactored JSON entities to better reflect the actual JSON structure 2015-10-16 06:41:23 +02:00
build.gradle 🤪 Various improvements 2018-06-13 19:19:30 +02:00
gradlew Migrated project to Kotlin and created a new frontend 2017-12-08 07:27:42 +01:00
gradlew.bat Initial commit 2015-09-30 18:06:58 +02:00
settings.gradle Migrated project to Kotlin and created a new frontend 2017-12-08 07:27:42 +01:00

README.md

Jabit Server

This is the server node using the Jabit library. You can run it by calling

java -jar jabit-server.jar

The interface will be available on port 9000, Bitmessage as usual on Port 8444.

There are still a few problems with the interface (the idea is to allow collecting and displaying broadcasts).

On first startup it will create a config file (allowing you to configure the Bitmessage port), a whitelist, a blacklist and a shortlist. If the whitelist isn't empty, the blacklist will be irrelevant. You can disable the feature by simply adding a valid Bitmessage address to the whitelist. For shortlisted addresses, only the last five broadcasts are displayed and stored (useful e.g. for time services or Q's Aktivlist).

Building / Development

You can build the jar file with

./gradlew build

As there is a problem with the build order, you'll need to do this twice.

To deploy on a Ubuntu server (might work on other Linuxes as well), create a file /etc/init/jabit.conf with the following contents:

chdir /srv/jabit

exec su -s /bin/sh -c 'exec "$0" "$@"' jabit -- /usr/bin/java -jar jabit-server.jar --server.port=9000 > /dev/null

start on runlevel [2345]
stop on runlevel [^2345]

there must be a user jabit and a folder /srv/jabit where this user has write permission containing jabit-server.jar.