Local development doesn't work without setting VAPID config about stacker.news HOT 3 CLOSED

IMO would love to see the effort to get a dev env setup reduced. I think wrapping that in a conditional for running in development would be nice, e.g.

if (process.env.NODE_ENV === 'development' && !process.env.VAPID_MAILTO) {
  console.info('VAPID_* env vars not set in development, skipping webPush setup')
} else {
  webPush.setVapidDetails(
    process.env.VAPID_MAILTO,
    process.env.NEXT_PUBLIC_VAPID_PUBKEY,
    process.env.VAPID_PRIVKEY
  )
}

Alternatively, move the setVapidDetails call into one (or many) of the async functions so that it just throws on the first time you attempt to do anything with push, rather than during initial render.

from stacker.news.

IMO would love to see the effort to get a dev env setup reduced. I think wrapping that in a conditional for running in development would be nice, e.g.

if (process.env.NODE_ENV === 'development' && !process.env.VAPID_MAILTO) {
  console.info('VAPID_* env vars not set in development, skipping webPush setup')
} else {
  webPush.setVapidDetails(
    process.env.VAPID_MAILTO,
    process.env.NEXT_PUBLIC_VAPID_PUBKEY,
    process.env.VAPID_PRIVKEY
  )
}

Alternatively, move the setVapidDetails call into one (or many) of the async functions so that it just throws on the first time you attempt to do anything with push, rather than during initial render.

Just a +1 here, I used the above quoted code snippet to enable local development and it got me past this issue. Thank you for the workaround!

from stacker.news.

Ah, thanks for the issue and you are right! It doesn't work without setting up these environment variables and we should update our documentation.

For the VAPID keys, you can run npx web-push generate-vapid-keys. VAPID_MAILTO should just be a mail prefixed with mailto:. So mailto:[email protected] should work.

There may be a similar issue for the imgproxy env but these don't prevent starting the server. However, It may break the frontend when visiting some posts. For IMGPROXY_KEY and IMGPROXY_SALT you can run openssl rand -hex 64.

Would you mind creating a PR to document this? Else I can do this soon.

from stacker.news.