You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using the tech-docs-monitor over at HMRC, where we've built it in to an AWS Lambda function. This is working really well for us, however it currently requires us to maintain a fork of this repository in order to add the necessary Lambda build and runtime functionality.
It occurred to me that, if there were a distributable tech-docs-monitor RubyGem then we could ditch our fork and simply consume the Gem in the usual manner, adding the necessary scaffolding to allow us to build the Gem in to an AWS Lambda. I was wondering if you might be open to such an approach?
Grateful for your thoughts on this one. In case it aids your thinking then you can see the adaptations that we've made to get everything work in AWS Lambda here.
Many thanks,
Edd
The text was updated successfully, but these errors were encountered:
Hope you'll excuse my pinging you directly. Was wondering if either of you are still working on this repository? Would be great to chat about this request if you are.
This would be useful for us too, either a gem or command line tool that's released would be great (rather than having to fork the repo and resolve conflicts between us and upstream).
I know you're all super busy, but if you're open to this work being done I might be able to put some time aside to do the majority of it. There's a slight complication that I won't be able to test it as I'm not in the GDS GitHub org, but I could perhaps copy the publishing configuration in alphagov/tech-docs-gem and then hand it over to yourselves in a PR for testing and tweaking.
Hi folks,
We're using the tech-docs-monitor over at HMRC, where we've built it in to an AWS Lambda function. This is working really well for us, however it currently requires us to maintain a fork of this repository in order to add the necessary Lambda build and runtime functionality.
It occurred to me that, if there were a distributable tech-docs-monitor RubyGem then we could ditch our fork and simply consume the Gem in the usual manner, adding the necessary scaffolding to allow us to build the Gem in to an AWS Lambda. I was wondering if you might be open to such an approach?
Grateful for your thoughts on this one. In case it aids your thinking then you can see the adaptations that we've made to get everything work in AWS Lambda here.
Many thanks,
Edd
The text was updated successfully, but these errors were encountered: