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

Detect if we're running with encrypted home directories and suggest using AMPHOME instead #50

Open
mattwire opened this issue Sep 6, 2017 · 3 comments
Labels
environment-detection Ways to improve guided setup (amp config/amp test)

Comments

@mattwire
Copy link

mattwire commented Sep 6, 2017

amp test fails if you have ~/.amp under and encrypted home directory. Detect this scenario and suggest using AMPHOME environment variable instead to put the config somewhere else.

@totten
Copy link
Collaborator

totten commented Oct 24, 2017

I don't really have that Ubuntu-encrypted-home-directory configuration for testing (and not keen to reproduce), but... maybe we could have a document/scratchpad/wiki-page with a list of common problems, and then the amp test screen could show a link to that?

@colemanw
Copy link

colemanw commented Dec 5, 2019

Is there such a place? If so I'll document #55

@totten totten added the environment-detection Ways to improve guided setup (amp config/amp test) label Dec 10, 2019
@totten
Copy link
Collaborator

totten commented Dec 10, 2019

... maybe we could have a document/scratchpad/wiki-page with a list of common problems, and then the amp test screen could show a link to that?
Is there such a place?

Eh, not really. Looking at this much later, it may be easier to just keep these things as Github issues and apply a label. I've updated a few with the label environment-detection:

environment-detection Ways to improve guided setup (amp config/amp test)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
environment-detection Ways to improve guided setup (amp config/amp test)
Projects
None yet
Development

No branches or pull requests

3 participants