rchain / rsong-acquisition

RSong Asset Acquisition

RSong Acquisition

This repository is archived in favor of rsong

A minimal utility for loading RSong binary assets to RChain.

Caution

This project is still under active development.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system

Install

• Prerequisites
• Clone & Build
• Execute

Prerequisites

• sbt
• JDK8
• docker

Clone & Build

git clone [email protected]:kayvank/rsong-acquisition.git
cd rsong-acquisition
sbt compile 
sbt universal:packageBin

Execute

To run the project locally:

• make sure you have a local instance of rnode up and running
• execute the project:

sbt run
## alternatively
sbt clean compile universal:pacageBin
cd target/universal
unzip ./rsong-acquisition-1.2-SNAPSHOT.zip
cd rsong-acquisition-1.2-SNAPSHOT/

./bin/rsong-acquisition   

Detail

• Install rsong contract:

./bin/rsong-acquisition  Install  

• Deploy and Propose rsong assets to block-chain:

./bin/rsong-acquisition  Deploy

• Install contract, deploy and propose assets

./bin/rsong-acquisition 

Environment variables

tbd

Running tests:

There are minimal unit tests.

tests are:

• unit tests
• integration tests

Unit tests

sbt clean test

Future work

• rsong-acquisition should work against an asset manifest
• add acquisitions against aws s3, dropbox, and other cloud related storage dev.
• use environment variables to target diff rnode installations
• impl monix

References

• docker-image
• Rholang
• RChain Cooperative
• http4s

rsong-acquisition's Issues

upgrade rsong-acquisition to node 0.8.4

this task requires

1. upgrading the rsong rnode
2. coordinate the upgrade with rsong-acquisition upgrade to noe-8

create manifest.json file for asset acquisition

Summary:

create a manifest.json file for asset digestion

Detail:

manifest file contains asset metadata. This file allowes

• aggregate assets into product

migrate Rsong to Rchain GCP account

Summary:

migrate to RChain kubernetes account.

Detail:

RSong app was developed under my GCP account, kayvan. Simple transfer of project to Rchain GCP account is not possible without involving and creating Google tickets.

Required-Work

1. create a new k8 kluster
2. create a new VM for rnode
3. create required dns names
4. create required ingress and tls

Drive a cost estimate for RSong

1 RSong cost estimate

The purpose of this doc is start RSong development cost estimates.

1.1 current cost

  current cost includes:


1.1.1 kubernetes cluster
------------------------


1.1.2 rnode VM
--------------


1.1.3 storing assets on chain. This is approximately 75 Meg for the current 3 assets
------------------------------------------------------------------------------------


1.1.4 google cloud build
------------------------


1.1.5 required static IP
------------------------

  You may get the current cost from Ian as the account is under his
  control.


1.2 future known cost create a

1.2.1 new dev environment

• 1.2.1.1 expected additional cost is 25%

1.2.2 adding 2nd rNode to prod

• 1.2.2.1 expected cost is additional 7%

1.3 Expected increased cost to add more feature to RSong

  This cost increase will depend on required features and expected load.


1.3.1 Factors influencing the cost
----------------------------------

* 1.3.1.1 Are assets stored on chain or off chain


* 1.3.1.2 expected number of assets

  + 1.3.1.2.1 expected number of assets

    if immersion, make sure you double the number of the 3D and Stereo
    versions