search

Strider-CD / strider-github-status

Strider test status for Github Pull Requests
7 stars 8 forks source link

Missing in npm-registry #1

Closed edwardsmit closed 9 years ago

edwardsmit commented 10 years ago

This project seems missing in the npm registry. I successfully installed this plugin through manual deployment steps and the plugin does what it's supposed to do. What needs to be done to make this an official plugin?

niallo commented 10 years ago

@jaredly is this ready to go to npm?

jaredly commented 10 years ago

Yeah that would be great

niallo commented 10 years ago

Thanks, I'll push it when I get the chance!

cusspvz commented 9 years ago

Could you please push it to npm? It is not safe and pratical to have plugins coming directly from git.

cusspvz commented 9 years ago

@jaredly as you are currently working on strider-github-status couldn't you simply just npm publish ? :smile:

jaredly commented 9 years ago

https://www.npmjs.org/package/strider-github-status

cusspvz commented 9 years ago

You deserve a massive Thanks! :)

cusspvz commented 9 years ago

One more question, what is the approach you setup to maintain strider updated and with plugins?

Since strider package doesn't have some plugins as dependencies, and i didn't see anything about this subject i've created a fork, added the plugins we use and cloned into our strider production server.

Problem is that it is not secure to have something being deployed directly from git instead of npm.

I've seen also that Strider has support to run on docker, but that doesn't allow external plugins, maybe unless if another container is created on top of strider?

jaredly commented 9 years ago

The "current way" as such is to npm install any plugins you need after grabbing strider. There's been some preliminary work on a plugin manager, with both a console and a web interface On Oct 8, 2014 7:20 PM, "José Moreira" notifications@github.com wrote:

One more question, what is the approach you setup to maintain strider updated and with plugins? Since strider package http://Strider-CD/strider/blob/master/package.json doesn't have some plugins, and i didn't see anything about this subject i've created a fork, added the plugins we use and cloned on our strider production server.

Problem is that it is not secure to have something being deployed directly from git instead of npm.

I've seen also that Strider has support to run on docker, but that doesn't allow external plugins, maybe unless if another container is created on top of strider?

— Reply to this email directly or view it on GitHub https://github.com/Strider-CD/strider-github-status/issues/1#issuecomment-58451799 .

cusspvz commented 9 years ago

Could hotplug help you in some way? We developed this because we would need a simple and reliable plugin system on almost every tool we write.