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

docs: SSH documentation in README and change to web page #314

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

Prodeguerriero
Copy link
Contributor

Hi there!

I hope I am not overstepping any boundaries here. 😁

Here's a changelog:

  • One big linting pass over the README.md file:
    • Markdown lint. Hence, the new .markdownlint.json file
    • LanguageTool lint
  • New section to the README file regarding the “Settings” page
    • Add documentation regarding SSH keys and login password
    • Add heading for “Storage”, but I wouldn't really know what to write in there yet
  • Change the SSH text in the HTML page,

Note that I did not test how the changes to the HTML page will render, as I didn't have an easy way to do so.

Cheers,

@Prodeguerriero
Copy link
Contributor Author

This is related to issue #313

@Prodeguerriero
Copy link
Contributor Author

By the way, given that I can't really contribute much besides documentation, if you want I could review the entire README file and update it.

@@ -40,7 +40,8 @@

<h4>SSH</h4>
<hr>
SSH allows you to access the command line of this machine remotely. Once your SSH public key has been added, you can connect to this server with "ssh {{username}}@{{hostname}}".<br>
To access this machine remotely, add your public SSH key by pasting it in the field below, then click on "Save" at the bottom of the page. If the operation is successful, you'll see your public key appear below the "Add public key" field once tha page reloads. For more details, please refer to <a href="https://github.com/ChimeraOS/chimera/blob/master/README.md">the README file of the Github repository</a>.<br>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My concern with this is that it is too long of a description. Perhaps we could make this message a tooltip/popup?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The rest of this PR is great, so perhaps at the very least, you could split this part out into a separate PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we could make this message a tooltip/popup?

HTML isn't exactly my thing. This was an easy enough edit even without being able to properly preview the end result. I wouldn't know how to make anything prettier than this.
In principle I don't disagree. But I would argue that a longer description doesn't hurt, while someone else works on a nicer implementation.

you could split this part out into a separate PR

Pardon my ignorance, but how would I do that? Make a new commit on this branch that skips this file, and then create a new branch just for this file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could also opt for a middle-of-the-road solution, and go for:

SSH allows you to access the command line of this machine remotely. Once your SSH public key has been added, you can connect to this server with "ssh {{username}}@{{hostname}}".
For more details, please refer to the README file of the Github repository.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could also opt for a middle-of-the-road solution, and go for:

SSH allows you to access the command line of this machine remotely. Once your SSH public key has been added, you can connect to this server with "ssh {{username}}@{{hostname}}".
For more details, please refer to the README file of the Github repository.

Yes, that works.

@@ -4,3 +4,4 @@ __pycache__/
venv/
.pybuild
*.egg-info
*.code-workspace
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alkazar I hope this is not a problem.

@alkazar
Copy link
Member

alkazar commented Oct 16, 2024

Nice work, thank you!

@alkazar alkazar merged commit 30ac2e1 into ChimeraOS:master Oct 16, 2024
1 check passed
@Prodeguerriero Prodeguerriero deleted the wip-ssh-doc branch October 18, 2024 20:51
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

Successfully merging this pull request may close these issues.

2 participants