Noel are you talking about the "RubyGems" button under "Software / Services", or am I missing something?
My rubygems button had stopped working before, but I'm pleased to see that it's up and running again.
I just put a RoR blogging package (free one called simplelog) onto our intranet server at work. It sits along side the application I am working on, in the process I learnt a bit more about the setup so I thought I would share it with you. I don't know how relevant it will be to us lot trying to get rails applications working on the shared hosting packages though.
A rails application is deployed into a folder on the server.
The user and group owner are set along with permissions. (In our case we use a user called "webs" and a group called "mars" - I think this is the group which apache is in.)
We then set up a virtual host within apache - that points to the directory, importantly it points to a proxy, which gives us a URL and a port number.
Then we fire up the rails app in mongrel (using "script/server --environment=production --port=8001").
I don't remember all the exact details as I was just looking over the shoulder of one of the IT guys, but hopefully it gives everyone here a bit more of an idea as to how everything links up in a RoR app deployment.
The important thing to note here is that it doesn't matter what is in the ".htaccess" or "dispatch.xxx" files, they don't get used at all. The IT guy added the command above into some-file-I-know-nothing-about which makes sure it gets started whenever the server is rebooted.
Like I said I don't think this directly helps within the shared host environment, but hopefully helps to explain how things are happening.
My rubygems button had stopped working before, but I'm pleased to see that it's up and running again.
I just put a RoR blogging package (free one called simplelog) onto our intranet server at work. It sits along side the application I am working on, in the process I learnt a bit more about the setup so I thought I would share it with you. I don't know how relevant it will be to us lot trying to get rails applications working on the shared hosting packages though.
A rails application is deployed into a folder on the server.
The user and group owner are set along with permissions. (In our case we use a user called "webs" and a group called "mars" - I think this is the group which apache is in.)
We then set up a virtual host within apache - that points to the directory, importantly it points to a proxy, which gives us a URL and a port number.
Then we fire up the rails app in mongrel (using "script/server --environment=production --port=8001").
I don't remember all the exact details as I was just looking over the shoulder of one of the IT guys, but hopefully it gives everyone here a bit more of an idea as to how everything links up in a RoR app deployment.
The important thing to note here is that it doesn't matter what is in the ".htaccess" or "dispatch.xxx" files, they don't get used at all. The IT guy added the command above into some-file-I-know-nothing-about which makes sure it gets started whenever the server is rebooted.
Like I said I don't think this directly helps within the shared host environment, but hopefully helps to explain how things are happening.
Comment