Ruby on Rails

> On Jun 29, 2018, at 11:17 PM, Frederick Cheung <frederick.cheung@gmail.com> wrote:
>
> On Thursday, June 28, 2018 at 2:13:31 AM UTC+1, Phil wrote:
>> This is odd... I have a few models that after some time just start doing SELECT "my_tablemy_belongs_to_table".* sort of thing. (Almost like it is trying to reference a join table, but missing a _ between the table names.)
>>
>> In other words, things work for hours, days or weeks then suddenly goes from SELECT "my_table".* to SELECT "my_tablemy_belongs_to_table".*
>
> There are a few activerecord settings (table_name, table_name_prefix maybe some others) that could do this. Might these be getting changed by accident (perhaps because your model has a method whose name clashes with an active record method) ?
>
> Fred
>
>>
>> The associated FROM clause also changes to match. Hundreds of exceptions per minute then ensue and all heck breaks loose. ;')
>>
>> I perhaps am running into a namespace issue or something(?)... how does a model get triggered into changing it's associated table name in runtime? Our temp fix it to just restart the service/app but that's obviously not sustainable. We had to do it several times today.
>>
>> Thoughts?
>>
>> ruby 2.5.0p21 (2018-02-18 revision 62472) [x86_64-linux]
>> rails 5.1.6
>> pg 1.0.0
>>
>> Thanks!
>>
>>
>> Phil

Thank you Fred and Colin.

Somehow table_name seems to be getting set to something else... I can simulate how it breaks but I don't know where/why it is breaking in the production code...

>> UserAccount.table_name = "blah"
=> "blah"
>> UserAccount.first
Traceback (most recent call last):
1: from (irb):2
ActiveRecord::StatementInvalid (PG::UndefinedTable: ERROR: relation "blah" does not exist
LINE 1: SELECT "blah".* FROM "blah" ORDER BY "blah"."id" ASC LIMIT ...
^
: SELECT "blah".* FROM "blah" ORDER BY "blah"."id" ASC LIMIT $1)


Something in Rails 5.1.x is appending to 'table_name' in the model during some condition?

I can't easily reproduce. I don't see anywhere in the code where I'm operating on table_name directly.

(still digging, I hope everyone is having a good Saturday, btw :')


Phil

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/066091BE-E396-4E3A-BDDC-DE0DECD24476%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

On Fri, Jun 29, 2018 at 5:16 PM, 'Ayari HoussemEddine' via Ruby on
Rails: Talk <rubyonrails-talk@googlegroups.com> wrote:

> I've installed Redmine and Ruby but when i am trying to install rails i had
> a problem anyone can help me plzz ???

http://www.catb.org/esr/faqs/smart-questions.html

--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yCsDEQTjLeNQy7PDrxn%3DB_R1L%2BmY2YRH4MJtByw-S8JLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

On 30 June 2018 at 01:16, 'Ayari HoussemEddine' via Ruby on Rails:
Talk <rubyonrails-talk@googlegroups.com> wrote:
> Hello i am working in my final graduation project.
> I need to install Redmine which is developped bu ROR plateforme.
> I've installed Redmine and Ruby but when i am trying to install rails i had
> a problem anyone can help me plzz ???

You might be better on a Redmine forum rather than here.

Colin

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLueRzSNDi0rn4P%3DKxVsM0bSY4mxVNd-PbtpPdNer-rhUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

On Thursday, June 28, 2018 at 2:13:31 AM UTC+1, Phil wrote:
> This is odd... I have a few models that after some time just start doing SELECT "my_tablemy_belongs_to_table".* sort of thing. (Almost like it is trying to reference a join table, but missing a _ between the table names.)
>
> In other words, things work for hours, days or weeks then suddenly goes from SELECT "my_table".* to SELECT "my_tablemy_belongs_to_table".*

There are a few activerecord settings (table_name, table_name_prefix maybe some others) that could do this. Might these be getting changed by accident (perhaps because your model has a method whose name clashes with an active record method) ?

Fred

>
> The associated FROM clause also changes to match. Hundreds of exceptions per minute then ensue and all heck breaks loose. ;')
>
> I perhaps am running into a namespace issue or something(?)... how does a model get triggered into changing it's associated table name in runtime? Our temp fix it to just restart the service/app but that's obviously not sustainable. We had to do it several times today.
>
> Thoughts?
>
> ruby 2.5.0p21 (2018-02-18 revision 62472) [x86_64-linux]
> rails 5.1.6
> pg 1.0.0
>
> Thanks!
>
>
> Phil

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/1ba53edc-d9c8-47e0-9811-5834b20548f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

On 28 June 2018 at 21:49, Julian Medina <julian.l.medina@gmail.com> wrote:
> Thanks! So essentially I could have a separate button for volume purchases which would bring up a different view? Would I then have a loop in my controller that would create records for each person who is getting certified?

Since you haven't quoted the previous message we don't know who this
is addressed to. Assuming it was my suggestion that you could have a
different action in the same controller then presumably yes, that is
what you would do. Of course the code can get tricky as you may have
to allow for problems saving the record for each one (caused by
validation errors) and work out how to handle that.

Colin

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLv%2BdMrVKXV7kz%2B47izzQTe859HnSs%3D7jZu259jNDAZWLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

On 28 June 2018 at 21:51, Julian Medina <julian.l.medina@gmail.com> wrote:
> This is an interesting approach. Thanks! Would I essentially just duplicate my current controller but add a loop within the volume controller so that records are created based on the number of individuals getting certified? I am assuming I'd need two separate views as well.

Obviously you need a view to show your form. You shouldn't have to
duplicate any actions from the current controller as presumably this
controller will only have the one action in it - showing the form,
adding the records, and handling any errors.

Colin

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLtoJPcssx4bH1VDDDb6uydBjQ6NS6SYA38G9aW2KamtSQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

This is an interesting approach. Thanks! Would I essentially just duplicate my current controller but add a loop within the volume controller so that records are created based on the number of individuals getting certified? I am assuming I'd need two separate views as well.

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/124e670c-0f53-4115-a636-d4c3367f0c1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thanks! So essentially I could have a separate button for volume purchases which would bring up a different view? Would I then have a loop in my controller that would create records for each person who is getting certified?

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/60b35430-aa5f-437c-ae32-b675052d893c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Also, if you wanted to stick to the REST actions in your controllers, you could have a separate controller (with no additional model): think TutorsController and MultipleTutorsController or something like that. Rails conditions you to think that a controller must be unique to its model, but controllers don't even need models if that's not what they are doing, and multiple controllers can help refine your routing around a single model -- think a ContentsController and an AdminContentsController, with the same Content model.

Walter

> On Jun 28, 2018, at 3:17 AM, Colin Law <clanlaw@gmail.com> wrote:
>
> On 28 June 2018 at 05:37, Julian Medina <julian.l.medina@gmail.com> wrote:
>> Hello:
>>
>> I have an interesting yet somewhat strange task. Currently, there is a form
>> in my app which adds just single record for certifying tutors. The group
>> wants a way for volume purchasing where a coordinator can login and add
>> multiple tutors in one form. I was considering a nested form or form object
>> but since the certificate actually follows the individual instead of
>> coordinator, I am now thinking it is best if multiple records under the
>> "Certifcation" model get created under a single form. I really don't see why
>> I'd need an entirely separate model for this. Would I need to implement a
>> "hacky" solution for this?
>
> Remember you can have multiple actions on a controller which bring up
> different forms. So you can have a separate action that brings up the
> multi-record form.
>
> Colin
>
> --
> 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 rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLtz4W9oRvtUiKkdx8cMPnV1zqLN%3DpkOgUMQveTbY4JZYw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/6CF88F4E-158B-4D45-8A81-F2EC8EBA5161%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.

On 28 June 2018 at 05:37, Julian Medina <julian.l.medina@gmail.com> wrote:
> Hello:
>
> I have an interesting yet somewhat strange task. Currently, there is a form
> in my app which adds just single record for certifying tutors. The group
> wants a way for volume purchasing where a coordinator can login and add
> multiple tutors in one form. I was considering a nested form or form object
> but since the certificate actually follows the individual instead of
> coordinator, I am now thinking it is best if multiple records under the
> "Certifcation" model get created under a single form. I really don't see why
> I'd need an entirely separate model for this. Would I need to implement a
> "hacky" solution for this?

Remember you can have multiple actions on a controller which bring up
different forms. So you can have a separate action that brings up the
multi-record form.

Colin

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLtz4W9oRvtUiKkdx8cMPnV1zqLN%3DpkOgUMQveTbY4JZYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

On 28 June 2018 at 02:13, Phil Edelbrock <edelbrp@gmail.com> wrote:
>
> This is odd... I have a few models that after some time just start doing SELECT "my_tablemy_belongs_to_table".* sort of thing. (Almost like it is trying to reference a join table, but missing a _ between the table names.)

Is there nothing unusual in the log just before it happens the first
time? Also look in the system/server logs to see if anything happened
there.

Colin

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLsmZz8YFoe9Qh%2BUYJWWOVBV_j%3DaKvuioS3_CJrrarTu1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

This could be off topic, but there was this excellent thing
called Ferro https://easydatawarehousing.github.io/ferro/ , now
its not maintained I think.

Hassan Schroeder <hassan.schroeder@gmail.com> wrote:
> On Wed, Jun 27, 2018 at 3:10 AM, David Gautier
> <kriomx@gmail.com> wrote:
>
> > I am a full-stack developer, that can explain why I think ERB templates are
> > useless.
>
> So am I, so that doesn't really "explain" it :-)
>
> Also, given the ubiquity of templating systems in basically
> every language used for web dev, it seems like there are more
> use cases than not...
>
> > If I'm asking myself, "for who do we write ERB templates with HTML? Who will
> > read the code ?"
> > I can answer "me ... the team ...So it does not matter, we understand Ruby"
>
> As always, TMTOWTDI...
>

- --
- - Karthikeyan A K

Sent using Mailpile, Free Software from www.mailpile.is

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE19aIrDNxkBJVboERznHPBBVO1PMFAls0de0ACgkQznHPBBVO
1PP9mA//QdCsKhoUsFK9Vh3z5YcCEdZzqNpZoBpCB1uJz9V51eU4CNVxQg3i2UO3
rhlVRbBuKmU+RmVIrSUULpyBxFdA04N8MgxFnkfzJ8iCZiwzolzmXTam3fL/1NbN
yYVuiSmNr12lYXFHd2xvaE008QRAiFjFIl1plGd09FwAVMkwnim5DbeSWYZMvc8P
HCO8L1kO+x94TDWM75FJmTdtGUk1bfZeOs6rPLsmtTkEWSB8wxFLwn9eFTyhy7Hy
2xQEDt6ZZG34JMtZkDsBQo5YpiwMYDvHfVenO8GDkbzekldUViXTUR1E+5V00KFY
bvhEost5dBnSIDTfgSdwWD+nCs4FMPWaOWa3O3Ic6JvP6vUeThsVD7gHGMkykiJo
mhjclqEUnebfRgOTarBGtKGGIuKJOOuDddgxySkNfyULFYc0+fgk4Y8gRgCyP8Cm
xfoM1cgO1M9LXs6DaffRL7TO1aBSUH0ZQG/OY3of1fOmEoN3SC1B12l2KCZDvx4o
4w3TLSluZdMWewX4Pf7djJsTZPlyNBZ9cXQT+2znCYT86dPt9jqACcZKmnAzcPbd
ivOJFvbNCaqVe1uf6c/a8jFD+zoEYjrblgMMYTirb0VXzMAj8BqtRVW1EZ7eqN1f
IpA5K1XBdaRIUyUsk1A6MDU24hmphgFFU0mZFdRBuN5tutFlkyw=
=9FoE
-----END PGP SIGNATURE-----

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/vJkjQLQbHhCaGQzwLk3gpBBbmwIzvmfYcJWPDDva2297%40mailpile.
For more options, visit https://groups.google.com/d/optout.

This is odd... I have a few models that after some time just start doing SELECT "my_tablemy_belongs_to_table".* sort of thing. (Almost like it is trying to reference a join table, but missing a _ between the table names.)

In other words, things work for hours, days or weeks then suddenly goes from SELECT "my_table".* to SELECT "my_tablemy_belongs_to_table".*

The associated FROM clause also changes to match. Hundreds of exceptions per minute then ensue and all heck breaks loose. ;')

I perhaps am running into a namespace issue or something(?)... how does a model get triggered into changing it's associated table name in runtime? Our temp fix it to just restart the service/app but that's obviously not sustainable. We had to do it several times today.

Thoughts?

ruby 2.5.0p21 (2018-02-18 revision 62472) [x86_64-linux]
rails 5.1.6
pg 1.0.0

Thanks!


Phil

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/06C283DC-D65C-4F5D-AD30-2D620B48242F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

On Wed, Jun 27, 2018 at 3:10 AM, David Gautier <kriomx@gmail.com> wrote:

> I am a full-stack developer, that can explain why I think ERB templates are
> useless.

So am I, so that doesn't really "explain" it :-)

Also, given the ubiquity of templating systems in basically every
language used for web dev, it seems like there are more use cases
than not...

> If I'm asking myself, "for who do we write ERB templates with HTML? Who will
> read the code ?"
> I can answer "me ... the team ...So it does not matter, we understand Ruby"

As always, TMTOWTDI...

--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yAM_R8EJ4BSnWn%2B4MDMZw5fvMjuVzqT9smoryUMEJessw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

On Wed, Jun 27, 2018 at 5:50 AM, Stephanie_Snowflake
<spicychemist@gmail.com> wrote:
> I don't even have Rails 2.2.3 on my Mac!

That makes utterly no sense. You previously said you could run the
app, including tests, in its original form.

>> So I need to start over from the original project directory! Like
>> uninstall rails.

Upgrading a project like this is much easier if you're using a version
manager like rvm to maintain separate gemsets for the stages of the
upgrade.

Regardless, you need to get back to the original *working with tests*
starting point and upgrade a step at a time. In particular pay attention
to the deprecation warnings *and fix them* before moving on.

Good luck.
--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yCbCPugZJb%2BJrb%3DSuw3Zmvj4%3DZjGvsawjaLdrxsxwYy2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

In my experience, Stripe is the easiest. Particularly for recurring (subscription) payment. There's a great example app at the RailsApps site: https://github.com/RailsApps/rails-stripe-membership-saas if you want to do recurring billing. For single payment, it's even simpler than that.

Walter

> On Jun 26, 2018, at 5:51 PM, David Merrick <merrickdav@gmail.com> wrote:
>
> Hi Looking for a payment gateway that is easy to set up in Rails. The idea is that as part of the Registration Process a user pay money to gain access to restricted pages.
>
> I will at Stripe https://stripe.com/nz but if any one can suggest a simpler one feel free to do so.
>
> Cheers Dave
>
> --
> 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 rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a99450a6-bc91-4e9e-85d5-94a4b4f07a4c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/F255BA99-EEB3-4E63-80F3-A790EDF8A5A2%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.

Wow. That's quite a lot of RAM to be starved like that. I've been running four moderately-traffic'd Rails apps, along with a smattering of PHP apps, on one "droplet" with (I had to go look at the control panel) 1GB RAM and 30GB SSD. It's been up and running for four years. There's a Rails 3.2 app, a Rails 4.0 app, a Rails 4.2 app, and a Rails 5.1 app. There's also two major PHP apps that get a lot of love from mostly spammers, and one minor one that never gets any traffic. I'm not holding this up as a bastion of good devops, but just to give you the counterpoint that your server is probably not your problem.

What application server are you using, and which database? I'm on Passenger (mod_passenger compiled into Apache), using MySQL.

Walter

> On Jun 27, 2018, at 8:35 AM, tom <tomabroad@gmail.com> wrote:
>
> hi,
> i was wondering what a typical setup for a small web app is.
>
> my challenge currently is that my server kills some processes because im out of memory.
>
> i am running ruby 2.3, nginx, passenger, mta, sidekick.
>
> i have 4gb ram and i am on digital ocean. i have barely any traffic on the site.
>
> what "should" that server be handle?
> what does your configuration look like? care to share configs?
>
> thx
>
> --
> 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 rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CADQqhMfHstCNvt65wFQzDy-fptU3aDM3YAkjj24LV6pfpFCoEg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/244C3A27-3A02-4C6F-8DF8-3D3B767D0B77%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.

On 27 June 2018 at 13:50, Stephanie_Snowflake <spicychemist@gmail.com> wrote:
> I don't even have Rails 2.2.3 on my Mac!

I am not surprised, it has been obsolete for ten years.

Colin

>
> On Wednesday, June 27, 2018 at 7:35:53 AM UTC-5, Stephanie_Snowflake wrote:
>>
>> So I need to start over from the original project directory! Like
>> uninstall rails.
>>
>> On Tuesday, June 26, 2018 at 4:16:03 PM UTC-5, Colin Law wrote:
>>>
>>> On 26 June 2018 at 22:04, Stephanie_Snowflake <spicyc...@gmail.com>
>>> wrote:
>>> > when I received the project it had Ruby 2.2.3, Rails 2.2.3, bundler
>>> > 1.16.2
>>>
>>> You can't just upgrade Rails from 2.2.3 (which is ten years old) to
>>> Rails 5 by updating the gems. Rails is now vastly different to what
>>> it was then. This link gives details of how to upgrade if you can get
>>> it going with rails 3.
>>> http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html
>>>
>>> Colin
>
> --
> 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 rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-talk/6c25af25-1848-4694-a80c-75698aae3d9b%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLv%3DgGQviQXs7jaX7Tojcp740XY93Cr8ityAZO4-URvkUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

On 27 June 2018 at 13:35, Stephanie_Snowflake <spicychemist@gmail.com> wrote:
> So I need to start over from the original project directory! Like uninstall
> rails.

In fact I think from the questions that you have asked that you have
very little experience with Rails. In that case I suggest that you
start by working right through a good tutorial such as
railstutorial.org, which is free to use online. Then you should
understand the basics of Rails. The reason I say this is that
upgrading a Rails app which is not even one you developed yourself can
be quite tricky. Particularly upgrading over so many versions of
Rails. Depending on the size of the app it may even be quicker to
start from scratch. Whichever route you choose a few days spent on
the tutorial will be repaid with interest when you get back to the
job.

Colin

>
> On Tuesday, June 26, 2018 at 4:16:03 PM UTC-5, Colin Law wrote:
>>
>> On 26 June 2018 at 22:04, Stephanie_Snowflake <spicyc...@gmail.com> wrote:
>> > when I received the project it had Ruby 2.2.3, Rails 2.2.3, bundler
>> > 1.16.2
>>
>> You can't just upgrade Rails from 2.2.3 (which is ten years old) to
>> Rails 5 by updating the gems. Rails is now vastly different to what
>> it was then. This link gives details of how to upgrade if you can get
>> it going with rails 3.
>> http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html
>>
>> Colin
>
> --
> 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 rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-talk/bb70519c-79ae-4a7c-9d59-34d40add5268%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

--
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 rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLv1vZvRmsoDGRqPwN8WxtFirW1FdWnopd6EFxpN49ZrCQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.