-
Notifications
You must be signed in to change notification settings - Fork 33
Alpha Testing
Alpha 1 Code has now been released, on or before 15.December 2016. Two main new features, 'Bitmark Storage' & 'Bitmark Passport' have been developed!
- Activity: Smoke Testing Alpha 1 code 15-18 December 2016.
- Activity: Feature Testing Alpha 1 toward Milestone Alpha 2 will take place in the period between 18 December to 21 January.
- Activity: Alpha 2 testing will be a minor bug fix and documentation release running from 22 Jan - 22 Feb
See Roadmap for more detail on Milestone.
Features should be ready for testing. Expected is alpha code for testing and bug fixing. Feature will include a decentralized passport, decentralized storage.
Having a server online or desktop computer would be useful to help testing. Instructions will be provided.
Update: Alpha 1 of bitmark storage was tested by 3 participants. Thanks to those that have tried it. I believe it's working for me and at least one other person. Also we have completed the goal of fixing all major bugs. Now we will move to Alpha 2, which will fix minor bugs. One thing that emerged was that having an older version of node could cause an error message in the installation process, so I'm going to raise this as an issue upstream to aid with installation. Possibly it may be an idea to use pre compiled binaries. Second thing is that to use bitmark storage you need a bitmark passport. There's a few routes to getting a bitmark passport -- either host your own, or use a provider -- this could be documented better. So, moving to alpha 2, will concentrate on minor bug fixes and feature additions (as time allows) of bitmark storage, and testing the integration of those two. Aim is to move now from Alpha 2 to Beta 1 which will be a freeze release, with features finalized.
Bitmark storage will include bitmark passport. Those two elements are part of the feature freeze.
In addition to this feature freeze, there will possibly be paid storage integration, depending on how much can be fit in and how much changes upstream, but that is not part of the feature freeze.
There is also the possibility of some basic facebook and google plus integration, depending on progress upstream. This is also not part of the feature freeze. An update on this will be given around the alpha 2 milestone (see roadmap)
Currently aimed at people running their own cloud storage or home storage that are able to understand running a server or follow instructions.
-
A server with some disk space is required to run bitmark storage.
-
nodejs -- Version 6 or higher
-
git
-
(optional) having your own domain is an advantage
-
Clone the bitmark storage repo
git clone https://github.com/project-bitmark/bitmark-storage && cd bitmark-storage -
run
npm install -
run
node bin/solid initto generate a config (or use a pre determined config and keys)
to generate keys see the section below : generating keys
Note: this is the hardest step -- visit slack for help -- see also answering the init questions below
-
install pm2 ( npm install -g pm2 )
-
run
node bin/solid -v start
(Optional)
-
use pm2 to ensure the process restarts automatically
-
(optional) forward a port to the outside world if not already
-
(optional) if running on your home pc add a dyndns service like noip.com.
-
(optional) CNAME a domain to your storage server
-
(optional) remove SSL warnings using letsencrypt
It is possible to use the defaults for most questions. Some notes:
Path to the folder you want to serve.
This is where you want to host files. Perhaps use ~/data/
There are two ways. 1 is locally
`openssl genrsa 2048 > ./privkey.pem`
`openssl req -new -x509 -nodes -sha256 -days 3650 -key ./privkey.pem -subj '/CN=*.localhost' > ./fullchain.pem`
The second way is to use letsencrypt
There is currently one recommended provider for testing run at MIT
See channel #testing on slack for more info
https://waffle.io/project-bitmark/bitmark-storage
- melvincarvalho (slack)
- brian (slack)
- maxlele (slack)