(archive) Rholang Web 0.1

Owned by Medha Parlikar (Unlicensed)
Last updated: Mar 06, 2018 by Kelly FosterVersion comment
2 min read

Goals:

Provide a mechanism for users to author Rholang smart contracts, compile and run these contracts via a Web interface

Done when:

  • Deliver Rholang Web Sandbox in Docker image.

In more detail:

  • Tutorial specific examples appear in the drop down.  Mercury samples do not appear.
  • Web Sandbox available in Docker distribution.
  • Able to save contracts I create
  • Branding of the Web Compiler matches RChain's look and feel (black and Red at least)

What is needed:

  • What's unique about Rholang
  • Getting started documentation
  • Installation and running instructions
  • Links to tutorial & Developer portal inside the Web interface
  • Pointed specific examples of contracts.
    • New examples authored by Mike - start with 'tut-' 
  • Contributing / getting involved section
  • Download link (location) - Comes with Docker


Testing

  • Test the docker package
  • iPad testing - Medha - tomorrow afternoon.
  • Chrome, Safari -
  • OSX testing - Safari, Chrome



key summary assignee status sprint
Refresh


ProjectRholang
LeadKyle Butt
Status

IN DEV

Start Date 
Completion DateTBD

Stakeholders

NameRoleReviewed
Lucius MeredithCEO- CoOp 
  •  
Nash FosterCEO- Pyrofex 
  •  

Action Items:

  •  

Launch Readiness Review:


Open Issues affecting the release


Docker instructions:

rchain/rholang-web

The compile-and-run pipeline has been packaged up for use as a web application. This application is also made available via docker, so that individuals may run it locally.

docker run -ti --net host rchain/rholang-web

will cause a web server to listen on port 8000, which a browser can reach at localhost:8000.

Note on ports

It has been reported that the default port of 8000 may not work in all cases. Docker has an on-again-off-again relationship with local networking, having been designed for service-level, cloud computing. To try to alleviate some networking pain, the container accepts a single argument (after the image name) that tells it on which port to listen. For example, using host networking (usually the simplest) and port 80 (the normal port for HTTP traffic):

docker run -ti --net host rchain/rholang-web 80

causes the webserver to look "normal" to a browser, so going to localhost may work.

Another alternative to try, if that fails on your machine, is to use docker's own networking and expose the port

docker run -ti -p 80:80 rchain/rholang-web 80

which has been reported to work better in some cases.