-
Notifications
You must be signed in to change notification settings - Fork 16
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
Improve README.md #72
Conversation
README.md
Outdated
- `/opt/socket_vmnet/bin/socket_vmnet` | ||
- `/opt/socket_vmnet/bin/socket_vmnet_client` | ||
|
||
You can customize the install location using the `PREFIX` environmemnt variable, |
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.
The default PREFIX
has to be explained
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.
I can add one example of using PREFIX near this section.
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.
Explained in the previous paragraph now.
@@ -47,6 +46,7 @@ brew install socket_vmnet | |||
``` | |||
|
|||
The binaries will be installed onto the following paths: | |||
|
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.
Is this spacing required by some linter? If so, it should be enforced in the CI
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.
BTW what is the benefit of this spacing style?
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.
We can use yamllint markdownlint to enforce this. I'll add an issue to add it.
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.
The source is more clear. The rendered page looks the same.
We use PRFIX=/opt/socket_vment by default, and we recommend to use the default location for good reasons. Show the recommend commands without the unneeded PREFIX. Mention PREFIX in the next paragraph about avoiding bad locations like /usr/local. Using non-default location introduces the risk of using a directory writable by unprivileged user and complicates lima configuration which defaults to /opt/socket_vmnet. Signed-off-by: Nir Soffer <nsoffer@redhat.com>
- Improve instructions for enabling debug logs - Mention that stdout is not used for logging - Remove HOMEBREW_PREFIX from logs locations since homebrew installation is not recommended. - Remove note about old logs location Fixes: lima-vm#70 Signed-off-by: Nir Soffer <nsoffer@redhat.com>
On managed machines, this happens after every reboot. `/usr/libexec/bootpd` is already part of the firewall and configured to accept incoming connections. Removing it from the firewall and adding it again fixes the issue. On other machines that do not have this issue, removing and adding bootpd from the firewall is not needed but also does not cause any issue. Fixes: lima-vm#62 Signed-off-by: Nir Soffer <nsoffer@redhat.com>
The current syntax works, but the tables looks better when reading the source this way. (Automatic formatting by Zed markdown extension). Signed-off-by: Nir Soffer <nsoffer@redhat.com>
Change done by formatting the file with Zed markdown extension. Not sure why it is better, but using this makes it easier for me to keep the file nicely formatted. Signed-off-by: Nir Soffer <nsoffer@redhat.com>
It is easier to read the source when sections are separated by blank lines. (Automatically formatted by Zed markdown extension). Signed-off-by: Nir Soffer <nsoffer@redhat.com>
Github supports alert extensions which are rendered much nicer. Examples: > [!NOTE] > Highlights information that users should take into account, even when skimming. > [!TIP] > Optional information to help a user be more successful. > [!IMPORTANT] > Crucial information necessary for users to succeed. > [!WARNING] > Critical content demanding immediate user attention due to potential risks. > [!CAUTION] > Negative potential consequences of an action. [1] https://github.com/orgs/community/discussions/16925 Signed-off-by: Nir Soffer <nsoffer@redhat.com>
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.
Thanks
Preview changes