> For example, if you're deploying via VM, would you just go ahead and package
> Memcached in that VM, or take a different route? Similarly, have you run into
> problems using the migration framework for some enterprise clients?
If the load is small, as it seems to be, and a VM can handle it, why
Todd,
This is django presenting complete Cloud architecture to end user connected
to the core hardware structure at backend. You get registered for example
and spin up a VM, so the signals will get your site session connected to
the core datacenter implementations to complete the task. I remember
Thanks - I intentionally left it vague, as I'd like to better understand
the space of options when working with Python + Django and where headaches
might arise. I suspect there are aspects that seem straightforward, but end
up being a headache for certain environments.
The main application is C
I was part of dinCloud hosting provider and they have complete solution
built in Python/Django. You can see the website where all the VM's
architecture is built using django framework. Its a cloud hosting provider
with few enterprise applications provided as Saas and hardware monitoring
with NOC Pa
Hi,
The solutions depend on what you need and what knowledge and resources you
already have. As you describe it I think it's a bit vague. For example, whether
you will deploy on metal or on VM depends on what load you expect, who
administers the VM, who administers the metal, and so on and so on.
My team is considering using Django for a SaaS/on-premise enterprise web
application. We've been happy with building with Django for SaaS, but don't
have experience deploying and supporting it on-premise in enterprise Linux
and Windows environments. Therefore, we'd like to get the community's
p
6 matches
Mail list logo