Bower: disable strict-ssl

[humitos]

I had to disable strict SSL on Bower due to an error with jQuery: bower/bower#2608

I'm not sure if this is strictly required, but I'm creating a PR in case we need to this in production as well.

Related #10356

[benjaoming]

Oh that seems annoying. Is this only for development and never for production?

There's an alternative to switching off SSL here that is popular: bower/bower#2608 (comment)

[agjohnson]

Not great, but we don't rebuild these assets often either way.

[humitos]

In theory, we rebuild them on each deploy when preparing the repositories.

[agjohnson]

Ah hrm, yeah I forgot that was added to the release script. I guess we can see if it affects next build and can plan from there. I'm not too worried about this fix, and we need to continue building our assets.

[humitos]

I'm confused now. I just prepare the repositories, but I don't think the inv docker.buildassets command was called 🤷🏼

[benjaoming]

@humitos I'm guessing that we only do builds with bower manually?

In that case, maybe this is fine? Perhaps post a follow-up issue to sort out if this old Node.js stack is staying or being replaced?

(assuming that the root of the issue is that most/all of the stack is outdated/deprecated, including some repo and its SSL certificate)

[humitos]

In that case, maybe this is fine? Perhaps post a follow-up issue to sort out if this old Node.js stack is staying or being replaced?

Yeah, "in theory", I understand the plan here "soonish" is to:

• replace the nodejs stack here with the one from ext-theme
• migrate all the readthedocs-embed.js feature to the new Addons js client

So, I think all the current stack is going to disappear in the medium term.

[benjaoming]

@humitos I think that a change like this which makes the build actually work is more desirable than the alternatives.

(I linked to an alternative that was using an unofficial repo which is also not a nice solution).

[humitos]

OK. I'm merging this for now so we unblock the generation of assets.