There is a really good walkthrough for slicehost deployment of nginx /
mongrel_cluster at urbanpuddle.com -- be careful with the switches, as there
are some user-name configs that may differ should you go with mongrel.
Last, but even better, log onto freenode and join channel #slicehost (/j
#slicehost)..  Ryan52, in particular, is very helpful and kind.  You may
want to say hi from tefflox when you /msg him ;-)

On Tue, Aug 19, 2008 at 10:30 AM, Jesse Crockett <[EMAIL PROTECTED]> wrote:

> I suppose I should state that my configuration was Nginx and two
> mongrels... haven't read word one on Thin..
>
>
> On Tue, Aug 19, 2008 at 10:28 AM, Jesse Crockett <[EMAIL PROTECTED]>wrote:
>
>> The problems I encountered on slicehost were due to storing them in su
>> protected environments such as /var/www.  I followed the tutorials by
>> letter, tho I did start from scratch, keeping production directories in
>> /home/jess/[site], and it cleared smoothed everything over.  If still very
>> close to development, I suggest re-installing to your home directory.  Has
>> the deployment worked in /var/www at all?  I can't remember if mine ever
>> worked there, but my efforts to chmod started to get tedious, and in my
>> experience it's best not to tinker with integral settings.  Again, my best
>> advise is re-mapping to /home.  It may take two or three go-rounds in all,
>> so keep all the tutorial tabs open. :-)
>>
>>
>> On Tue, Aug 19, 2008 at 10:06 AM, Vict0r <[EMAIL PROTECTED]> wrote:
>>
>>>
>>> Hi Jesse -
>>>
>>> Thanks for answering -
>>>
>>> Slicehost is exactly where I am, and I went through their tutorials
>>> word for word; I am just storing the sites in /var/www/site1.com and /
>>> var/www/site2.com as opposed to doing it in /home/username/public_html/
>>> site1.com and /home/username/public_html/site2.com as they are
>>> suggesting.
>>>
>>> Everything else I followed to the letter - and now I am getting
>>> Insoshi's 500.html page instead of a home page.
>>>
>>> In the beginning Thin would look like it was starting (in response to
>>> the start command) and then would quietly exit, without even a message
>>> - I documented it here (comments on the very bottom):
>>>
>>> http://articles.slicehost.com/2008/5/6/ubuntu-hardy-thin-web-server-for-ruby
>>>
>>> Now however, when that Insoshi appears to be properly configured (?) I
>>> rebooted the VM and 3 Thin processes show up in "ps ax" list and their
>>> log files do not show errors - so they do nto exit like before.
>>>
>>> I should probably mention that Ruby and Rails are the latest stable
>>> too.
>>>
>>> Any Ideas? I just spent the whole night with no sleep on this...
>>>
>>> Victor
>>>
>>> On Aug 19, 8:44 am, "Jesse Crockett" <[EMAIL PROTECTED]> wrote:
>>> > The slicehost.com tutorials are worth looking into, even if you're not
>>> on
>>> > slicehost.  Their support and maintenance of these exact sort of
>>> problems is
>>> > bar none, very good indeed.  Depthy tutorials for mongrels, phusion,
>>> > servers, the works.  Also forums for asking questions.  Slicehost is
>>> > building a rather friendly community.  Good place for quick answers on
>>> VPS
>>> > deployment.
>>> >
>>> >
>>> >
>>> > On Tue, Aug 19, 2008 at 5:31 AM, Vict0r <[EMAIL PROTECTED]>
>>> wrote:
>>> >
>>> > > Hi -
>>> >
>>> > > First of all thank you for your Insoshi development!
>>> >
>>> > > I am trying to get it Insoshi running on Ubuntu 8.04 / Apache 2.2 /
>>> > > Thin 0.82 / MySQL 5.0
>>> >
>>> > > After going through all the git instructions, installing all the
>>> gems,
>>> > > and doing the rake spec with zero errors, I get the Insoshi's 500
>>> > > error instead of the homepage from the insoshi/public/500.html when I
>>> > > go directly to the domain name (with or without www.)
>>> >
>>> > > Apache is up since other domains hosted there give me index.html's
>>> > > from their proper folders.
>>> >
>>> > > thin config is as follows:
>>> >
>>> > > cat /etc/thin/DOMAINNAME.yml
>>> > > ---
>>> > > pid: tmp/pids/thin.pid
>>> > > log: log/thin.log
>>> > > timeout: 30
>>> > > port: 5000
>>> > > max_conns: 1024
>>> > > chdir: /var/www/DOMAINNAME.com/rails/insoshi
>>> > > max_persistent_conns: 512
>>> > > environment: production
>>> > > address: 0.0.0.0
>>> > > daemonize: true
>>> > > servers: 3
>>> >
>>> > > What could be wrong? the site as you can see is in /var/www/
>>> > > DOMAINNAME.com.com/rails/insoshi
>>> >
>>> > > Was I supposed to change permissions to something via CHMOD? I know
>>> > > that when I ran rake and all the other commands, I had to do SUDO in
>>> > > front of each command in order for pretty much every one of your
>>> > > install steps to work properly.
>>> >
>>> > > Please let me know (or let me know if you need more information) ! I
>>> > > am a fan of yours ever since your railspace teaching video...
>>> >
>>> > > Victor- Hide quoted text -
>>> >
>>> > - Show quoted text -
>>> >>>
>>>
>>
>

--~--~---------~--~----~------------~-------~--~----~
Insoshi developer site: http://dogfood.insoshi.com/
Insoshi documentation: http://docs.insoshi.com/

You received this message because you are subscribed to the Google
Groups "Insoshi" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/insoshi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to