Hi curious, The only thing I really modified was taking gluon out of the web2py dir and putting it in the libs dir (and really that doesn't even need to be done, I was just trying to confirm to the openshift project structuring when I was first experimenting). Other then that, you can just make sure your setup.py in the main project directory has the necessary requires modules (for whatever extra you may be using). If you run into any specific problems, just open an issue on my git repo for the template and we'll work it out.
Openshift will always have a free tier and the lowest paid tier is supposed to be around ~$40ish /mo. That gives you up to 16 instances which is quite a bit. On the free tier you'll have 3 instances and up to 1gb disk those and 512mb of memory. Also, to add on to some of what Alec said, in the past you couldn't hot deploy, but that's a feature that's been voted up and I believe may be coming soon. You can always check the suggested features on openshift.com It has mysql, postgres and mongodb available from a data model, and there are DIY options where you could implement something like a separate redis or memcached. If you have any questions feel free to post in the forums and point me to it and I'll do my best to answer. The community around Openshift is pretty good so they'll probably answer as well. Andrew On Sunday, August 19, 2012 3:16:23 PM UTC-5, curiouslearn wrote: > > Alec, > > I was thinking of trying out Red Hat Openshift and came across your > repository. While I have not tried your instructions yet, and they will > most probably work, unfortunately, the things that you modified in the > web2py folder is not clear from those instructions. If it is not too > complicated, can you please post some instructions on how to modify a fresh > web2py (install from source) folder. For example, things such as location > of .yml file, does the name of setup.py need to be changed (as is required > for dotcloud hosting). > > That would be really helpful. > > Thanks. > > On Sunday, August 19, 2012 10:29:22 AM UTC-4, Alec Taylor wrote: >> >> I'm using Red Hat OpenShift. >> >> How to setup web2py on it: >> https://github.com/prelegalwonder/openshift_web2py/ >> >> It is free for the moment, not sure when they're going to start charging >> for it. >> >> Major disadvantage is that the way they have setup git means the whole >> site goes down everytime you push. This might be something that web2py >> can fix with a custom integration package. >> >> On Sun, Aug 19, 2012 at 9:54 AM, Simon Carr <simon...@gmail.com> wrote: >> > After a few weeks of getting to know web2py i have decided that it >> should become one of the development tools in my tool belt. >> > >> > The only thing that is stopping me moving on however is hosting >> options. I am going to take a look at app engine as one option but i need >> to know that i can also deploy on a standard web server. >> > >> > I would need to be able to use apache which i know web2py can do but i >> am not sure how complicated this is. I also think that I am going to need >> to use a VPS but these go up in price very quickly beyond 1gb and 1 cpu. >> > >> > Can anyone give some comments on where they host, what spec server >> they have and what performance they get. >> > >> > Thanks >> > Simon >> > >> > -- >> > >> > >> > >> > --
