Simon Biggs

@alysivji I was reading some of your blog posts and I noticed quite a speciality in docker-compose. Might you be keen on working on this with me?

The target use case is to have a tool where someone can create a ScriptedForms server within their work intranet. Having multiple users, each with a JupyterHub sign in users...

Yes that sounds perfect. By the sounds of it I think I'll learn a few things from this. That will be nice :). Postgres db is for people to use...

Nah, that's not what I was going to do. That will exist within jupyterlab eventually and when I build a jupyterlab extension for this the variable explorer will then come...

This would also be a stepping stone to being able to make the form sections be more transferrable. Meaning a custom layout file would be more possible...

And I think the custom layout file is the way I want to go with respect to documentation... So full circle. I've thought about docs. Now is not the time...

:) we'll see how we go :) On Thu., 19 Apr. 2018, 11:42 pm Robin, wrote: > @SimonBiggs understood -> if required for > documentation then should be implemented first...

@robmarkcole along the same "keeping it simple" vein, does this proposal keep the basics simple do you think? Should I be looking at section naming redesign, or is it okay...

@robmarkcole Thanks for the feedback :) After your response I have done more editing of the top post trying to make the names more succinct. Is the swap of 'section'...

I don't believe this is name changing for name changing sake. At the beginning I only had `start`, `button` and `live`. The name `live` was chosen to contrast against `button`,...