copious-endpoints v1.2.1
copious-endpoints
This module is from the github repository for copious-blog-entries. This is a subdirectory and its own project.
This module provides servers that enter bloggable content into directories and other stores for access by mini-link-server applications which present media links to blog interfaces and their search mechanism.
Two kinds of command line interfaces are provided:
- copious-users
- copious-contacts
A third kind service has been moved. The service copious-persistence will have its own repository and package since it requires larger libraries such as IPFS.
User applications store records which aid in associating a kind of user identity with assets. This is for the operation of the system as an asset tracker and has little to do with authorization which is handled elsewhere by making use of distributed identities.
Persistence applications manage assets and provide the means of managing asset publication and linking assets with counting services, which provide mechanisms for paying asset creators.
Installation
npm install -g copious-endpointsNote: npm has been touchy about installation. Please refer to this article for a smoother installation process: my article
Running
Once the module is installed, you can run the programs from the command line. Use the two commands as follows:
copious-users relay-service.confcopious-contacts contact-service.confThe first command will launch the user record managment service. This service is fairly local to the server. It will look for keys in keys directory.
The second command will launch all the differents kinds of persistence services that are specified in the configureations. It will also look for keys in keys directory.
Some other directories may need to be created on the top level. It may help to issue the following commands prior to running the services.
mkdir users
mkdir assets
mkdir dataConfiguring
The following configuration file is for three services, a relay service that switches packets to endpoints from any number clients, a user manager services, and a persistence service. (The contact service configuration is follows after it.) The configuration file specifies all that will be needed to make connections, startup as a server, idenitify directories for storage, etc. Here is an example of the configuration file:
{
"port" : 5112,
"address" : "localhost",
"path_types" : {
"outgo_email" : {
"relay" : {
"files_only" : true,
"file_per_message" : false,
"output_dir" : "mail",
"output_file" : "outgoing",
"wrap_limit" : 50
}
},
"contact" : {
"relay" : {
"files_only" : true,
"file_per_message" : false,
"output_dir" : "contacts",
"output_file" : "contacts",
"wrap_limit" : 50
}
},
"user" : {
"relay" : {
"files_only" : false,
"output_dir" : "fail_over_user",
"output_file" : "/user_data.json",
"port" : 5114,
"address" : "localhost",
"max_pending_messages" : false,
"file_shunting" : false,
"max_reconnect" : 24,
"reconnect_wait" : 5,
"attempt_reconnect" : true
}
},
"persistence" : {
"relay" : {
"files_only" : false,
"output_dir" : "fail_over_persistence",
"output_file" : "/user_data.json",
"port" : 5116,
"address" : "localhost",
"max_pending_messages" : false,
"file_shunting" : false,
"max_reconnect" : 24,
"reconnect_wait" : 5,
"attempt_reconnect" : true
},
"types" : [ "assets", "blog", "demo", "ownership", "stream" ]
},
"paid-persistence" : {
"relay" : {
"files_only" : false,
"output_dir" : "fail_over_persistence",
"output_file" : "/user_data.json",
"port" : 5117,
"address" : "localhost",
"max_pending_messages" : false,
"file_shunting" : false,
"max_reconnect" : 24,
"reconnect_wait" : 5,
"attempt_reconnect" : true
},
"types" : [ "assets", "blog", "demo", "ownership", "stream" ]
}
},
"launch_endpoints" : {
"user_endpoint" : [ "endpoints/user_category_server", "relay-service.conf" ],
"persistence_endpoint" : [ "endpoints/persistence_category_server", "relay-service.conf", "free" ],
"paid_persistence_endpoint" : [ "endpoints/persistence_category_server", "relay-service.conf", "paid" ]
},
"user_endpoint" : {
"port" : 5114,
"address" : "localhost",
"app_handles_subscriptions" : true,
"user_directory" : "test/assets/users",
"directories" : [ "blog", "stream", "demo", "links" , "ownership", "wallet", "assets" ],
"create_OK" : true,
"remove_OK" : true,
"all_users" : "test/users",
"_gen_targets" : ["dashboard", "profile"],
"user_file_sep" : "+",
"tls" : {
"server_key" : "keys/ec_key.pem",
"server_cert" : "keys/ec_crt.crt",
"client_cert" : "keys/cl_ec_crt.crt"
}
},
"persistence_endpoint" : {
"port" : 5116,
"address" : "localhost",
"user_directory" : "test/assets/users",
"directories" : [ "blog", "stream", "demo", "links" , "ownership", "wallet", "assets" ],
"counting_service" : "localhost:6767",
"multi_meta_hanlders" : {
"meta" : "meta_searching",
"counting" : "counting_service"
},
"tls" : {
"server_key" : "keys/ec_key.pem",
"server_cert" : "keys/ec_crt.crt",
"client_cert" : "keys/cl_ec_crt.crt"
},
"ucwid" : {
"pk_str": "public key",
"priv_key": "private key"
},
"ipfs": {
"dir" : "persistence-ipfs-repo",
"swarm_tcp" : 4026,
"swarm_ws" : 4027,
"api_port" : 5026,
"tcp_gateway" : 9294
},
"publication_directories" : {
"blog" : "test/persistence/blog",
"stream" : "test/persistence/stream",
"demo" : "test/persistence/demo",
"links" : "test/persistence/links",
"contacts" : "test/persistence/links",
"ownership" : "test/persistence/ownership",
"wallet" : "test/persistence/wallet",
"assets" : "test/persistence/assets"
},
"entry_types_to_producers" : {
"blog" : "dashboard",
"stream" : "dashboard",
"demo" : "dashboard",
"links" : "dashboard",
"contacts" : "profile",
"ownership" : "profile",
"wallet" : "profile",
"assets" : "profile"
},
"all_users" : "test/users",
"create_OK" : true,
"remove_OK" : true
},
"paid_persistence_endpoint" : {
"port" : 5117,
"address" : "localhost",
"user_directory" : "test/assets/users",
"directories" : [ "blog", "stream", "demo", "links" , "ownership", "wallet", "assets" ],
"counting_service" : "localhost:6767",
"multi_meta_hanlders" : {
"meta" : "meta_searching",
"counting" : "counting_service"
},
"tls" : {
"server_key" : "keys/ec_key.pem",
"server_cert" : "keys/ec_crt.crt",
"client_cert" : "keys/cl_ec_crt.crt"
},
"ucwid" : {
"pk_str": "public key",
"priv_key": "private key"
},
"ipfs": {
"dir" : "paid-persistence-ipfs-repo",
"swarm_tcp" : 4028,
"swarm_ws" : 4029,
"api_port" : 5028,
"tcp_gateway" : 9296
},
"publication_directories" : {
"blog" : "test/paid-persistence/blog",
"stream" : "test/paid-persistence/stream",
"demo" : "test/paid-persistence/demo",
"links" : "test/persistence/links",
"contacts" : "test/paid-persistence/links",
"ownership" : "test/paid-persistence/ownership",
"wallet" : "test/paid-persistence/wallet",
"assets" : "test/paid-persistence/assets"
},
"entry_types_to_producers" : {
"blog" : "dashboard",
"stream" : "dashboard",
"demo" : "dashboard",
"links" : "dashboard",
"contacts" : "profile",
"ownership" : "profile",
"wallet" : "profile",
"assets" : "profile"
},
"all_users" : "test/users",
"create_OK" : true,
"remove_OK" : true
}
}contact configuration
Here is a configuration file for copious-contacts:
{
"port" : 5336,
"address" : "localhost",
"user_directory" : "./assets/users",
"contacts_directory" : "./contacts",
"directories" : [ "contacts" ],
"multi_meta_hanlders" : {
"meta" : "meta_searching"
},
"tls" : {
"server_key" : "keys/ec_key.pem",
"server_cert" : "keys/ec_crt.crt",
"client_cert" : "keys/cl_ec_crt.crt"
},
"ucwid" : {
"pk_str": "public key",
"priv_key": "private key"
},
"publication_directories" : {
"contact" : "./contact"
},
"entry_types_to_producers" : {
"contacts" : "profile"
},
"all_users" : "./users",
"create_OK" : true,
"remove_OK" : true,
"launch_endpoints" : {
"contact_endpoint" : [ "endpoints/contact_category_server", "contact-service.conf" ]
}
}NOTE:
All crypto keys in this repository are for examples only. Do not expect them to work on any data stored and retrievable by these tools.
blog-services a.k.a. copious-endpoints
Theses services run a tpc/ip service built on top of node.js, making use of the net module and its TLS provisions. This service derives from categorical-handlers, which is a specialization of the endpoint class from the message-relay-services package.
The entries, these applications make, are the JSON objects containing the link and other meta data about the links.
For instance, the persistence services interact with the mini-link-servers, which provide asset searching, with blogs and streamers, and with counting services.
See for example:
client examples
Some of the client operations that interact with these services can be found in the desktop application provided by copious-blog-entries desktop tool
The NW app will actually load files into IPFS. But, the blog services will only accept persistence record entries with IPFS CIDs in fields. The blog services may make sure the content identified by a CIDs are available for presentation by blog interfaces.
The contact services client is being used by the basic version of captcha-igid which is one of the copious-transition-apps.
A note on generating keys
Here is an article about generating keys for these applications: Elliptic Curve TLSv1.3.
You can see above, that for the contact example, the tls field is as follows:
"tls" : {
"server_key" : "keys/ec_key.pem",
"server_cert" : "keys/ec_crt.crt",
"client_cert" : "keys/cl_ec_crt.crt"
}When you run the commands shown in the article with an empty keys directory, you will only get two keys.
Here are the commands again:
$ openssl ecparam -name secp384r1 -genkey -out keys/ec_key.pem
$ openssl req -new -x509 -key keys/ec_key.pem -sha256 -nodes -out keys/ec_crt.crt -days 365After running these commands, there are just two files in the keys directory:
- ec_key.pem
- ec_crt.crt
In the test directory, there is a client.js that publishes messages to the contact server. Here is the configuration found in the javascript code:
{
"port" : 5336,
"address" : "localhost",
"files_only" : false,
"output_dir" : "fail_over_persistence",
"output_file" : "./user_data.json",
"max_pending_messages" : false,
"file_shunting" : false,
"max_reconnect" : 24,
"reconnect_wait" : 5,
"attempt_reconnect" : true,
"tls" : {
"client_key" : "ckeys/ec_key.pem",
"client_cert" : "ckeys/ec_crt.crt",
"server_cert" : "ckeys/srv_ec_crt.crt"
}
}Notice that for the client, another directory ckeys, has been made, The client has its own .pem and .cert files But, it refers to ckeys/srv_ec_crt.crt. And, the server had these fields: "client_cert" : "keys/cl_ec_crt.crt".
Where did these files come from? Well... they are just copies.
Here are *nix copy commands that put the certs into the right directories:
$cp keys/ec_crt.crt ckeys/srv_ec_crt.crt
$cp ckeys/ec_crt.crt keys/cl_ec_crt.crtSometimes its easy to forget this simple state of affairs.
Just keep in mind that you will want to copy srv_ec_crt.crt to all the key directories of clients.