Skip to content
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.

First joof setup failed — second time success #20

Open
kluplau opened this issue Oct 27, 2018 · 3 comments
Open

First joof setup failed — second time success #20

kluplau opened this issue Oct 27, 2018 · 3 comments
Assignees
Labels

Comments

@kluplau
Copy link

kluplau commented Oct 27, 2018

Hi,

First time running joof setup failed, saying the ~/.joof folder didn't exist. I tried cd'ing into it, but it did exists. I therefore tried running joof setup once again, this time with success.

image

Machine:
Running Node v9.11.2 (through NVM) on MacOS v10.13.6

@mikker
Copy link
Owner

mikker commented Oct 30, 2018

Thanks for reporting!

There's so much going on, I wonder if a better solution all-in-all would be to just provide better manual instructions?

@mikker mikker self-assigned this Oct 30, 2018
@mikker mikker added the bug label Oct 30, 2018
@kluplau
Copy link
Author

kluplau commented Oct 30, 2018

Maybe. The Safari extension installation was a surprise for me as well, as I am a Chrome-only user, so that should be optional. A manual process would fix this as well.

I'm not fully aware of what happens behind the scene, so I'm not in a position where I can provide comprehensive feedback regarding the one or the other solution.

@mikker
Copy link
Owner

mikker commented Oct 30, 2018

Safari Extensions are sort-of deprecated on their own too. They need to come with an App from the App Store now.

Browser specifics (extension, certificate) should be optional, yes.
The background service should stay in the installer.

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

No branches or pull requests

2 participants