-
Notifications
You must be signed in to change notification settings - Fork 21
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
marketplace: write instructions for transitioning #447
Conversation
✅ Deploy Preview for grist-help-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
db88f64
to
cfc3223
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With a few more details to help the user's mental model in case of problems (and there are always problems), this is close to fine. I was hoping for instructions that would help with transitioning any single-server setup, with some extra notes for AWS-specific steps, but maybe there isn't enough to say.
The main thing I'd like to see fleshed out is to systematically clue the user in on the default email wrinkle. It is dangerous and confusing to be setting up Grist without knowing what that is about. Feels like it merits a section in the self-managed handbook, rather than a very passing mention in telemetry which is all I see right now? https://support.getgrist.com/self-managed/#how-do-i-control-telemetry
It would be super helpful if you told users that this email will control access to the single team site that gets created for them on first run, and the consequences and symptoms of changing it. And that'll be valuable not only for AWS users but lots of other people.
5e730c2
to
6f2e8de
Compare
* The entire `~/grist-persist/docs` directory | ||
|
||
Also see ["What files does Grist | ||
store?"](../../self-managed#what-files-does-grist-storex) for an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
extra "x" on the URL
The traditional method to copy files across instances is `scp`, a file | ||
transfer mechanism over the SSH protocol. A small complication is that | ||
the user to copy to, `grist` in the target EC2 instance, by default | ||
does not have ssh login enabled. We recommend copying into the default |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"an SSH login" or "an ssh
login"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a couple tiny things
6f2e8de
to
8b2b801
Compare
There are very few users who should ever need to do this, so the instructions are a little sparse on details. I believe this to be an acceptable compromise.