nick
nick
I think Travis on Rubinius just needs to be rebuilt for this build to pass; it is working on all other distros and worked for me when I used `guard...
this information is available in the heroku panel.
fwiw, I think it makes sense to publicly document `responseAllowList` and `requestAllowList` and silently support `responseWhitelist` and `requestWhitelist` as aliases. I've seen this approach across many libraries making similar changes.
Did you run `yarn build` before `docker build` ?
hmm, I'm not sure what your issue is then. given that this docker image hasn't been updated in a while, I shared a solution (and there are others) on this...
nice, thanks @ekeih fwiw here's my Dockerfile using Nginx. ``` ARG GATSBY_ACTIVE_ENV=production FROM node:12-buster AS build RUN yarn global add gatsby-cli ARG GATSBY_ACTIVE_ENV ENV GATSBY_ACTIVE_ENV=$GATSBY_ACTIVE_ENV WORKDIR /app ADD . ./...
@daydream05 you could add the string `"public, max-age-0, must-revalidate"` to this line https://github.com/NeonLaw/codebase/blob/development/docker/production.nginx.conf#L73
you can source from git in your Cargo.toml like: ``` hubcaps = { git = "https://github.com/softprops/hubcaps", branch = "master" } ``` also fwiw, I'm not @softprops, but I'd be offended...
please do not close, this is still an issue.