Did anyone said Thread Alert? 

I think I've heard something, so let's talk
Tryorama Control Protocol (TryCP)
We have an update to Tryorama (formerly Try-o-rama), which takes a new approach to setting up conductor configurations. 
-
-
Introducing TryCP
6/6
(...) a better picture of how machines running your hApp will function in realistic conditions (e.g., simulating hardware, dog chews through ethernet cable, toddler unplugs HoloPort, etc.).pic.twitter.com/0aMJWdacm8Show this thread -
Updates to Tryorama
Speaking of Tryorama, our just-released version 0.2.0 has some new features and breaking changes.
Name change
TryCP integration
Breaking change: New conductor configuration processShow this thread -
Name change 1/2
As you may have already noticed, the first change is that we removed the dashes from the name. We realized “Try-o-rama” couldn’t be used in code—plus, removing the dashes saves you a few keystrokes.Show this thread -
Name change 2/2
The name change has already been made in both our GitHub repo and NPM package listing. You can still mentally insert the dashes if you prefer :-)Show this thread -
TryCP integration 1/3
More significantly, this new release gives you the ability to manage remote conductors during scenario testing by integrating TryCP.Show this thread -
TryCP integration 2/3
If you have access to machines running a server that speaks TryCP, you can easily set up your tests to spin up conductors on your remote machines, rather than on the local one running the tests.Show this thread -
TryCP integration 3/3
This will extend the functionality of Tryorama and make it easier for you to do end-to-end testing in real-world settings, which was one of our goals in developing Tryorama.Show this thread -
Breaking change: New conductor configuration process 1/9
The new release introduces a breaking change to the way conductor configuration is specified.Show this thread -
Breaking change: New conductor configuration process 2/9
In previous versions of Tryorama, the API was set up to take an 'easy’ (sugared) or 'hard' (plain) approach to configuration.Show this thread -
Breaking change: New conductor configuration process 3/9
One version, with a single required field, was designed for common cases; the other version, which was more verbose, was for special cases where very specific configurations were necessary.Show this thread -
Breaking change: New conductor configuration process 4/9
This allowed common conductor configurations to be created easily, with as little boilerplate as possible.Show this thread -
Breaking change: New conductor configuration process 5/9
The problem was that if you departed from the well trodden path in any significant way, you had to switch to ‘hard’ (plain).Show this thread -
Breaking change: New conductor configuration process 6/9
To simplify, we have merged these two approaches into one process in Tryorama 0.2.0, as well as making it more expressive.Show this thread -
Breaking change: New conductor configuration process 7/9
This means that with just a slight increase in boilerplate, you can write test conductor config files without much effort and gradually add more complexity as needed.Show this thread -
Breaking change: New conductor configuration process 8/9
Unlike earlier versions, you won’t have to make the leap from ‘easy’ to ‘hard’ if you need a greater degree of customization.Show this thread -
Breaking change: New conductor configuration process 9/9
We encourage you to check out the repo for Tryorama, which lays out the conductor config process in more detail. Please offer any feedback you may have to help us improve Tryorama for the future.Show this thread -
and that's all folks! If you prefer to read it all in one piece please check this link:
http://ow.ly/5EHT50xkV6U
#Holochain#TryOramapic.twitter.com/r2PxNOpo4ZShow this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
