Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove reference to hosted service #96

Merged
merged 1 commit into from Jan 6, 2018

Conversation

Projects
None yet
3 participants
@c-w
Copy link
Owner

commented Jan 5, 2018

No description provided.

@c-w c-w requested a review from hugovk Jan 5, 2018

@hugovk

This comment has been minimized.

Copy link
Collaborator

commented Jan 5, 2018

Is the hosted version going away?

If so, also change the wording in "A hosted version of this package exists too.".

@c-w c-w force-pushed the c-w-patch-1 branch from 273bca7 to 4a0b8ae Jan 5, 2018

@c-w

This comment has been minimized.

Copy link
Owner Author

commented Jan 5, 2018

Good point, that could be clearer. Fixed. The HTTP wrapper repo isn't going away, I just don't have the bandwidth anymore to maintain the hosted deployment of the wrapper.

Happy to hand over the reins if someone else wants to take this on though. I'm also happy to continue paying for infrastructure costs and provide:

  1. An Azure VM of up to $35/month, e.g. one of the new B-series could work well.
  2. A nice domain name: gutenbergapi.org; I still have this until April, happy to renew and keep paying for it if someone wants to take over hosting the service.

@hugovk @cpeel @MasterOdin @sethwoodworth anyone interested?

README.rst Outdated
@@ -24,7 +24,8 @@ The functionality provided by this package includes:

The package has been tested with Python 2.7, 3.4, 3.5 and 3.6.

A hosted version of this package exists too. `Try it out! <https://c-w.github.io/gutenberg-http/>`_
A HTTP interface to this package exists too.

This comment has been minimized.

Copy link
@hugovk

hugovk Jan 5, 2018

Collaborator

-> "An HTTP"

@hugovk

This comment has been minimized.

Copy link
Collaborator

commented Jan 5, 2018

I'm good with the offline version, thank you.

@c-w c-w force-pushed the c-w-patch-1 branch from 4a0b8ae to 303c15d Jan 5, 2018

@hugovk hugovk merged commit 361e3bb into master Jan 6, 2018

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@hugovk hugovk deleted the c-w-patch-1 branch Jan 6, 2018

@MasterOdin

This comment has been minimized.

Copy link
Collaborator

commented Jan 7, 2018

Following up on the conversation, what did you (@c-w) mean by:

The HTTP wrapper repo isn't going away, I just don't have the bandwidth anymore to maintain the hosted deployment of the wrapper.

How much bandwidth was being used by people for the app? Or was it more in downloading and processing the Gutenberg dump on a however often basis.

I'm willing to help take over maintaining the hosted version if people are using it and are finding it valuable (especially given that you're willing to help with costs).

@c-w

This comment has been minimized.

Copy link
Owner Author

commented Jan 7, 2018

@MasterOdin Thanks for getting in touch and apologies for the ambiguity; bandwidth definitely refers to "human bandwidth" here, i.e. time for dealing with the long-term work of keeping a service running, including:

  • Updates for the VM.
  • Upgrading the metadata catalog every now and then.
  • Renewing TLS certs (e.g. there was recently an issue where certbot auto-renew would randomly fail).
  • Dealing with shifting dependencies (e.g. there recently was an issue with pip-install on Python 3.6)
  • And so forth.

Processing power or hosting costs are not currently an issue.

Not to worry: It's not all that much work in the grand scheme of things, but between a new job and volunteering for Ascoderu, my free time has recently been pretty limited.

Long term, I'd love to get the service into a better shape (e.g. improve monitoring via
a service like Application Insights, set up auto-updates for the metadata catalog, etc.) and then start a conversation with the gutenberg.org team if they'd be interested in taking on the API as a first-party service.

Thanks for stepping up! I'll reach out via email with next steps so that we can get you access to a VM and to the DNS.

@MasterOdin

This comment has been minimized.

Copy link
Collaborator

commented Jan 7, 2018

Yeah sure, a lot of what I do in my day job is in automation which seems like doing this stuff would be up my alley. I believe you have my email already, but it's also in my profile as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.