lacinia-pedestal adds support for accessing Lacinia GraphQL as an HTTP endpoint
GitHub repo: https://github.com/walmartlabs/lacinia-pedestal
Documentation: http://lacinia-pedestal.readthedocs.io/en/latest/
Featured changes in 0.16.1:
- Updated the version of the packaged GraphiQL; this
Just wanted to correct a mistake in what I wrote above. Obviously you can't
clear the password hashes while retaining a link between people and their
accounts, so it would more accurately be stated as all accounts are gone
and you have to create a new account.
On Tue, Jul 6, 2021 at 12:42 AM
Thank you Alan for all your contributions :)
Hosting things and maintaing them is really hard. We, the LambdaIsland
team, are already maintaining clojurians-log and clojureverse and it's
definitely not easy!
With a wonderful idea from @borkdude and his `sci` library, I built
"4ever-clojure":
Hey Alan, we really like 4clojure. We've suggested using it for training
most people at nilenso and we're very thankful to you and all the
contributors for that!
We (nilenso) would be up for picking up the hosting costs, and also some
other operations or development work if needed.
It would be
Hear, hear! Thank you for your wonderful work. It has been such a joy to be
able to use the service throughout the years. If you do end up dumping a
dataset with the problems, it would be great to also get the solutions if
feasible. For me personally I have perhaps learned the most by studying
Thanks for all the work (and money!) that's been spent over the years
maintaining 4clojure, I know it's been much appreciated by many in the
community. Is it possible to provide a data dump of the problem set? As far
as I can tell this data isn't in the Github repo, it seems to be in a Mongo
Hi Alan,
Just as a thought. If it's minimal work on your end (eg. if the folks from
Roam research who chimed in above pick it up) why not clear the password
hashes and let the new maintainer handle the communication that passwords
need to be reset?
Rob
On Sun, Jul 4, 2021 at 1:26 PM Alan
