Re: [Rails] Old Rails app from Docker Container - trying to run natively again . .

Hassan, On 2020-03-15 11:31, Hassan Schroeder wrote: On Sat, Mar 14, 2020 at 3:52 PM Philip Rhoades wrote: Docker crashed and I lost the Rails container so I have to go back to the original source. I don't know what "lost the Rails container" means. Can't you just rerun the Dockerfile?

Re: [Rails] Old Rails app from Docker Container - trying to run natively again . .

On Sat, Mar 14, 2020 at 3:52 PM Philip Rhoades wrote: > Docker crashed and I lost the Rails container so I have to go back to > the original source. I don't know what "lost the Rails container" means. Can't you just rerun the Dockerfile? > Could someone suggest how I could fix the problem seen

[Rails] Old Rails app from Docker Container - trying to run natively again . .

People, Docker crashed and I lost the Rails container so I have to go back to the original source. Could someone suggest how I could fix the problem seen below? - I deleted the Gemfile.lock file first. Thanks, Phil. $ bundle install --path vendor/bundle . . Bundle complete! 15 Gemfile

[Rails] Is it worth switching to Postgresql?

No, it isn't. If you notice only those 2 downside, you'd better stick with you current choice. MySQL 8 has better encoding support, I am assuming you're mentioning about emoji encodings. And you can also learn Docker for ease of development to address the other issue you have. -- You received

Re: [Rails] Is it worth switching to Postgresql?

Sorry, using different db on different environment is not something I'm recommending, it was just to point out that the transition should be really easy. I do think it's faster to prototype using sqlite as long as it fits the needs, but in a more mature projects I would use the same db everywhere

Re: [Rails] Is it worth switching to Postgresql?

> On Mar 14, 2020, at 12:17 PM, Rob Jonson wrote: > > thanks folks, > > I guess I'm asking more about the practical pain points. - As you say, I > trust rails to deal with most of the day-to-day. > > do you end up battling to get your postgres install working after upgrading > mac (or

Re: [Rails] Is it worth switching to Postgresql?

thanks folks, I guess I'm asking more about the practical pain points. - As you say, I trust rails to deal with most of the day-to-day. do you end up battling to get your postgres install working after upgrading mac (or postgres?) do you have problems with string encoding incompatibilities in

Re: [Rails] Is it worth switching to Postgresql?

I think Ariel's reply is spot-on. Rails is basically DB agnostic, however I think the trend is that PostgreSQL is the more favored backend (except for stuff like Wordpress). We're doing a lot more SQL procedural stuff these days with our rails apps (e.g. kicking out JSON from a single query

Re: [Rails] Is it worth switching to Postgresql?

Usually ActiveRecord takes care of most of the differences, and postresql has a lot of similarities with mysql. I guess it would be a different call if you ask about learning a completely different db engine like mongo or graphql, but learning postgresql shouldn't take too much time knowing MySQL,

[Rails] Is it worth switching to Postgresql?

Hi Folks, I have been using Mysql for forever, and broadly it works fine for me, with two complaints 1) occasional issues with mismatches in encoding/collation on strings 2) hours lost on every mac upgrade trying to get mysql working properly again I know that people are generally favouring