Deploy

To publish your service in a network, you need to have access to at least one node in the network; we assume that they are properly set up (with an node id seed specified), see Starting A las2peer Network and L2pNodeLauncher Commands. On the first node that should run your service, follow these steps:

• Copy the service jar and its dependencies to the node's services folder.
• If your service uses a .properties file, copy it into the etc folder.
• Start the service: startService('[email protected]'), see also L2pNodeLauncher Commands. You may add this command to your start script in the bin folder.

Now, the service is available in the whole network. If the capacity of one node is not enough, you can run it on multiple nodes following the same steps on each additional node.

Versioning

Please use the Semantic Versioning scheme to version your service. Increase the version number each time you update your service and follow the steps above to deploy it.

This has the advantage that services and frontends using your service will not break if your service changes its API.