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

Cht.sh is down 🤯 #405

Open
sathishkannan162 opened this issue Mar 22, 2024 · 2 comments
Open

Cht.sh is down 🤯 #405

sathishkannan162 opened this issue Mar 22, 2024 · 2 comments

Comments

@sathishkannan162
Copy link

sathishkannan162 commented Mar 22, 2024

cht.sh is not working. It seems the website is down.

Screenshot 2024-03-22 at 5 53 24 PM
@chubin
Copy link
Owner

chubin commented Mar 22, 2024 via email

@earboxer
Copy link

After I discovered cht.sh was down (Thursday afternoon), I wanted to start my own cheat server.

I found it was directing it's requests to cht.sh, so I changed upstream.url to my own server instead, but that caused it to just cascade a bunch of requests to my own server.

I don't want fully-offline, I want the ability to host my own cheat.sh.
(if we could do this, then we could even have a "list of known cheat.sh instances" so that people can still use it when the main instance is down)

In lib/adapter/question.py, it says

    Answer to a programming language question, using Stackoverflow
    as the main data source. Heavy lifting is done by an external
    program `CONFIG["path.internal.bin.upstream"]`.

    If the program is not found, fallback to the superclass `UpstreamAdapter`,
    which queries the upstream server (by default https://cheat.sh/)
    for the answer

@chubin Where is this bin/upstream? Most of my requests to cheat.sh would be handled by it.

I think it would be a great benefit to programmers everywhere if that was open source as well. (even if e.g. we need a stackexchange api key or some large data dump somewhere)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants