[melbourne-pug] How to go about an aspect of a web app

Tim Richardson tim at growthpath.com.au
Fri Jan 17 14:01:51 CET 2014


hi,  have a look at web2py. it comes distributed as a windows installer,
bundling a python distribution,  a python web server (rocket)  and the
highly productive web2py framework.  Most people move onto a source
distribution and another web server but you can go a long way with the
install bundle.
On 16/01/2014 2:40 pm, "Tennessee Leeuwenburg" <tleeuwenburg at gmail.com>
wrote:

> 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.
>
> 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.
>
> 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.
>
> Cheers,
> -T
>
>
> On Tue, Jan 14, 2014 at 11:29 AM, Rasjid Wilcox <rasjidw at openminddev.net>wrote:
>
>>  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.
>>
>>
>> On 13/01/2014 8:42 PM, Tennessee Leeuwenburg wrote:
>>
>>  Hey,
>>
>>  A question for the peanut gallery...
>>
>>  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.
>>
>>  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.
>>
>>  In fact I think I've pretty much convinced myself given it took just
>> one sentence to say and seems immediately clear.
>>
>>  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.
>>
>>  Cheers,
>> -Tennessee
>>
>>  --
>> --------------------------------------------------
>> Tennessee Leeuwenburg
>> http://myownhat.blogspot.com/
>> "Don't believe everything you think"
>>
>>
>> _______________________________________________
>> melbourne-pug mailing listmelbourne-pug at python.orghttps://mail.python.org/mailman/listinfo/melbourne-pug
>>
>>
>>
>> _______________________________________________
>> melbourne-pug mailing list
>> melbourne-pug at python.org
>> https://mail.python.org/mailman/listinfo/melbourne-pug
>>
>>
>
>
> --
> --------------------------------------------------
> Tennessee Leeuwenburg
> http://myownhat.blogspot.com/
> "Don't believe everything you think"
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/melbourne-pug/attachments/20140118/48947d71/attachment.html>


More information about the melbourne-pug mailing list