<html>#2260: provide compiled ET code on tutorial machine
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit Virtual Machine</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>The tutorial server uses docker and each user gets their own docker containers, so we are fine there. The tricky par t is that since the tutorial notebook is supposed to work both in the tutorial docker container as well as standalone and also show the basic workflow when building the Einstein Toolkit we would want to showcase how to use GetComponents (which will behave differently if its output directory exists) and simfactory (which would work fine I think even within an existing build).</p>
<p>As for having new users install docker on their laptop then run inside, this seems not so easy to me as docker is actually not so easy to get up and running and its command line interface is neither stable nor small (or obvious as far as I can tell).</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2260/provide-compiled-et-code-on-tutorial'>https://bitbucket.org/einsteintoolkit/tickets/issues/2260/provide-compiled-et-code-on-tutorial</a></p>
</html>