search

di2e / Argo

Runtime service discovery, configuration and cyber-security
http://docs.argo.ws
MIT License
2 stars 1 forks source link

Create Responder Plugin for simple file/web server #110

Open jvettraino opened 8 years ago

jvettraino commented 8 years ago

This responder plugin should respond with the locations of the files that are exposed in the embedded web server. This will allow an Argo responder for files without the need for a separate web server

jmsimpson68 commented 8 years ago

This I'd like to know more about. Generally plugins should be a separate project/repo.

Jeff Simpson 571-212-0927

On May 15, 2016, at 9:59 PM, Jeff Vettraino notifications@github.com wrote:

This responder plugin should respond with the locations of the files that are exposed in the embedded web server. This will allow an Argo responder for files without the need for a separate web server

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub

jvettraino commented 8 years ago

This is to support the Px goal. We can move to a separate repo/area if that is better, I just have it in here on a branch for now argo-file-server-plugin Basically what it does is spin up a small web server as part of the plugin and then returns Argo files that point back to files served up in the web server.

jmsimpson68 commented 8 years ago

Yea, I would definitely recommend having the plugin be a separate repo and manage it independently of the core Argo release.

Each plugin should be its own jar that just gets dropped into the lib dir and have a little config done.

Jeff Simpson 571-212-0927

On May 16, 2016, at 8:57 AM, Jeff Vettraino notifications@github.com wrote:

This is to support the Px goal. We can move to a separate repo/area if that is better, I just have it in here on a branch for now argo-file-server-plugin Basically what it does is spin up a small web server as part of the plugin and then returns Argo files that point back to files served up in the web server.

— You are receiving this because you commented. Reply to this email directly or view it on GitHub