-
-
Notifications
You must be signed in to change notification settings - Fork 173
Updated Velocity chmod guide #520
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
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
I like the idea of encouraging better habits, maybe we even should actually explain what the command does, i.e. "then run chmod to make the file executable" |
@@ -59,7 +59,7 @@ java -Xms1G -Xmx1G -XX:+UseG1GC -XX:G1HeapRegionSize=4M -XX:+UnlockExperimentalV | |||
|
|||
Once saved, open a terminal (or log into the machine) if you haven't already, navigate to the |
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 like the idea of this PR, maybe a paragraph like this works better though?
Once you've saved the files, open a terminal (or log into the machine) if you haven't already. Navigate to the directory where you have placed the Velocity JAR file and the start.sh
file. Then, you will need to prepare the start.sh script to be executable and run it.
-
Run
chmod u+x start.sh
. This command modifies the file's permissions, granting the file's owner (you) the ability to execute (x) the script. Without this step, the system may not recognize the script as something that can be run. -
Now that the file is executable, run
./start.sh
to run the script.
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.
Since the PR is stale, I decided to apply your suggestion.
Within Linux's chmod system, `+x` grants all users access to execute the file, whereas `u+x` only grants the user who owns the file access to execute it. Provided the user is the one who created the `start.sh` file, there's no reason why this permission change wouldn't cause issues, but it's good to get into the habit of using "least privilege" when assigning permissions, and I know from personal experience that hosting Minecraft servers can be the start of a career in sysadmining.
Within Linux's chmod system,
+x
grants all users access to execute the file, whereasu+x
only grants the user who owns the file access to execute it. Provided the user is the one who created thestart.sh
file, there's no reason why this permission change wouldn't cause issues, but it's good to get into the habit of using "least privilege" when assigning permissions, and I know from personal experience that hosting Minecraft servers can be the start of a career in sysadmining.