Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

simple configuration - not coding? #389

Closed
amanu opened this Issue Mar 22, 2013 · 3 comments

Comments

Projects
None yet
3 participants

amanu commented Mar 22, 2013

trying to put node-http-proxy in front of some node instances and also legacy apps, so far looks extremely complicated compared to apache httpd that I'm trying to replace :(.

any plans to offer the user a simplified config mode, not a coding based one?

regards.

@indexzero indexzero closed this Mar 23, 2013

amanu commented Mar 23, 2013

There is one already ... rtfm?

Sorry but there there's really no FM to start with :).
(wiki is empty, official website not existing not as many other projects; or not linked from the readme).

There's only the long(thankfully) readme that shows that if anything can be done, it must be coded by hand in JavaScript. While I enjoy coding in JavaScript, in most companies, one WON'T be able to pass it to those from admin/maintenance :).

https://github.com/nodejitsu/node-http-proxy/blob/master/bin/node-http-proxy#L9-L22

BTW, I haven't asked about the command line parameters :).

Just tried to push as small node based app in production, so a proxy replacement was required too :).
Pointing the admins to this project (there are not that many node proxy projects :) ), got the answer to give them something production ready that just needs to be configured (like the apache.org httpd), not just a library to code against :).

Contributor

mmalecki commented Mar 23, 2013

There are multiple examples in the examples directory.
The thing about http-proxy is that it offers countless possibilities and there's no easy way to simply configure it with a JSON file or anything like that. It'd simply become a mess. I believe that everyone should be able to understand as little JavaScript as it's required to configure a basic proxy (if not, I think that basically explaining the code to them would do the job).

Of course, you are welcome to write a tool to create a proxy basing on a config file, which will suit your needs. Keep in mind that it won't suit everyone's needs.

If you have problems with configuring the proxy, feel free to reach out to us in #nodejitsu channel on Freenode. I'm mmalecki there. I'd be happy to help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment