Update panel-setup.mdx

[Azim]

need to run setup as root

Summary by CodeRabbit

• Documentation
  • Updated panel setup documentation to reflect the required elevated privileges for the environment setup command.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

A documentation update modifying the command example in the panel setup guide by adding the sudo prefix to the PHP artisan command for environment setup configuration.

Changes

Cohort / File(s)	Summary
Documentation Updates docs/panel/panel-setup.mdx	Added sudo prefix to the php artisan p:environment:setup command example for proper privilege escalation

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A tiny tweak, so swift and clean,
Just "sudo" to be clearly seen,
The path to setup, now precise—
One word made docs so very nice! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update panel-setup.mdx' is vague and non-descriptive; it only mentions the file name without conveying what substantive change was made or why.	Use a more descriptive title like 'Add sudo requirement to panel setup command' to clearly indicate the specific change and its purpose.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	d5a342e
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/694b0a7331c1bf00081308f7
😎 Deploy Preview	https://deploy-preview-182--pelica.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Azim]

according to @notAreYouScared on discord, this needs to be ran as root for the setup to work.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 019f49e and d5a342e.

📒 Files selected for processing (1)

• docs/panel/panel-setup.mdx

🔇 Additional comments (1)

docs/panel/panel-setup.mdx (1)

13-13: The documented approach for Pelican panel installation is correct. Using sudo php artisan p:environment:setup is the recommended method, and the subsequent chown commands (lines 33, 38, 43) properly transfer ownership to the web server user after the artisan setup command creates the .env file with root ownership. This three-step workflow—setup with sudo, set permissions, then change ownership to the web server user—is consistently applied throughout the installation documentation and is the intended process.