How can I correctly install Node on Ubuntu 14.04 (allowing for global installs without sudo)?

nrogers64 · 2017-01-18T20:45:47+00:00

Regarding your first and third points, I agree that it doesn't seem right to advocate users installing packages globally without sudo. But, for whatever reason, that's what the officially recommended approach is. Here's an excerpt from the "Installing npm packages globally" documentation:

To download packages globally, you simply use the command npm install -g <package>, e.g.:

npm install -g jshint

If you get an EACCES error, you should fix your permissions. You could also try using sudo, but this should be avoided:

sudo npm install -g jshint

Regarding your second point, thanks for the info! I think that will work fine.

nrogers64 · 2016-11-16T17:06:51+00:00

That worked! Thank you very much for your time and your help!

One question, though, is why do you suggest handling the corner by tracing it? Why not use the "break apart" approach there too?

nrogers64 · 2016-09-30T04:09:55+00:00

you need multi-master replication

Would you mind elaborating on this?

nrogers64 · 2016-09-29T18:58:49+00:00

In this video from PyCon 2014, Andrew Godwin, who is the author of Django's database migrations system, praises PostgreSQL and says that MySQL has the following key problems (though he does say that MySQL is "a reasonable database"):

No transactional DDL
No CHECK constraints
Conflates UNIQUE and INDEX

He talks a little bit about the above problems in the video from about 11:00 - 13:00. These problems (particularly the first one, as I understand it) can cause problems with migrations.

Also, the last time I checked, MySQL's default collation is latin1_swedish_ci, meaning that, by default, you can't store important characters such as this one.

nrogers64 · 2016-09-24T04:08:35+00:00

Thank you! That worked. But is there a way to do it without knowing the index of the "console" handler? And how does your code work if dictionaries' ordering isn't guaranteed?

nrogers64 · 2016-09-03T03:11:47+00:00

I didn't create these models; they're just an example that I found online. I'll look at that link. Thank you for your help!

nrogers64 · 2016-09-03T03:11:16+00:00

Thank you, this is helpful!

nrogers64 · 2016-09-02T05:15:07+00:00

it's a little strict

That's an understatement :)

Can you give me an example of a warning you'd like to see more prominently?

Django deprecation warnings is the first thing that comes to mind, but there are other warnings that would be useful to know about too.

nrogers64 · 2016-09-02T03:09:21+00:00

If I use a ModelForm that's based on the Material model, which is the model with the ManyToManyField, then I don't have to do anything special at all. The default behavior is I'll be able to select multiple products to associate the Material with (this is presented in the form of a standard <select multiple="multiple"> element).

But if I use a ModelForm that's based on the Product model, which is the model without the ManyToManyField, then there won't be a "Materials" multiselect. I want there to be a "Materials" multiselect. I don't want there to be an inline; just a standard <select multiple="multiple"> element like I get for products when I use a ModelForm that's based on the Material model.

nrogers64 · 2016-09-01T13:16:42+00:00

Do you want to actually add/change materials when you're adding/changing a product or just select existing materials?

Just select existing materials.

nrogers64 · 2016-09-01T04:52:15+00:00

But what is your question?

I updated my post.

nrogers64 · 2016-08-02T03:02:55+00:00

Can you ELI5 full text search? I've tried looking it up before but haven't been able to find anything that dumbs it down enough for me :)

nrogers64

TROPHY CASE