visit my blog at http://jimlabs.herokuapp.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 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/CAJ8y7Vd7OO_nMpOqt9_0br%3Dor0-FSHYi0a95ivCOkfqqHfrGNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Hi--I got error xmlrpc-0.3.0 requires ruby version >= 2.3 when i deploy to heroku . what should I do ?Thank you
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/ae91d3a6-4bd9-41b9-8741-2322b52caf44%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/CAPmpWecq84jhacjeU5DL1MYxAixsg6cJdHntKnGaaRcK9mpPZw%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/ae91d3a6-4bd9-41b9-8741-2322b52caf44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
oh, right. Just to do some minor things, but with pgadmin you have to write a bunch of sql.
On Friday, April 28, 2017 at 9:18:54 AM UTC-4, Colin Law wrote:On 28 April 2017 at 14:15, Joe Guerra <JGu...@jginfosys.com> wrote:
> Got it working. I was just using the default settings that ror. It's much
> easier to deal with sqlite in development. I hate using PGAdmin for
> postgres.
Why do you have to use pgadmin? You should very rarely have to go
direct to the database.
Colin
>
> Thanks,
> Joe
>
> On Thursday, April 27, 2017 at 7:30:10 PM UTC-4, jim wrote:
>>
>>
>>
>> On Fri, Apr 28, 2017 at 9:17 AM, Joe Guerra <JGu...@jginfosys.com> wrote:
>>>
>>> ok, I'm having difficulty with heroku, they are having some build
>>> problems...
>>>
>>> I'll try later. I guess commenting out the # rename table in change def
>>> should work?
>>>
>>> I was puzzled because the column title started with a capital letter, it
>>> worked fine in sqlite, but generated errors in postgres. (so the quickest
>>> fix for me was to edit the column in postgress directly). I belive I
>>> skipped this migration before, but I forget how I did that.
>>
>>
>> is there anything that keeps you from using postgres for development?
>>
>>>
>>>
>>> Thanks,
>>> Joe
>>>
>>> On Thursday, April 27, 2017 at 7:02:48 PM UTC-4, jim wrote:
>>>>
>>>>
>>>>
>>>> On Fri, Apr 28, 2017 at 8:54 AM, Joe Guerra <JGu...@jginfosys.com>
>>>> wrote:
>>>>>
>>>>> Hi, I got stuck on a migration (basically to fix a column name). I
>>>>> actually went into the table itself and corrected the problem. My herkou
>>>>> migration gets stuck, and I've got other migrations behind it that aren't
>>>>> running.
>>>>
>>>>
>>>> If you've already fixed the table manually, then you don't need to run
>>>> the migration at all. You have 3 hackish options
>>>>
>>>> 1. Just delete the migration and update the old migration so it uses
>>>> the correct column name.
>>>> 2. Insert the timestamp of the migration that you want to skip to a
>>>> table called schema_migrations (not sure if this is
>>>> the exact name). Rails basically checks this table to see which
>>>> migrations need to run.
>>>> 3. Edit the migration so that it doesn't do anything, commit, deploy,
>>>> run db:migrate. Edit the migration again, commit,
>>>> deploy, run db:migrate. The second db:migrate should not run the edited
>>>> migration file.
>>>>
>>>> May I ask why you decided to fix the table manually?
>>>>
>>>>>
>>>>> What should I do?
>>>>>
>>>>> Thanks,
>>>>> Joe
>>>>>
>>>>> --
>>>>> 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-ta...@googlegroups.com .
>>>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/rubyonrails-talk/9567374e- .3003-4dde-8e3c-cf6c834247e4% 40googlegroups.com
>>>>> For more options, visit https://groups.google.com/d/optout .
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> ------------------------------------------------------------ -
>>>> visit my blog at http://jimlabs.herokuapp.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 rubyonrails-ta...@googlegroups.com .
>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/rubyonrails-talk/f4266b4f- .c569-4820-891f-2e7ba8a89126% 40googlegroups.com
>>>
>>> For more options, visit https://groups.google.com/d/optout .
>>
>>
>>
>>
>> --
>> ------------------------------------------------------------ -
>> visit my blog at http://jimlabs.herokuapp.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 rubyonrails-ta...@googlegroups.com .
> To post to this group, send email to rubyonra...@googlegroups.com.
> To view this discussion on the web visit--To view this discussion on the web visit https://groups.google.com/d/
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 .msgid/rubyonrails-talk/ .0bcd9ba2-e6ca-47e0-bfc9- 779d222ab336%40googlegroups. 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 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%3D0gLvrEinZOh9U6eYcoh2VwMOEEz%3DdaiO3ksfmWnkr7ULdUw%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/d9b8a12d-9e27-4b06-99b0-a03069fda895%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Thursday, April 20, 2017 at 9:52:54 AM UTC-4, sadathiru wrote:
Hello,
I've a team of ROR developers who are ready to engage in delivering.We've experienced with different flavor of technologies other than ROR like python, java, perl, javascript, git, JSON, REST, SOAP, bash, RDBMS, linux commands and few others.
We've also rich experience of working in different domains in ROR development like telecom, inventory, ecommerce, payments/cards, etc..Looking for the right opportunity to work out of remote location.
Thanks in advance!
sadathiru
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/b104ac08-23a9-4f32-9a9c-713b38f1c0f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Friday, April 28, 2017 at 9:18:54 AM UTC-4, Colin Law wrote:
On 28 April 2017 at 14:15, Joe Guerra <JGu...@jginfosys.com> wrote:
> Got it working. I was just using the default settings that ror. It's much
> easier to deal with sqlite in development. I hate using PGAdmin for
> postgres.
Why do you have to use pgadmin? You should very rarely have to go
direct to the database.
Colin
>
> Thanks,
> Joe
>
> On Thursday, April 27, 2017 at 7:30:10 PM UTC-4, jim wrote:
>>
>>
>>
>> On Fri, Apr 28, 2017 at 9:17 AM, Joe Guerra <JGu...@jginfosys.com> wrote:
>>>
>>> ok, I'm having difficulty with heroku, they are having some build
>>> problems...
>>>
>>> I'll try later. I guess commenting out the # rename table in change def
>>> should work?
>>>
>>> I was puzzled because the column title started with a capital letter, it
>>> worked fine in sqlite, but generated errors in postgres. (so the quickest
>>> fix for me was to edit the column in postgress directly). I belive I
>>> skipped this migration before, but I forget how I did that.
>>
>>
>> is there anything that keeps you from using postgres for development?
>>
>>>
>>>
>>> Thanks,
>>> Joe
>>>
>>> On Thursday, April 27, 2017 at 7:02:48 PM UTC-4, jim wrote:
>>>>
>>>>
>>>>
>>>> On Fri, Apr 28, 2017 at 8:54 AM, Joe Guerra <JGu...@jginfosys.com>
>>>> wrote:
>>>>>
>>>>> Hi, I got stuck on a migration (basically to fix a column name). I
>>>>> actually went into the table itself and corrected the problem. My herkou
>>>>> migration gets stuck, and I've got other migrations behind it that aren't
>>>>> running.
>>>>
>>>>
>>>> If you've already fixed the table manually, then you don't need to run
>>>> the migration at all. You have 3 hackish options
>>>>
>>>> 1. Just delete the migration and update the old migration so it uses
>>>> the correct column name.
>>>> 2. Insert the timestamp of the migration that you want to skip to a
>>>> table called schema_migrations (not sure if this is
>>>> the exact name). Rails basically checks this table to see which
>>>> migrations need to run.
>>>> 3. Edit the migration so that it doesn't do anything, commit, deploy,
>>>> run db:migrate. Edit the migration again, commit,
>>>> deploy, run db:migrate. The second db:migrate should not run the edited
>>>> migration file.
>>>>
>>>> May I ask why you decided to fix the table manually?
>>>>
>>>>>
>>>>> What should I do?
>>>>>
>>>>> Thanks,
>>>>> Joe
>>>>>
>>>>> --
>>>>> 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-ta...@googlegroups.com .
>>>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/rubyonrails-talk/ .9567374e-3003-4dde-8e3c- cf6c834247e4%40googlegroups. com
>>>>> For more options, visit https://groups.google.com/d/optout .
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> ------------------------------------------------------------ -
>>>> visit my blog at http://jimlabs.herokuapp.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 rubyonrails-ta...@googlegroups.com .
>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/rubyonrails-talk/ .f4266b4f-c569-4820-891f- 2e7ba8a89126%40googlegroups. com
>>>
>>> For more options, visit https://groups.google.com/d/optout .
>>
>>
>>
>>
>> --
>> ------------------------------------------------------------ -
>> visit my blog at http://jimlabs.herokuapp.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 rubyonrails-ta...@googlegroups.com .
> To post to this group, send email to rubyonra...@googlegroups.com .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-talk/ .7476074e-9b38-4d0c-8c09- cc8320e689e3%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/0bcd9ba2-e6ca-47e0-bfc9-779d222ab336%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On 28 April 2017 at 14:15, Joe Guerra <JGuerra@jginfosys.com> wrote:
> Got it working. I was just using the default settings that ror. It's much
> easier to deal with sqlite in development. I hate using PGAdmin for
> postgres.
Why do you have to use pgadmin? You should very rarely have to go
direct to the database.
Colin
>
> Thanks,
> Joe
>
> On Thursday, April 27, 2017 at 7:30:10 PM UTC-4, jim wrote:
>>
>>
>>
>> On Fri, Apr 28, 2017 at 9:17 AM, Joe Guerra <JGu...@jginfosys.com> wrote:
>>>
>>> ok, I'm having difficulty with heroku, they are having some build
>>> problems...
>>>
>>> I'll try later. I guess commenting out the # rename table in change def
>>> should work?
>>>
>>> I was puzzled because the column title started with a capital letter, it
>>> worked fine in sqlite, but generated errors in postgres. (so the quickest
>>> fix for me was to edit the column in postgress directly). I belive I
>>> skipped this migration before, but I forget how I did that.
>>
>>
>> is there anything that keeps you from using postgres for development?
>>
>>>
>>>
>>> Thanks,
>>> Joe
>>>
>>> On Thursday, April 27, 2017 at 7:02:48 PM UTC-4, jim wrote:
>>>>
>>>>
>>>>
>>>> On Fri, Apr 28, 2017 at 8:54 AM, Joe Guerra <JGu...@jginfosys.com>
>>>> wrote:
>>>>>
>>>>> Hi, I got stuck on a migration (basically to fix a column name). I
>>>>> actually went into the table itself and corrected the problem. My herkou
>>>>> migration gets stuck, and I've got other migrations behind it that aren't
>>>>> running.
>>>>
>>>>
>>>> If you've already fixed the table manually, then you don't need to run
>>>> the migration at all. You have 3 hackish options
>>>>
>>>> 1. Just delete the migration and update the old migration so it uses
>>>> the correct column name.
>>>> 2. Insert the timestamp of the migration that you want to skip to a
>>>> table called schema_migrations (not sure if this is
>>>> the exact name). Rails basically checks this table to see which
>>>> migrations need to run.
>>>> 3. Edit the migration so that it doesn't do anything, commit, deploy,
>>>> run db:migrate. Edit the migration again, commit,
>>>> deploy, run db:migrate. The second db:migrate should not run the edited
>>>> migration file.
>>>>
>>>> May I ask why you decided to fix the table manually?
>>>>
>>>>>
>>>>> What should I do?
>>>>>
>>>>> Thanks,
>>>>> Joe
>>>>>
>>>>> --
>>>>> 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-ta...@googlegroups.com.
>>>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/rubyonrails-talk/9567374e-3003-4dde-8e3c-cf6c834247e4%40googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -------------------------------------------------------------
>>>> visit my blog at http://jimlabs.herokuapp.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 rubyonrails-ta...@googlegroups.com.
>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/rubyonrails-talk/f4266b4f-c569-4820-891f-2e7ba8a89126%40googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>> --
>> -------------------------------------------------------------
>> visit my blog at http://jimlabs.herokuapp.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 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/7476074e-9b38-4d0c-8c09-cc8320e689e3%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%3D0gLtXz3O3aMMNs%2Bft2WCMEiV0rP-VNot0yNMCJGfb-LjjHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
On Thursday, April 27, 2017 at 7:30:10 PM UTC-4, jim wrote:
On Fri, Apr 28, 2017 at 9:17 AM, Joe Guerra <JGu...@jginfosys.com> wrote:ok, I'm having difficulty with heroku, they are having some build problems...I'll try later. I guess commenting out the # rename table in change def should work?I was puzzled because the column title started with a capital letter, it worked fine in sqlite, but generated errors in postgres. (so the quickest fix for me was to edit the column in postgress directly). I belive I skipped this migration before, but I forget how I did that.is there anything that keeps you from using postgres for development?--Thanks,Joe
On Thursday, April 27, 2017 at 7:02:48 PM UTC-4, jim wrote:On Fri, Apr 28, 2017 at 8:54 AM, Joe Guerra <JGu...@jginfosys.com> wrote:Hi, I got stuck on a migration (basically to fix a column name). I actually went into the table itself and corrected the problem. My herkou migration gets stuck, and I've got other migrations behind it that aren't running.If you've already fixed the table manually, then you don't need to run the migration at all. You have 3 hackish options1. Just delete the migration and update the old migration so it uses the correct column name.2. Insert the timestamp of the migration that you want to skip to a table called schema_migrations (not sure if this isthe exact name). Rails basically checks this table to see which migrations need to run.3. Edit the migration so that it doesn't do anything, commit, deploy, run db:migrate. Edit the migration again, commit,deploy, run db:migrate. The second db:migrate should not run the edited migration file.May I ask why you decided to fix the table manually?--What should I do?Thanks,Joe
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-ta...@googlegroups.com .
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/ .9567374e-3003-4dde-8e3c- cf6c834247e4%40googlegroups. com
For more options, visit https://groups.google.com/d/optout .
-------------------------------------------------------------- -
visit my blog at http://jimlabs.herokuapp.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 rubyonrails-ta...@googlegroups.com .
To post to this group, send email to rubyonra...@googlegroups.com .
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/ .f4266b4f-c569-4820-891f- 2e7ba8a89126%40googlegroups. com -------------------------------------------------------------- -
visit my blog at http://jimlabs.herokuapp.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 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/7476074e-9b38-4d0c-8c09-cc8320e689e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
ok, I'm having difficulty with heroku, they are having some build problems...I'll try later. I guess commenting out the # rename table in change def should work?I was puzzled because the column title started with a capital letter, it worked fine in sqlite, but generated errors in postgres. (so the quickest fix for me was to edit the column in postgress directly). I belive I skipped this migration before, but I forget how I did that.
--Thanks,Joe
On Thursday, April 27, 2017 at 7:02:48 PM UTC-4, jim wrote:On Fri, Apr 28, 2017 at 8:54 AM, Joe Guerra <JGu...@jginfosys.com> wrote:Hi, I got stuck on a migration (basically to fix a column name). I actually went into the table itself and corrected the problem. My herkou migration gets stuck, and I've got other migrations behind it that aren't running.If you've already fixed the table manually, then you don't need to run the migration at all. You have 3 hackish options1. Just delete the migration and update the old migration so it uses the correct column name.2. Insert the timestamp of the migration that you want to skip to a table called schema_migrations (not sure if this isthe exact name). Rails basically checks this table to see which migrations need to run.3. Edit the migration so that it doesn't do anything, commit, deploy, run db:migrate. Edit the migration again, commit,deploy, run db:migrate. The second db:migrate should not run the edited migration file.May I ask why you decided to fix the table manually?--What should I do?Thanks,Joe
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-ta...@googlegroups.com .
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/9567374e- .3003-4dde-8e3c-cf6c834247e4% 40googlegroups.com
For more options, visit https://groups.google.com/d/optout .
-------------------------------------------------------------- -
visit my blog at http://jimlabs.herokuapp.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 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/ .f4266b4f-c569-4820-891f- 2e7ba8a89126%40googlegroups. com
visit my blog at http://jimlabs.herokuapp.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 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/CAJ8y7Vf2uHq_nfSn3U%2Bk5TSwS1VhPVheRabtwgP0WFQ0dFsxaw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
On Thursday, April 27, 2017 at 7:02:48 PM UTC-4, jim wrote:
On Fri, Apr 28, 2017 at 8:54 AM, Joe Guerra <JGu...@jginfosys.com> wrote:Hi, I got stuck on a migration (basically to fix a column name). I actually went into the table itself and corrected the problem. My herkou migration gets stuck, and I've got other migrations behind it that aren't running.If you've already fixed the table manually, then you don't need to run the migration at all. You have 3 hackish options1. Just delete the migration and update the old migration so it uses the correct column name.2. Insert the timestamp of the migration that you want to skip to a table called schema_migrations (not sure if this isthe exact name). Rails basically checks this table to see which migrations need to run.3. Edit the migration so that it doesn't do anything, commit, deploy, run db:migrate. Edit the migration again, commit,deploy, run db:migrate. The second db:migrate should not run the edited migration file.May I ask why you decided to fix the table manually?--What should I do?Thanks,Joe
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-ta...@googlegroups.com .
To post to this group, send email to rubyonra...@googlegroups.com .
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/ .9567374e-3003-4dde-8e3c- cf6c834247e4%40googlegroups. com
For more options, visit https://groups.google.com/d/optout .
-------------------------------------------------------------- -
visit my blog at http://jimlabs.herokuapp.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 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/f4266b4f-c569-4820-891f-2e7ba8a89126%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi, I got stuck on a migration (basically to fix a column name). I actually went into the table itself and corrected the problem. My herkou migration gets stuck, and I've got other migrations behind it that aren't running.
--What should I do?Thanks,Joe
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/ .9567374e-3003-4dde-8e3c- cf6c834247e4%40googlegroups. com
For more options, visit https://groups.google.com/d/optout .
visit my blog at http://jimlabs.herokuapp.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 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/CAJ8y7VcnBcg5PWMxb0y2LtMVqQNuLAgfeOE3L8AKDdoJ4F7LHw%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/CAL37D8FYW58p%3DWLp7mFV5ho8AKSzR7eOrhdSaeA0kk9pPTWosw%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/9567374e-3003-4dde-8e3c-cf6c834247e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Not sure what you meant regarding binary compatibility issues moving to a new version of RHEL. But if you are moving to or upgrading RHEL I'd definitely suggest switching to Nginx/Passenger as Nginx benchmarks much better than Apache does and the passenger integration is much more straight forward than Apache. If you have specific questions, please drop them here.
> On Apr 27, 2017, at 12:15 PM, Robert Nicholson <robert.nicholson@gmail.com> wrote:
>
> We have a Rails application that runs via an old Apache using Passenger on an old release of RedHat Linux.
>
> What are the logical options to avoid binary compatibility issues when moving to a newer RedHat Linux?
>
>
> --
> 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/7AC6CC26-E808-453A-BAC3-EB26AC2A4DE1%40gmail.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/23E61389-2D6A-484E-90C3-E6F8F3C31A11%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
We have a Rails application that runs via an old Apache using Passenger on an old release of RedHat Linux.
What are the logical options to avoid binary compatibility issues when moving to a newer RedHat Linux?
--
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/7AC6CC26-E808-453A-BAC3-EB26AC2A4DE1%40gmail.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/54c1c1d0-02f3-4d12-8b5b-450793ae76b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Senior RUBY ON RAILS DEVELOPER in San Francisco with a well-funded Global mobile technology company backed by Dreamworks Animation and other Top Silicon Valley VC's. The company caters to the kid's entertainment/education arena. Their award winning apps are at the leading and cutting edge in the explosive multi-billion dollar kid's mobile entertainment/educational mobile market. Top pay, great equity, excellent benefits, outstanding Union Square location. HIRING IMMEDIATELY!!!
If there is any interest, please email resume to mat.kanno@nearshoresystems.com
SENIOR SOFTWARE ENGINEER (RUBY ON RAILS)
Engineering | San Francisco, CA | Full Time
JOB DESCRIPTION
Seeking a passionate Senior Software Engineer/Architect to join growing team in San Francisco. Working directly with the VP of IT/Ops, VP of Product, and other key team members, you'll be responsible for designing and creating the critical internal and partner-facing business systems that support our mobile networks around the world. This is an excellent opportunity for the right individual who lives and breathes code and data!
Desired Experience:
• At least (4) years professional experience with web application development and architecture using Ruby on Rails.
• Export knowledge of MVC, OOP, and design patterns.
• Expert in JavaScript and thorough understanding of front-end frameworks (Vue, Angular or React)
• In-depth understanding of RDBMS / SQL (NoSQL/MongoDB a plus)
• Experience with data analytics tools such as MixPanel, Google Analytics, etc.
Other Skills:
• Ability to succeed in a fast-paced, Agile environment
• A consummate collaborator, able to establish strong relationships with technical, product, and business experts
• Accustomed to providing all the options related to achieving the user's objectives
• A champion of quality, able to QA and vouch for the integrity of the report output
• Maintaining business stakeholder engagement and setting expectations
• Assessing current processes and recommending changes as needed
• Documenting and communicating technical specifications to ensure that proper and optimized techniques, queries, data standards, and final deliverables are understood and incorporated into data and analytics processes
• Strong prioritization and time-management skills
• Translate business requirements into specifications that will be used to implement the required user-friendly environments, reports and dashboards, created from potentially multiple data sources
Perks
• Benefits - health, dental, life insurance, vision
• Paid vacation
• Employee stock option program
• Available 401K plan
• Employee referral program
• Stocked kitchen
• Accessible to all public transportation including BART and MUNI via Powell Station
• Bright, cheerful, convenient, Union Square location
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/f24128fa-3815-4af2-ad16-5a5783b6506b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.