Open groovecoder opened 8 years ago
Doesn't doiuse.com already exist like this? Perhaps we should ask the owner about assisting with the already existing server, rather than spinning up a brand new one.
unless we have some other micro-services to attach to this aswell. :wink:
I'm not sure what you're asking? I'm talking about changing this GitHub web hook code to use doiuse.com "api" instead of installing the doiuse module into the web hook itself. I've sent issues and PRs upstream to the doiuse.com repository.
You have http://moz-doiuse.herokuapp.com in your example code. I assumed that would be a newly created service.
On Thu, Jan 14, 2016, 17:33 luke crouch notifications@github.com wrote:
I'm not sure what you're asking? I'm talking about changing this GitHub web hook code to use doiuse.com "api" instead of installing the doiuse module into the web hook itself. I've sent issues and PRs upstream to the doiuse.com repository.
— Reply to this email directly or view it on GitHub https://github.com/mdn/discord/issues/167#issuecomment-171816982.
Q: Why is this email five sentences or less? A: http://five.sentenc.es
Newly created? You doubt my powers? https://moz-doiuse.herokuapp.com/ is working with all the modifications we need! ;)
This is a big architectural change and may require updates to the doiuse.com code-base itself.
When we make more
doiuse
interfaces - editor plugins, browser extensions, site monitors, etc., we want them to call a single doiuse.com server, so we can update all clients with the latest and greatestdoiuse
functionality with a single server deployment.So, we should change discord to call to a doiuse.com server instead of using
postcss(doiuse())
directly. E.g., something like: