Remove reference to hosted service

[c-w]

No description provided.

[hugovk]

Is the hosted version going away?

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

[c-w]

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?

[hugovk]

-> "An HTTP"

[hugovk]

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

[MasterOdin]

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]

@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]

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.