Closed Bug 1144416 Opened 11 years ago Closed 11 years ago

SUMO: Install npm and make it available on the system path

Categories

(Infrastructure & Operations Graveyard :: WebOps: Community Platform, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rehandalal+mozilla, Assigned: fox2mike)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/770] )

We are now installing node dependencies when we deploy SUMO, so we will need npm to be available.
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/770]
See Also: → 1142120
Blocks: 1143951
Blocks: 1143943
Blocks: 1143947
Blocks: 1143946
Blocks: 1143941
Any chance of getting this in there soon? It's blocking a lot of things from landing. Thanks!
So if npm is on the box, it's good enough?
As far as I know. We might run into something else, but I expect a working npm to be enough.
Hey Shyam! Think we might be able to get this today?
I'll poke at this now, from IRC this is only needed on the admin node.
Assignee: server-ops-webops → smani
sysadmins r102418 has the puppet commit to install npm. supportadm.private.phx1 now has npm installed : [root@supportadm.private.phx1 ~]# which npm /usr/bin/npm [root@supportadm.private.phx1 ~]# npm --version 1.3.6
We deployed our staging environment using a new branch that uses npm. It worked, and we were able to install our node-based dependencies via npm-lockdown. This gives us the ability to install and use node tools, and gievs us the same cryptographic assurance when doing so for those as peep gave us for python dependencies. Thanks!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.