~sircmpwn/public-inbox

sourcehut.org: Fix typo in GraphQL blog post v1 PROPOSED

Jake Bauer: 1
 Fix typo in GraphQL blog post

 1 files changed, 1 insertions(+), 1 deletions(-)
Export patchset (mbox)
How do I use this?

Copy & paste the following snippet into your terminal to import this patchset into git:

curl -s https://lists.sr.ht/~sircmpwn/public-inbox/patches/10980/mbox | git am -3
Learn more about email & git
View this thread in the archives

[PATCH sourcehut.org] Fix typo in GraphQL blog post Export this patch

---
 content/blog/2020-06-10-How-GraphQL-will-shape-the-alpha.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2020-06-10-How-GraphQL-will-shape-the-alpha.md b/content/blog/2020-06-10-How-GraphQL-will-shape-the-alpha.md
index a2d9ca5..60e4d64 100644
--- a/content/blog/2020-06-10-How-GraphQL-will-shape-the-alpha.md
+++ b/content/blog/2020-06-10-How-GraphQL-will-shape-the-alpha.md
@@ -95,7 +95,7 @@ The GraphQL services are completely standalone, and it is possible to deploy
them independently of the web application. With these, you can deploy a
SourceHut instance with no frontend at all, using the GraphQL APIs exclusively.
Today, the Python backends to the web services communicate directly with
PostgreSQL via SQLAlchemy, but it is my intention to built out experimental
PostgreSQL via SQLAlchemy, but it is my intention to build out experimental
replacement backends which are routed through GraphQL instead. This way, the
much more performant and robust GraphQL backends become the single source of
truth for all information in SourceHut. This could substantially increase my
--
2.20.1
Thanks!

To git@git.sr.ht:~sircmpwn/sourcehut.org
   763ac2c..4e9e7a3  master -> master