A "Mothership" is just another s3db deployment, where "Sattelite" deployments can register into.
There are two functions for a mothership: to deliver code and to fit as a deployment discovery service. Both functionalities may exist in the same mothership.
If you are looking into building a mothership only as deployment registry:
1. Create a project (you can download from here the turtle format document and import through S3DB's interface "Import from N3/RDF" feature)
The project should have a collection for the deployments with a set of rules:
PLEASE NOTE: If your rule_ids are different from these, you will need to update config.inc.php accordingly (see below)
2. Create a Key for your Admin user (on the webS3DB interface, open the tab named "Keys" and create a new key)
You will need to add this information (both the project_id, the collection_id and the key) to your config.inc.php. This file can be accessed in S3DB's main directory (e.g. /var/www/s3db_mothership/config.inc.php)
Make sure your Mothership deployment is accepting registrations by using the s3rl.php function described here. Don't forget to replace the default mothership URL with your own mothership URL. You can try a mock url and publicKey for testing, S3DB will not care (e.g. url=http://localhost/mynewdeploymetn&publicKey=test&name=D12345)
- A project
- A collection in that project
- 2 rules, one where the file itself will be uploaded into, one where the path where the file should go to.
(NOTE: Use the following code as example. You will need to create a user, e.g. daemon, with a key, as well as a project, a collection and two rules.)