LOL, definitely not :-]
On Apr 19, 7:27 am, Walter Lee Davis wrote:
> On Apr 19, 2012, at 2:32 AM, Kal wrote:
>
>
>
>
>
>
>
>
>
> > Hi Walter,
>
> > So, I finally got everything working here (with database and all).
>
> > 1) I definitely had to create a new user 'app_user', add it to the
> > sudo
On Apr 19, 2012, at 2:32 AM, Kal wrote:
> Hi Walter,
>
> So, I finally got everything working here (with database and all).
>
> 1) I definitely had to create a new user 'app_user', add it to the
> sudoer file, and apply 'chown - R app_user /home/rubys/work/depot'.
>
> 2) I wasn't able to issue
Hi Walter,
So, I finally got everything working here (with database and all).
1) I definitely had to create a new user 'app_user', add it to the
sudoer file, and apply 'chown - R app_user /home/rubys/work/depot'.
2) I wasn't able to issue "RAILS_ENV=production bundle exec rake
assets:precompile"
Thanks for the suggestion Raels :)
Although, this doesn't seem to be the culprit :(
~Kal
On Apr 13, 10:36 am, Raels Koder wrote:
> I get the same error. I am also using passenger, although I don't
> always use it. I am also using RVM.
>
> I noticed an error that popped up in my email from rak
Hi Walter,
They look correct... (from httpd.conf)
LoadModule passenger_module /usr/local/lib/ruby/gems/1.9.1/gems/
passenger-3.0.11/ext/apache2/mod_passenger.so
PassengerRoot /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.11
PassengerRuby /usr/local/bin/ruby
-
On Apr 13, 2012, at 10:36 AM, Raels Koder wrote:
> I get the same error. I am also using passenger, although I don't
> always use it. I am also using RVM.
>
> I noticed an error that popped up in my email from rake (I am working on
> a Mac) that showed an error from rake 1.8.X something or o
I get the same error. I am also using passenger, although I don't
always use it. I am also using RVM.
I noticed an error that popped up in my email from rake (I am working on
a Mac) that showed an error from rake 1.8.X something or other, instead
of the rake from 1.9.2 that I am running. I s
Hi Walter,
I was wrong; creating a new user 'app_user', adding it to the sudoer
file, and then applying 'chown - R app_user /home/rubys/work/depot'
did work.
I was just reading too deep into Cowboy's (http://www.cowboycoded.com/
tag/passenger/) instructions, which didn't pertain to my setup
(spec
Hi Walter,
That didn't seem to work...
This is getting more and more confusing to the point where I don't
know if I'm coming or going...
Mostly, this is because the Ruby on Rails stack involves so many
items, I'm not sure where it's broken.
I'm getting closer (or maybe not). I'll post my findi
On Apr 2, 2012, at 10:15 PM, Kal wrote:
> Hi Walter,
>
> Very sorry for the confusion.
>
> When I mention server, I'm actually referring to the box, not a
> service(s).
>
> I'm actually running everything from a virtual dedicated server
> (through GoDaddy.com).
>
> I'm not testing any of the
Hi Walter,
Very sorry for the confusion.
When I mention server, I'm actually referring to the box, not a
service(s).
I'm actually running everything from a virtual dedicated server
(through GoDaddy.com).
I'm not testing any of the aforementioned items on a desktop nor am I
deploying to Apache v
On Apr 2, 2012, at 8:39 PM, Kal wrote:
> Hi Walter,
>
> Again, my apologies for the delay in reply. I'm more confused now
> than before, so it took some time to poke around.
>
> Firstly, I don't run a separate development and production server.
> Does that matter?
If you start rails with rail
Hi L,
therubyracer (0.9.9) is already installed :(
Thanks Anyway :)
~Kal
On Mar 31, 7:51 am, "Firstname L." wrote:
> Ok this might sound funny but , this problem is usually caused by lack
> of javascript libraries in your rails setup so i would recommend you to
> do this .
>
> Install this ge
Typo: product listing are NOT displayed :(
On Apr 2, 8:39 pm, Kal wrote:
> Hi Walter,
>
> Again, my apologies for the delay in reply. I'm more confused now
> than before, so it took some time to poke around.
>
> Firstly, I don't run a separate development and production server.
> Does that matte
Hi Walter,
Again, my apologies for the delay in reply. I'm more confused now
than before, so it took some time to poke around.
Firstly, I don't run a separate development and production server.
Does that matter?
Installed are rake (0.9.2.2) and bundler (1.0.21). I have not run
bundle install o
My apologies Walter, et al.
I haven't had access to my computers within the last 24 hrs. I shall
look into your recommendations tonight.
As always, thank you for your assistance and prompt replies.
~Kal
On Mar 30, 9:26 am, Walter Lee Davis wrote:
> On Mar 30, 2012, at 12:34 AM, Kal wrote:
>
On Mar 30, 2012, at 12:34 AM, Kal wrote:
> Hi Walter,
>
> I did as instructed but now getting a "rake aborted! stack level too
> deep (in /home/rubys/work/depot/app/assets/stylesheets/
> scaffolds.css.scss)" error.
>
> I tried to modify "config.assets.compile = true: (from false) within
> confi
Hi Walter,
I did as instructed but now getting a "rake aborted! stack level too
deep (in /home/rubys/work/depot/app/assets/stylesheets/
scaffolds.css.scss)" error.
I tried to modify "config.assets.compile = true: (from false) within
config/environments/production.rb but still no good :(
Thanks A
Hi Walter,
I did as instructed but now getting a "rake aborted! stack level too
deep" error (in /home/rubys/work/depot/app/assets/stylesheets/
scaffolds.css.scss).
I also tried modified "config.assets.compile = true" (from false)
within config/environments/production.rb but still no good :(
Than
On Mar 29, 2012, at 10:51 PM, Kal wrote:
> (Re-posting)
>
> Thanks Walter,
>
> I think you are correct. I had neglected to set up a production
> version of the database.
>
> I just ran "rake db:migrate RAILS_ENV=production". However, I now get
> a "500 Internal Server Error".
>
> Anyway, he
(Re-posting)
Thanks Walter,
I think you are correct. I had neglected to set up a production
version of the database.
I just ran "rake db:migrate RAILS_ENV=production". However, I now get
a "500 Internal Server Error".
Anyway, here is the error from production.log. Any ideas?
Thanks,
Kal
-
Hi Leonardo,
Per my reply to Walter, I just ran "rake db:migrate
RAILS_ENV=production". However, I now get a "500 Internal Server
Error".
Below is my config/database.yml file and these are the permissions to
the db/production.sqlite3 file.
-rw-r--r-- 1 root root 5120 Mar 29 20:45 production.sq
22 matches
Mail list logo
