I wanted to provide some ideas on the dramaturgy of the envisioned screencast.
Undoubtfully useful, I will not be able to prepare one before two weeks in the future.
The clip should develop as follows:
- One starts in some kind of presentation that intoduces the problematic the video is going to solve.
- quick explanation of remoteStorage by a simple diagram
- “You can easily start yourself!”-claimish progression onto the real Starter Kit.
- Screencast shows the path from http://remotestorage.io/ over http://remotestorage.io/integrate/ to https://github.com/remotestorage/starter-kit
- From then on we’re basically following the tutorial.
But the environment in my imagination will be a little different:
The task will not be shown on
localhost, but on a prepared fresh CentOS virtual machine.
By doing this twist, we can also quickly show
- how to setup node.js and
- how to setup EPEL, if appropriate.
Maybe this should really be done in advance, to have a clean workflow displayed. So it’ll be a fresh CentOS, but with activated EPEL repositories, to easily install Node in a current version.
Then one has the server and its client really nice seperated next to each other
And now comes the twist:
A second instance of the same virtual machine exists already in the virtual network and will be shown now to the viewers.
Now referring to diagrams and this little cryptic explanation of Michiel’s
see how the hello-world app runs on port 8002, yet the AJAX requests go to your storage for me@localhost:8001, on storage port 8000.
This is of course useless if it’s on the same host, but you can see how this is a powerful architecture change if not only the port but also the domain name differs between the app and the storage: netizens can host their own data on their own server, instead of on the application provider’s server.
one could underline the implications of this technology and have a connecting point to build on with possible further videos; maybe by other members of this community .
Any comments are highly appreciated!