I figured I would check-in and see how the production is going. I was wondering if you considered integrating
Brewerwall as the main repository for all the grains, hops, yeasts, etc. Thanks for your hard work!
I looked at this and it looks really cool, thanks for the info, but sadly when I try to use the API, I get a redirect, is it working:
curl -v
http://brewerwall.com/api/v1/yeasts
* Trying 162.255.119.225...
* TCP_NODELAY set
* Connected to brewerwall.com (162.255.119.225) port 80 (#0)
> GET /api/v1/ HTTP/1.1
> Host: brewerwall.com
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 302 Found
< Server: nginx
< Date: Tue, 22 Jan 2019 18:13:33 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 48
< Connection: keep-alive
< Location:
http://www.brewerwall.com
< X-Served-By: Namecheap URL Forward
<
<a href='
http://www.brewerwall.com'>Found</a>.
* Connection #0 to host brewerwall.com left intact
but when I try to use the -L option to follow the 302 I get the html page, not the api:
curl -v -L
http://brewerwall.com/api/v1/yeasts
* Trying 162.255.119.225...
* TCP_NODELAY set
* Connected to brewerwall.com (162.255.119.225) port 80 (#0)
> GET /api/v1/ HTTP/1.1
> Host: brewerwall.com
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 302 Found
< Server: nginx
< Date: Tue, 22 Jan 2019 18:16:02 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 48
< Connection: keep-alive
< Location:
http://www.brewerwall.com
< X-Served-By: Namecheap URL Forward
<
* Ignoring the response-body
* Connection #0 to host brewerwall.com left intact
* Issue another request to this URL: '
http://www.brewerwall.com'
* Rebuilt URL to:
http://www.brewerwall.com/
* Trying 35.169.120.211...
* TCP_NODELAY set
* Connected to
www.brewerwall.com (35.169.120.211) port 80 (#1)
> GET / HTTP/1.1
> Host:
www.brewerwall.com
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 200 OK
and then the html page of the main website.
Doesn't seem to work for me?