<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Tennessee,<br>
<br>
Not exactly 'sexy', but I am currently deploying a Bottle app
(very similar to Flask) using CherryPy's WSGI server. Note that
I'm not using the CherryPy framework, just its WSGI server. Works
well on both Windows and Linux. Under Windows I usually deploy
with Py2Exe, and Linux I usually deploy by running under
Supervisor. There are ways of 'freezing' your app for Linux, but
I've never tried them.<br>
<br>
I had issues running the CherryPy server as a Windows service -
which I worked around using a subprocess, but it doesn't sound
like you will need to go to that level for what you want.<br>
<br>
Cheers,<br>
<br>
Rasjid.<br>
<br>
<br>
On 16/01/2014 2:40 PM, Tennessee Leeuwenburg wrote:<br>
</div>
<blockquote
cite="mid:CADhgxgfz=_KqZ45zQK7Gnee4M+bAwUajhteRJx-5iyzqOUubFg@mail.gmail.com"
type="cite">
<div dir="ltr">Being a massive web app n00b, I am currently just
using the builtin web server in Flask to develop for. In terms
of operational use, I have free choice of web server, and I
haven't yet tried to determine what would be most appropriate.
Advice would be appreciated! ... it will be an internal server
only, but I'd still like to Do It Right even if it's a simple
setup.
<div>
<br>
</div>
<div>The main interest for me is to make it really easy to
install. I was considering trying to write a deploy script to
simplify the process for the user, but I'm not sure if there's
a best recommended way for simplifying deployment. I thought
the application code could be installed into the Python
environment, with a deploy script to create a new workspace
and generate an appropriate web server config snippet as well
as the command to use the Flask built-in server for
development and testing purposes.</div>
<div><br>
</div>
<div>I'm probably asking some slightly odd questions since this
is my first signifiant web app and I don't have much
experience with web app architecture. </div>
<div><br>
</div>
<div>Cheers,</div>
<div>
-T</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Jan 14, 2014 at 11:29 AM,
Rasjid Wilcox <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:rasjidw@openminddev.net" target="_blank">rasjidw@openminddev.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>How is you app being deployed? Is it being run
behind a standard webserver (eg, Apache), or within a
Python based WSGI web-server? If the latter, I would
normally just pass in a command line paramater pointing
either to a config file or perhaps directly to the
project directory in your case.
<div>
<div class="h5"><br>
<br>
On 13/01/2014 8:42 PM, Tennessee Leeuwenburg wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">
<div dir="ltr">
<div>Hey,</div>
<div><br>
</div>
<div>A question for the peanut gallery...</div>
<div><br>
</div>
I'm writing a flask/bootstrap web app (not open
sourced as yet) for doing some scientific
processing in a pipeline data processing
methodology. I want to write an example pipeline,
but then have the app be deployable in user space
and use either a configured directory or a
dot-prefix directory for the data of that
particular instance of the app. I had imagined
this could be like a "layer" over the top of the
core application layer, so that users could have
their projects side-by-side with the core
application examples.
<div> <br>
</div>
<div>I'm now thinking maybe that's a bad idea, and
it would be better just to copy the sample
projects into the users workspace.</div>
<div><br>
</div>
<div>In fact I think I've pretty much convinced
myself given it took just one sentence to say
and seems immediately clear.</div>
<div><br>
</div>
<div>Are there any other paradigms in web apps for
managing the application state (other than
packing everything into a database)? The data
here exists naturally in a fundamentally
file-based paradigm, so I think it makes sense
to continue that mainly.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>-Tennessee</div>
<div>
<div><br>
</div>
-- <br>
--------------------------------------------------<br>
Tennessee Leeuwenburg<br>
<a moz-do-not-send="true"
href="http://myownhat.blogspot.com/"
target="_blank">http://myownhat.blogspot.com/</a><br>
"Don't believe everything you think" </div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<div class="im">
<pre>_______________________________________________
melbourne-pug mailing list
<a moz-do-not-send="true" href="mailto:melbourne-pug@python.org" target="_blank">melbourne-pug@python.org</a>
<a moz-do-not-send="true" href="https://mail.python.org/mailman/listinfo/melbourne-pug" target="_blank">https://mail.python.org/mailman/listinfo/melbourne-pug</a>
</pre>
</div>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
melbourne-pug mailing list<br>
<a moz-do-not-send="true"
href="mailto:melbourne-pug@python.org">melbourne-pug@python.org</a><br>
<a moz-do-not-send="true"
href="https://mail.python.org/mailman/listinfo/melbourne-pug"
target="_blank">https://mail.python.org/mailman/listinfo/melbourne-pug</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
--------------------------------------------------<br>
Tennessee Leeuwenburg<br>
<a moz-do-not-send="true" href="http://myownhat.blogspot.com/">http://myownhat.blogspot.com/</a><br>
"Don't believe everything you think"
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
melbourne-pug mailing list
<a class="moz-txt-link-abbreviated" href="mailto:melbourne-pug@python.org">melbourne-pug@python.org</a>
<a class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/melbourne-pug">https://mail.python.org/mailman/listinfo/melbourne-pug</a>
</pre>
</blockquote>
<br>
</body>
</html>