While learning Ruby rails I just had it on my Linux server and used a
Linux client to edit/view/debug/debug/debug.. etc. We got along very
nicely, much better than I have with any other web development
environment. (HTML and I simply don't like each other).
Anyway I got web space on an ISP that supports ruby rails, the big
difference is that on my local server I ran rails from the script
Then access with the likes of http://web:3000
My ISP seems to be running it as background process. Which seems sensible
because I don't want to have to keep a ssh terminal open just so I can
keep the site up.
But ISP's being ISP's they don't actually tell you what changes you have
to make to the way you access your site or add to the available
creates the structure as normal (minus most of the document/readme files)
I know that 'script/server' does not expose the site on port :3000. But I
have a feeling that it shouldn't.
So, what is normal practise for ruby rails out on your ISP's servers, for
adding projects to the 'server' and accessing the results?