Ethan

Making products people love πŸ”₯πŸš€

Get csp-report field, prettily JSON.stringify it and send it in a message to Telegram via my bot

Added a same-origin report URI that points to a cloud function to my Content Security Policy

Updated all cloud function calls in the web app to call the functions on the same domain. Now because it's not cross origin they don't need to send OPTIONS requests first, meaning I *HALVE* my cloud functions usage and am even less likely to hit the free limit

Switched functions.kanbanmail.app over from the cloud-functions repo to the web repo

Updated build command & functions output folder in Netlify settings for web repo

Added special proxy rules for functions.kanbanmail.app to the web repo so I can add it as a domain alias of web.kanbanmail.app and then function calls to functions.kanbanmail.app will still work

Moved all environment variables over from cloud-functions repo to web repo

Added a netlify-build npm script that calls the build script and then calls the netlify-lamda build command

Merged dependencies of the cloud-functions repo into the dependencies of the web repo

Updated all references to custom modules in cloud functions in web repo with the correct paths

Copied other module files from the cloud-functions repo and put them in a custom_modules folder in _input_functions in the web repo

Copied all cloud function files to _input_functions folder in web repo

Cleaned up cloud-functions repo before merge, created test and internal folders

Decided to move cloud functions into web app repo so I don't need extra OPTIONS requests for cross-origin stuff

Sent tweet about demo data! https://twitter.com/Booligoosh/status/1107802179102896129

So I'm doing an experiment and letting you contribute to the demo data for KanbanMail (that will show up in the screnshots etc.) β€” You can contribute here πŸ‘‰ kanbanmail.app/demodata πŸ‘ˆ