Using Kong with web applications

202 views
Skip to first unread message

tho...@whogloo.com

unread,
May 3, 2016, 8:34:40 AM5/3/16
to Kong
Is anyone using Kong as a front end for managing access to websites or complete web applications in addition to APIs? 

We are looking the feasibility of using Kong for managing several parts of our infrastructure, and not just APIs. 

Currently we are using nginx-proxy and Docker containers, and are very happy with the way this works - especially with dynamics URLs, where we can have more than one URl for each of the "applications" that users can access. When we provision new environments, nginx-proxy picks this up and quickly makes the applications available through the configured URLs and ports. 

Would it make sense to replace the nginx-proxy layer with Kong instead? it would mean we can use the plugins to provide generic support for all the good things that Kong supports from basic authentication to more complex stuff. 

Thanks.

regards

Thomas Hansen
whoGloo, Inc. (www.whogloo.com


Marco

unread,
May 3, 2016, 2:44:37 PM5/3/16
to tho...@whogloo.com, Kong
Hello,

Kong can technically work with any HTTP service, that includes APIs but also regular web-applications - I don't see any problem in doing so. I guess you could give it a try and let us know who that works.

Cheers


 Marco Palladino | CTO @ Mashape | mashape.com+1 (415) 361-3858

--
You received this message because you are subscribed to the Google Groups "Kong" group.
To unsubscribe from this group and stop receiving emails from it, send an email to konglayer+...@googlegroups.com.
To post to this group, send email to kong...@googlegroups.com.
Visit this group at https://groups.google.com/group/konglayer.
To view this discussion on the web visit https://groups.google.com/d/msgid/konglayer/848ac2b6-6358-497d-a97a-f119d265a476%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

tho...@whogloo.com

unread,
May 3, 2016, 3:16:05 PM5/3/16
to Kong, tho...@whogloo.com
Thanks Marco, 

We are testing at the moment, but were hoping someone else had beat us to it ;-) 

Along the same lines ..one of the things we are very keen on with using nginx-proxy is the automated creation of proxy configurations (and now also combined with letsencrypt to provide https support) for docker containers. Has anyone tried to extend this to automatically generate kong APIs? 

TIA

Regards

Thomas

Christopher Farnham

unread,
May 6, 2016, 8:38:15 AM5/6/16
to Kong, tho...@whogloo.com
Thomas,

I've thought about this as well. How are you thinking of dealing with URL rewrites within the response payload?

Chris

Thomas Hansen

unread,
May 6, 2016, 10:06:47 AM5/6/16
to Christopher Farnham, Kong

Hi Chris,

 

That’s is one of the challenges with this that we need to work out. Although we would like to be able to use Kong for everything, we may end up with our website based end points being managed with more traditional authentication etc. and continue to use the nginx-prixy mechanism we have now – as this works very well with the URL rewrites as well.

Regards

Thomas Hansen
CEO
___________________________________
whoGloo
www.whogloo.com
whogloo750x450

image001.png

Marco

unread,
May 6, 2016, 2:27:28 PM5/6/16
to Thomas Hansen, Christopher Farnham, Kong
As a reminder, Kong has been built to be easily extended with custom plugins. I would give it a try (https://getkong.org/docs/latest/plugin-development/), it may be easier than what it seems, especially for things like rewriting the URLs in the response payload. 


 Marco Palladino | CTO @ Mashape | mashape.com+1 (415) 361-3858

--
You received this message because you are subscribed to the Google Groups "Kong" group.
To unsubscribe from this group and stop receiving emails from it, send an email to konglayer+...@googlegroups.com.
To post to this group, send email to kong...@googlegroups.com.
Visit this group at https://groups.google.com/group/konglayer.
Reply all
Reply to author
Forward
0 new messages