Thank you for your feedback Sasha and Walter.
On Sunday, March 10, 2019 at 8:59:25 PM UTC-4, Sasha Boginsky wrote:
>
> Hi,
>
> I just switch it to sassc-rails and it works basically the same.
>
> Sasha
>
>
> > On Mar 10, 2019, at 8:02 PM, Walter Lee Davis > wrote:
> >
> >
> >> On Mar 10, 20
Hi,
I just switch it to sassc-rails and it works basically the same.
Sasha
> On Mar 10, 2019, at 8:02 PM, Walter Lee Davis wrote:
>
>
>> On Mar 10, 2019, at 6:17 PM, brainiacs...@gmail.com wrote:
>>
>> Hi Everyone,
>>
>> I was just curious as to what everyone is using since sass-rails is
> On Mar 10, 2019, at 6:17 PM, brainiacs...@gmail.com wrote:
>
> Hi Everyone,
>
> I was just curious as to what everyone is using since sass-rails is
> depreciating and if I add a ui kit it should change the look and feel of the
> app without have to change a great deal of the css. Correct?
Hi Everyone,
I was just curious as to what everyone is using since sass-rails is
depreciating and if I add a ui kit it should change the look and feel of
the app without have to change a great deal of the css. Correct?
--
You received this message because you are subscribed to the Google Group
I installed NodeJs and it worked like a charm. Thank you Colin, Walter and
everyone. The only issue I have now appears to be Can't connect to local
MySQL server through socket '/var/run/mysqld/mysqld.sock'. It never ends.
LOL
n Sunday, March 10, 2019 at 5:57:48 PM UTC-4, Colin Law wrote:
>
> O
On Sun, 10 Mar 2019 at 20:30, wrote:
>
> Hi Colin,
>
> I am not sure but I think the issue is that it is running on a desktop right
> now rather than on a webserver.
Shouldn't make any difference, provided you have run bundle install on
the desktop. Nowadays I do use nodejs but I used to use th
Hi Colin,
I am not sure but I think the issue is that it is running on a desktop
right now rather than on a webserver.
Thanks,
On Sunday, March 10, 2019 at 4:04:21 PM UTC-4, Colin Law wrote:
>
> On Sun, 10 Mar 2019 at 17:35, > wrote:
> >
> > Thank you Walter and Hasan. The gem is actually in
On Sun, 10 Mar 2019 at 17:35, wrote:
>
> Thank you Walter and Hasan. The gem is actually in the gem file but this
> occurred in development on my desktop so my guess would be I would need to
> install it there.
If therubyracer is in your Gemfile then that should be enough.
Colin
>
> On Sunday
Correct Walter. I have the data. I have to do a conversion and then it is
all set.
On Sunday, March 10, 2019 at 1:26:32 PM UTC-4, Walter Lee Davis wrote:
>
> Just the schema. For the data, you'd need to run a backup utility of some
> sort. On MySQL, there's mysqldump, I'm pretty sure there's sim
Thank you Walter and Hasan. The gem is actually in the gem file but this
occurred in development on my desktop so my guess would be I would need to
install it there.
On Sunday, March 10, 2019 at 1:27:30 PM UTC-4, Walter Lee Davis wrote:
>
> Correct. Your server does not have a JavaScript interp
Correct. Your server does not have a JavaScript interpreter available at the
command line. These days, I just install whatever version of NodeJS is in the
package manager for that server. If you want to avoid any server dependencies,
you can just add therubyracer to your Gemfile and bundle on th
Just the schema. For the data, you'd need to run a backup utility of some sort.
On MySQL, there's mysqldump, I'm pretty sure there's similar on the Postgres
side, so no matter which direction you want to go, you'd be set. Be sure to
only dump the data, not the structure, if you're using the sche
Yes I did. Where I was thrown off is in trying to understand what the
literal issue is so I could resolve it as my understanding was if there
were any outstanding issues with the app it wouldnt bundle I assumed the
issue to be OS related. I
On Sunday, March 10, 2019 at 1:10:22 PM UTC-4, Hassan
On Sun, Mar 10, 2019 at 9:45 AM wrote:
> Now that the bundle install has run successfully I have run into the
> following error while running rake db:create. Does anyone have any ideas how
> to resolve the issue?
> rake aborted!
> ExecJS::RuntimeUnavailable: Could not find a JavaScript runtime
Hi Everyone,
Now that the bundle install has run successfully I have run into the
following error while running rake db:create. Does anyone have any ideas
how to resolve the issue?
Thanks,
rake aborted!
ExecJS::RuntimeUnavailable: Could not find a JavaScript runtime. See
https://github.com/r
>
> bundle exec rails db:schema:dump
does this dump the data, or just the schema?
I would assume just the schema - and that to transfer the data you'll need
to use something like the solutions here:
https://wiki.postgresql.org/wiki/Converting_from_other_Databases_to_PostgreSQL#MySQL
--
You
16 matches
Mail list logo
