HOW TO SET UP YOU OWN UCA LINK SERVER
This thread is about how to set up a UCA link server. UCA link servers can be considered as nodes that help spreading transaction knowledge by automating the sync process.
STEP 1 : GET THE SOURCES
First of all you have to get D. J. Bernstein’s ucspi-tcpserver (see http://cr.yp.to/ucspi-tcp.html). There are several ways to get it run. While you can make your own Build we have simply installed the ucspi-tcp-ipv6 debian package via apt-get. Of course you also need the repository of the client as if you were a normal user. See GitHub Readme for how to install the client.
Assuming you have the client, step into this directory and extract the server tools:
tar -xvf server.tar
The following files will be extracted:
control/server.conf
controller.sh
logwatch.sh
filewatch.sh
start_server.sh
stop_server.sh
sender.sh
receiver.sh
Also the folders /log/ and /server/ have been extracted. The folder /log/ is where the server will write the logfiles to. In the folder /server/ the tempfiles of the server are being stored.
STEP 2 : CUSTOMIZE THE SERVER
Modfiy the file control/server.conf . At least you have to enter your IP-Adress and the logon credentials (username, PIN, password) of the user that should be used by the server.
STEP 3 : PUBLISH YOUR UCA LINK SERVER DETAILS
Add a line to uca.conf file in the /control/ folder. The file is a comma separated file (csv) .
The format of the file should be:
IP_OR_URL,SEND_PORT,RECEIVE_PORT,DESCRIPTION,
like e.g.:
127.0.0.1,15000,15001,CUSTOM SERVER,
Send this to your friends and the people that you want to use your server. You could also publish the details in this Forum or somewhere else on the web.
STEP 4 : START THE SERVER
You start the server by running the start_server.sh script:
./start_server.sh
The script will start controller.sh that acts as daemon running and monitoring the scriptssender.sh, receiver.sh, filewatch.sh and logwatch.sh in the background. People can now automatically sync with you by using the UCA link functionality.
STEP 5 : STOP THE SERVER
You stop the server by running the stop_server.sh script:
./stop_server.sh