I would also recommend checking out Heroku for a quicker test release. Down the 
line, when you want more control over the system administration, you can save a 
bit of money by building out your own services.

> On Jun 10, 2015, at 8:35 AM, Vijay Khemlani <[email protected]> wrote:
> 
> Wihtout knowing anything about your project, I think going RedHat + Oracle 
> might be a bit overkill, especially Oracle since it is a mess to configure 
> and tune.
> 
> Have you considered CentOS as an alternative? same binaries and libraries as 
> RedHat but completely free, and also easier to deploy in the typical VPS 
> providers (Linode, DigitalOcean, etc). For the database PostgreSQL is solid 
> and (kinda) simple to deploy and configure.
> 
> 
>> On Wed, Jun 10, 2015 at 7:36 AM, Jason <[email protected]> wrote:
>> We are a group of developers that are reasonable new to the Django web 
>> framework. We've managed to build an application that is currently housed in 
>> PythonAnywhere and are now at the stage where we would like to conduct some 
>> performance testing.
>> 
>> Our current plan is to rent some space from a VPN provider with 
>> production-like specs and start testing the performance of our application. 
>> However, whilst we are reasonably capable at building our application, we 
>> are new to the deployment of things in Virtual environments (including OS, 
>> database software etc...).
>> 
>> We are planning to use Red Hat Linux for the OS and an Oracle database for 
>> the initial deployment and would appreciate any ideas on how to go about 
>> gaining some assistance with this. To start with, we are planning to have 
>> the application code and the database under one virtual server and later on 
>> we will test the separation of the database and the application code.
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/c4e4dbd6-c50c-41b3-92c3-5d9d6ba8472e%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/CALn3ei1YQN1f78w6_COm2JcoDLgyPGry5%2BYc%3D6tuXhWPrEhBLg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/6AB5A293-E70A-459A-95E0-A42A09D12447%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to