From 0ef5a1f7a0aed81019af2314f482fa11953aea8b Mon Sep 17 00:00:00 2001 From: Nathan Date: Thu, 9 Jan 2025 22:58:23 +0000 Subject: [PATCH 1/2] Updated chmod permission 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. --- .../docs/velocity/admin/getting-started/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/velocity/admin/getting-started/getting-started.md b/src/content/docs/velocity/admin/getting-started/getting-started.md index 9ac57b86f..c3f1d68ef 100644 --- a/src/content/docs/velocity/admin/getting-started/getting-started.md +++ b/src/content/docs/velocity/admin/getting-started/getting-started.md @@ -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 directory where you have placed the Velocity JAR file and the `start.sh` file. Then run -`chmod +x start.sh` and then `./start.sh`. If it worked, you should now receive a console similar to +`chmod u+x start.sh` and then `./start.sh`. If it worked, you should now receive a console similar to the output in the next section. ## After launch From 519a39e081d4af1dfa90e2c4f26e84fc13c4a8cd Mon Sep 17 00:00:00 2001 From: Strokkur424 Date: Tue, 5 Aug 2025 12:51:13 +0200 Subject: [PATCH 2/2] Apply suggestions --- .../velocity/admin/getting-started/getting-started.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/src/content/docs/velocity/admin/getting-started/getting-started.md b/src/content/docs/velocity/admin/getting-started/getting-started.md index c3f1d68ef..a32809812 100644 --- a/src/content/docs/velocity/admin/getting-started/getting-started.md +++ b/src/content/docs/velocity/admin/getting-started/getting-started.md @@ -57,10 +57,13 @@ host. java -Xms1G -Xmx1G -XX:+UseG1GC -XX:G1HeapRegionSize=4M -XX:+UnlockExperimentalVMOptions -XX:+ParallelRefProcEnabled -XX:+AlwaysPreTouch -XX:MaxInlineLevel=15 -jar velocity*.jar ``` -Once saved, 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 run -`chmod u+x start.sh` and then `./start.sh`. If it worked, you should now receive a console similar to -the output in the next section. +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 for it to be executable and run it. + +1. 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. +1. Now that the file is executable, run `./start.sh` to run the script. ## After launch