figedi / coffeescrape

A simple scraper to get me some sweet second-hand coffee-machines

coffeescrape

A tiny scraper to get me some sweet coffee deals and notify me in telegram

Currently supported providers

• espressoperfetto
• kaffeezentrale
• mcc
• moba
• moema

Installation

No special setup needed, just run npm ci

Usage

You need to provide an env-file for local usage, see .env.example for values, names should be self explainatory.

Building / Deployment

This project is deployed to google cloud-run and triggered via cloud-scheduler periodically. The provided gh-actions workflow directly deploy new versions. To deploy your own version, do the following:

• Setup gh secrets (see all of them in the workflows file {{ .secrets. }})

• Setup in gcp service-account with proper access rights (cloudrun-admin, service-account-user, storage-admin), also put it in secrets

• Commit and deploy 🚀

• If it works, yay. If it doesnt, meh. Try reading the errors, it is most likely a permission issue w/ gcp. Note that you might have to go to the console to adjust the network access

Note: I did not use secrets for now and instead pass secret values via env-vars, naughty me.

Your service should be deployed and up and running as you will, if you want a similar setup as I have, try combine the deployment w/ cloud-scheduler for periodic checking.

coffeescrape's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀