Thanks for the help everybody. I wasn't able to fix the file, but I
just ended up deleting the entire place file and will try to start over
and protect it under active admin again.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the
Hi,
Have you try deleting the Gemfile.lock and then run bundle install and
then finally rails s.. hope this will help you..
:)
On Monday, 14 July 2014 03:34:39 UTC+5:30, Ruby-Forum.com User wrote:
I made a mistake last time and shut down my RoR project without pushing
to git or
On 14 July 2014 13:14, Rasool SB rasool...@gmail.com wrote:
Hi,
Have you try deleting the Gemfile.lock and then run bundle install and
then finally rails s.. hope this will help you..
Why delete Gemfile.lock when the system was previously working?
Gemfile.lock is what ensures the same
Thanks for the help Rasool, Colin and Hassan.
1. I get this error whenever I start rails server - nothing will
connect to local host to show me errors/the site.
a. This means I can't run rake routes - my rake commands are always
aborted and I get the same error message pasted above. I
On Mon, Jul 14, 2014 at 8:19 AM, Fatima Fatima li...@ruby-forum.com wrote:
1. I get this error whenever I start rails server - nothing will
connect to local host to show me errors/the site.
Irrelevant - the error messages are in your console/logs.
a. This means I can't run rake routes
Gemfile.lock is a list of gems used to ensure that all copies of the app
use the same gem versions
*, *When ever we accidentally shutdown, Rails or Ruby files( temporary
files) like /tmp/pids/server.pid and or Gemfile.lock caches logs to
interact with some methods, classes etc., due to
On Mon, Jul 14, 2014 at 9:06 AM, Rasool SB rasool...@gmail.com wrote:
When ever we accidentally shutdown, Rails or Ruby files( temporary
files) like /tmp/pids/server.pid and or Gemfile.lock caches logs to
interact with some methods, classes etc., due to sudden close of the
application
Thanks for the suggestions all. I'm going to play around using the
feedback and let you know what I come to.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Talk group.
To unsubscribe from this group and
Hassan is right. I doubt the problem is with your Gemfile.lock so I suggest
starting elsewhere and leaving it alone.
The best thing would be to stash your changes using git and going back to a
working version of the application. Go back to the last version that worked
and see what's different.
Thanks Eric - will try that!
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Talk group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
You should check the file mentioned in the first line of stacktrace or show it
to us
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Talk group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
11 matches
Mail list logo
