Yes, this is certainly an option. But I didn't mention it because Tom mentioned that he wanted to avoid a technical option, and I associated WebEnabled in my mind with an installation profile.<div><br></div><div>However, of course, he can just leave the account in a certain state, to be shared with those who access it, as you say. But that could be done on any server...<br>
<div><br></div><div>But I love the convenience of WebEnabled, many developers would profit greatly by incorporating it into their workflow, and I reviewed it positively on my blog: <a href="http://awebfactory.com.ar/node/432">http://awebfactory.com.ar/node/432</a></div>
<div><br></div><div><a href="http://awebfactory.com.ar/node/432"></a>Victor<br><br><div class="gmail_quote">On Sat, May 29, 2010 at 5:59 PM, Michael Anello <span dir="ltr"><<a href="mailto:michael@anelloconsulting.com">michael@anelloconsulting.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Tom,<br>
<br>
One other alternative is to utilize a site like WebEnabled.com. They<br>
are big Drupal supporters and have a great "clone" feature that we use<br>
during our workshops all the time.<br>
<br>
We normally teach the entire workshop off of a WebEnabled account,<br>
then at the end of the day, we "share" the Drupal application with our<br>
students via a URL. Upon visiting the URL, each student gets a clone<br>
of the application as we left it at the end of the workshop. It works<br>
quite well for us. WebEnabled accounts are free for up to 2<br>
applications.<br>
<br>
Full disclaimer: I don't work for WebEnabled, but they are a sponsor<br>
of our podcast.<br>
<br>
-mike<br>
DrupalEasy.com<br>
_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</blockquote></div><br></div></div>