-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
How to use briefkasten cloud? #70
Comments
@pH142857 on both instances you simply signin with your provider of choice, and then you land at the main screen of the application, as you mentioned, and can begin using it. I see that email login might be broken in v1 (briefkastenhq.com), ill check that out. |
Thanks for your answer. v2 looks also broken because I am not redirected to the application but to a blank page instead (when I created the ticket I was redirected to the login screen). So both versions are not usable for me. |
@pH142857 interesting, can you provide any additoinal context? Are there any errors in our console? I've been using v2 myself without issue almost daily 🤔 Am I understanding this correctly? In v2 (dev.briefkastenhq.com), you click on "Login with GitHub", you login with your GitHub account and are then redirected to a dev.briefkastenhq.com (which path exactly? Can you share the URL?) and it's just a white page? |
You understood correctly. Now that I am logged in I get that white page immediately when loading
|
Describe the bug
I would like to try Briefkasten and I understand there is a cloud instance at https://briefkastenhq.com and a beta one for v2 at https://dev.briefkastenhq.com, but I fail to see how to create an account. I tried the "email magic field" link but I got:
Then I tried through the GitHub button and accepted the third-party OAuth app on GitHub, but then I simply got redirected to the instance page and that's it.
The documentation is mute about it:
Reproduction
Go to briefkastenhq.com and try anything
System Info
Used Package Manager
n/a
Validations
The text was updated successfully, but these errors were encountered: