<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 12, 2015, at 10:47 PM, Willem Ferguson <<a href="mailto:willemferguson@zoology.up.ac.za" class="">willemferguson@zoology.up.ac.za</a>> wrote:</div><div class=""><br class="">Regarding cloud access I am a bit confused with the workflow. Please explain in a bit more detail?<br class=""></div></blockquote><div><br class=""></div>Sure</div><div><br class=""><blockquote type="cite" class=""><div class="">In the preferences panel, should I enter my own email address and an arbitrary password? The pin gets<br class="">sent to my own email address?<br class=""></div></blockquote><div><br class=""></div>Yes, enter your email and a random password (nothing you use elsewhere, please).</div><div>The password is NOT stored in clear text (I'm not quite as clueless as the US government), </div><div>but I don't want to end up causing anyone security issues...</div><div><br class=""><blockquote type="cite" class=""><div class="">If this is so, where does one use <a href="mailto:ssrftest@hohndel.org" class="">ssrftest@hohndel.org</a> and the password associated with that email address?<br class=""></div></blockquote><br class=""></div><div>I set that up so people could play with different parts of this without having to go threw</div><div>the two step process - but it looks like no one did, which is OK, too.</div><div><br class=""></div><div>So the process is like this:</div><div><br class=""></div><div>- enter your email (I obviously won't spam you, this is JUST to send you the PIN)</div><div>- enter a password</div><div>- decide if you want that password stored IN CLEAR TEXT in your preferences</div><div>- hit apply / OK</div><div><br class=""></div><div>- the backend infrastructure sends you a PIN</div><div>- a new field shows up in the preferences where you can enter that PIN</div><div>- again hit apply / OK</div><div><br class=""></div><div>- now the backend infrastructure initializes an empty git repo for you (but</div><div> that's irrelevant... as far as the user is concerned, now the cloud storage</div><div> is set up)</div><div><br class=""></div><div>We don't have a "Save As" function, yet. Basically it's a bit odd to get your </div><div>data into the cloud. Right now the easiest way appears to be to load from</div><div>the cloud storage (gets you an empty file). Import your data, then save to</div><div>cloud, but when I just tested this with a new account it failed, so I'll need</div><div>to debug what's wrong there... I will definitely work if you manually push</div><div>a branch <your email address> to the git repository (basically the "secret"</div><div>git URL is <a href="https://cloud.subsurface.org/git/your_email%5Byour_email%5D" class="">https://cloud.subsurface.org/git/your_email[your_email]</a></div><div><br class=""></div><div>I'll try to fix the "getting data into the cloud storage" issue today...</div><div><br class=""></div><div>Thanks for testing, Willem!</div><div><br class=""></div><div>/D</div><br class=""></body></html>