podman documentation

[m3ow-dev]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive guide for deploying the Panel with Rootless Podman using Quadlets, covering prerequisites, configuration, systemd integration, SELinux handling, startup, maintenance, verification, logs, and data management.
  • Added Podman-specific configuration guidance for Wings, including tmp directory changes, permissions/SELinux remediation, service unit examples, and an OOM-killer note.
  • Added new Advanced docs navigation entry.

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

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	b5ab719
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/6941bc2fc819ce0008a0a4fe
😎 Deploy Preview	https://deploy-preview-179--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.

[coderabbitai]

Walkthrough

Adds new Podman deployment documentation and updates Wings Podman guidance, plus a sidebar entry linking the new Podman doc; changes are documentation-only and do not modify runtime code or public APIs.

Changes

Cohort / File(s)	Summary
Podman Deployment Documentation docs/panel/advanced/podman.mdx	New full guide for deploying the Pelican Panel with Rootless Podman and Quadlets: prerequisites, directory/config layouts (Caddyfile, Pod YAML), systemd Quadlet usage, SELinux notes, startup/maintenance, verification, logs, and Podman volumes
Wings Podman Configuration Guide docs/wings/optional-config.mdx	Appended Podman-specific instructions: enabling Podman, changing tmp directory, SELinux/permission remediation, sample Wings systemd unit, restart steps, and OOM killer note for game servers
Documentation Navigation sidebars.ts	Added panel/advanced/podman entry to the Advanced category in the documentation sidebar

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Documentation-only changes across a few files; verify content accuracy and formatting.
• Pay attention to:
  • docs/panel/advanced/podman.mdx for correctness of commands, YAML blocks, and SELinux instructions.
  • docs/wings/optional-config.mdx for the tmp_directory and log_config examples and the custom systemd unit sample.
  • sidebars.ts entry placement and import/path consistency.

Poem

🐰 I dug a doc, neat and sound,
Quadlets planted in Podman ground,
SELinux politely bowed,
Systemd hums soft and proud,
Pelican panel hops around 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'podman documentation' is vague and generic, lacking specificity about what aspect of Podman documentation is being added or modified.	Consider a more descriptive title such as 'Add Podman deployment guide for Pelican Panel' or 'Document rootless Podman setup with Quadlets' to clearly convey the main change.

✅ 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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2bd8c03 and b5ab719.

📒 Files selected for processing (1)

• docs/panel/advanced/podman.mdx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/panel/advanced/podman.mdx

---

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.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (2)

docs/wings/optional-config.mdx (2)

183-183: Add space after # in shell comment.

Shell comments should have a space after the # for better readability, following standard shell scripting conventions.

Apply this diff:

-#Chown to the pelican's uid+# Chown to the pelican's uid

---

209-210: Provide more context for the OOM killer requirement.

The statement that "OOM killer must always be enabled... or else the wings will crash" is critical but lacks explanation. Consider adding:

• Why this is a Podman-specific requirement
• Where in the game server settings this is configured
• What causes Wings to crash without it

Consider expanding this to:

### Important for Podman: OOM Killer Configuration
The OOM (Out-of-Memory) killer must always be enabled in the game servers' settings when using Podman. Without it, Wings will crash on server start due to [brief technical reason].
To configure this:
1.[Step-by-step instructions or link to relevant panel settings]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 274ddb6 and 2bd8c03.

📒 Files selected for processing (3)

• docs/panel/advanced/podman.mdx (1 hunks)
• docs/wings/optional-config.mdx (1 hunks)
• sidebars.ts (1 hunks)

🔇 Additional comments (1)

sidebars.ts (1)

34-34: LGTM!

The sidebar entry is correctly added to the Advanced category and follows the existing structure.

[notAreYouScared]

Please address the conflicts

[m3ow-dev]

I dont think the pelican panel project is going to incorporate podman natively soon, meaning i will close this issue until the project is out of beta.

[parkervcp]

@m3ow-dev I am not against podman support. Keeping this around as a draft that you can update while the panel goes through changes may be a better idea.

[m3ow-dev]

All good, will continue to develop on this podman integration documentation

[m3ow-dev]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive guide for deploying the Panel with Rootless Podman using Quadlets, covering prerequisites, configuration, systemd integration, SELinux handling, startup, maintenance, verification, logs, and data management.
  • Added Podman-specific configuration guidance for Wings, including tmp directory changes, permissions/SELinux remediation, service unit examples, and an OOM-killer note.
  • Added new Advanced docs navigation entry.

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

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	b5ab719
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/6941bc2fc819ce0008a0a4fe
😎 Deploy Preview	https://deploy-preview-179--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.

[coderabbitai]

Walkthrough

Adds new Podman deployment documentation and updates Wings Podman guidance, plus a sidebar entry linking the new Podman doc; changes are documentation-only and do not modify runtime code or public APIs.

Changes

Cohort / File(s)	Summary
Podman Deployment Documentation docs/panel/advanced/podman.mdx	New full guide for deploying the Pelican Panel with Rootless Podman and Quadlets: prerequisites, directory/config layouts (Caddyfile, Pod YAML), systemd Quadlet usage, SELinux notes, startup/maintenance, verification, logs, and Podman volumes
Wings Podman Configuration Guide docs/wings/optional-config.mdx	Appended Podman-specific instructions: enabling Podman, changing tmp directory, SELinux/permission remediation, sample Wings systemd unit, restart steps, and OOM killer note for game servers
Documentation Navigation sidebars.ts	Added panel/advanced/podman entry to the Advanced category in the documentation sidebar

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Documentation-only changes across a few files; verify content accuracy and formatting.
• Pay attention to:
  • docs/panel/advanced/podman.mdx for correctness of commands, YAML blocks, and SELinux instructions.
  • docs/wings/optional-config.mdx for the tmp_directory and log_config examples and the custom systemd unit sample.
  • sidebars.ts entry placement and import/path consistency.

Poem

🐰 I dug a doc, neat and sound,
Quadlets planted in Podman ground,
SELinux politely bowed,
Systemd hums soft and proud,
Pelican panel hops around 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'podman documentation' is vague and generic, lacking specificity about what aspect of Podman documentation is being added or modified.	Consider a more descriptive title such as 'Add Podman deployment guide for Pelican Panel' or 'Document rootless Podman setup with Quadlets' to clearly convey the main change.

✅ 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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2bd8c03 and b5ab719.

📒 Files selected for processing (1)

• docs/panel/advanced/podman.mdx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/panel/advanced/podman.mdx

---

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.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (2)

docs/wings/optional-config.mdx (2)

183-183: Add space after # in shell comment.

Shell comments should have a space after the # for better readability, following standard shell scripting conventions.

Apply this diff:

-#Chown to the pelican's uid+# Chown to the pelican's uid

---

209-210: Provide more context for the OOM killer requirement.

The statement that "OOM killer must always be enabled... or else the wings will crash" is critical but lacks explanation. Consider adding:

• Why this is a Podman-specific requirement
• Where in the game server settings this is configured
• What causes Wings to crash without it

Consider expanding this to:

### Important for Podman: OOM Killer Configuration
The OOM (Out-of-Memory) killer must always be enabled in the game servers' settings when using Podman. Without it, Wings will crash on server start due to [brief technical reason].
To configure this:
1.[Step-by-step instructions or link to relevant panel settings]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 274ddb6 and 2bd8c03.

📒 Files selected for processing (3)

• docs/panel/advanced/podman.mdx (1 hunks)
• docs/wings/optional-config.mdx (1 hunks)
• sidebars.ts (1 hunks)

🔇 Additional comments (1)

sidebars.ts (1)

34-34: LGTM!

The sidebar entry is correctly added to the Advanced category and follows the existing structure.

[notAreYouScared]

Please address the conflicts

[m3ow-dev]

I dont think the pelican panel project is going to incorporate podman natively soon, meaning i will close this issue until the project is out of beta.

[parkervcp]

@m3ow-dev I am not against podman support. Keeping this around as a draft that you can update while the panel goes through changes may be a better idea.

[m3ow-dev]

All good, will continue to develop on this podman integration documentation

[m3ow-dev]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive guide for deploying the Panel with Rootless Podman using Quadlets, covering prerequisites, configuration, systemd integration, SELinux handling, startup, maintenance, verification, logs, and data management.
  • Added Podman-specific configuration guidance for Wings, including tmp directory changes, permissions/SELinux remediation, service unit examples, and an OOM-killer note.
  • Added new Advanced docs navigation entry.

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

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	b5ab719
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/6941bc2fc819ce0008a0a4fe
😎 Deploy Preview	https://deploy-preview-179--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.

[coderabbitai]

Walkthrough

Adds new Podman deployment documentation and updates Wings Podman guidance, plus a sidebar entry linking the new Podman doc; changes are documentation-only and do not modify runtime code or public APIs.

Changes

Cohort / File(s)	Summary
Podman Deployment Documentation docs/panel/advanced/podman.mdx	New full guide for deploying the Pelican Panel with Rootless Podman and Quadlets: prerequisites, directory/config layouts (Caddyfile, Pod YAML), systemd Quadlet usage, SELinux notes, startup/maintenance, verification, logs, and Podman volumes
Wings Podman Configuration Guide docs/wings/optional-config.mdx	Appended Podman-specific instructions: enabling Podman, changing tmp directory, SELinux/permission remediation, sample Wings systemd unit, restart steps, and OOM killer note for game servers
Documentation Navigation sidebars.ts	Added panel/advanced/podman entry to the Advanced category in the documentation sidebar

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Documentation-only changes across a few files; verify content accuracy and formatting.
• Pay attention to:
  • docs/panel/advanced/podman.mdx for correctness of commands, YAML blocks, and SELinux instructions.
  • docs/wings/optional-config.mdx for the tmp_directory and log_config examples and the custom systemd unit sample.
  • sidebars.ts entry placement and import/path consistency.

Poem

🐰 I dug a doc, neat and sound,
Quadlets planted in Podman ground,
SELinux politely bowed,
Systemd hums soft and proud,
Pelican panel hops around 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'podman documentation' is vague and generic, lacking specificity about what aspect of Podman documentation is being added or modified.	Consider a more descriptive title such as 'Add Podman deployment guide for Pelican Panel' or 'Document rootless Podman setup with Quadlets' to clearly convey the main change.

✅ 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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2bd8c03 and b5ab719.

📒 Files selected for processing (1)

• docs/panel/advanced/podman.mdx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/panel/advanced/podman.mdx

---

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.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (2)

docs/wings/optional-config.mdx (2)

183-183: Add space after # in shell comment.

Shell comments should have a space after the # for better readability, following standard shell scripting conventions.

Apply this diff:

-#Chown to the pelican's uid+# Chown to the pelican's uid

---

209-210: Provide more context for the OOM killer requirement.

The statement that "OOM killer must always be enabled... or else the wings will crash" is critical but lacks explanation. Consider adding:

• Why this is a Podman-specific requirement
• Where in the game server settings this is configured
• What causes Wings to crash without it

Consider expanding this to:

### Important for Podman: OOM Killer Configuration
The OOM (Out-of-Memory) killer must always be enabled in the game servers' settings when using Podman. Without it, Wings will crash on server start due to [brief technical reason].
To configure this:
1.[Step-by-step instructions or link to relevant panel settings]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 274ddb6 and 2bd8c03.

📒 Files selected for processing (3)

• docs/panel/advanced/podman.mdx (1 hunks)
• docs/wings/optional-config.mdx (1 hunks)
• sidebars.ts (1 hunks)

🔇 Additional comments (1)

sidebars.ts (1)

34-34: LGTM!

The sidebar entry is correctly added to the Advanced category and follows the existing structure.

[notAreYouScared]

Please address the conflicts

[m3ow-dev]

I dont think the pelican panel project is going to incorporate podman natively soon, meaning i will close this issue until the project is out of beta.

[parkervcp]

@m3ow-dev I am not against podman support. Keeping this around as a draft that you can update while the panel goes through changes may be a better idea.

[m3ow-dev]

All good, will continue to develop on this podman integration documentation

[m3ow-dev]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive guide for deploying the Panel with Rootless Podman using Quadlets, covering prerequisites, configuration, systemd integration, SELinux handling, startup, maintenance, verification, logs, and data management.
  • Added Podman-specific configuration guidance for Wings, including tmp directory changes, permissions/SELinux remediation, service unit examples, and an OOM-killer note.
  • Added new Advanced docs navigation entry.

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

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	b5ab719
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/6941bc2fc819ce0008a0a4fe
😎 Deploy Preview	https://deploy-preview-179--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.

[coderabbitai]

Walkthrough

Adds new Podman deployment documentation and updates Wings Podman guidance, plus a sidebar entry linking the new Podman doc; changes are documentation-only and do not modify runtime code or public APIs.

Changes

Cohort / File(s)	Summary
Podman Deployment Documentation docs/panel/advanced/podman.mdx	New full guide for deploying the Pelican Panel with Rootless Podman and Quadlets: prerequisites, directory/config layouts (Caddyfile, Pod YAML), systemd Quadlet usage, SELinux notes, startup/maintenance, verification, logs, and Podman volumes
Wings Podman Configuration Guide docs/wings/optional-config.mdx	Appended Podman-specific instructions: enabling Podman, changing tmp directory, SELinux/permission remediation, sample Wings systemd unit, restart steps, and OOM killer note for game servers
Documentation Navigation sidebars.ts	Added panel/advanced/podman entry to the Advanced category in the documentation sidebar

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Documentation-only changes across a few files; verify content accuracy and formatting.
• Pay attention to:
  • docs/panel/advanced/podman.mdx for correctness of commands, YAML blocks, and SELinux instructions.
  • docs/wings/optional-config.mdx for the tmp_directory and log_config examples and the custom systemd unit sample.
  • sidebars.ts entry placement and import/path consistency.

Poem

🐰 I dug a doc, neat and sound,
Quadlets planted in Podman ground,
SELinux politely bowed,
Systemd hums soft and proud,
Pelican panel hops around 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'podman documentation' is vague and generic, lacking specificity about what aspect of Podman documentation is being added or modified.	Consider a more descriptive title such as 'Add Podman deployment guide for Pelican Panel' or 'Document rootless Podman setup with Quadlets' to clearly convey the main change.

✅ 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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2bd8c03 and b5ab719.

📒 Files selected for processing (1)

• docs/panel/advanced/podman.mdx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/panel/advanced/podman.mdx

---

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.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (2)

docs/wings/optional-config.mdx (2)

183-183: Add space after # in shell comment.

Shell comments should have a space after the # for better readability, following standard shell scripting conventions.

Apply this diff:

-#Chown to the pelican's uid+# Chown to the pelican's uid

---

209-210: Provide more context for the OOM killer requirement.

The statement that "OOM killer must always be enabled... or else the wings will crash" is critical but lacks explanation. Consider adding:

• Why this is a Podman-specific requirement
• Where in the game server settings this is configured
• What causes Wings to crash without it

Consider expanding this to:

### Important for Podman: OOM Killer Configuration
The OOM (Out-of-Memory) killer must always be enabled in the game servers' settings when using Podman. Without it, Wings will crash on server start due to [brief technical reason].
To configure this:
1.[Step-by-step instructions or link to relevant panel settings]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 274ddb6 and 2bd8c03.

📒 Files selected for processing (3)

• docs/panel/advanced/podman.mdx (1 hunks)
• docs/wings/optional-config.mdx (1 hunks)
• sidebars.ts (1 hunks)

🔇 Additional comments (1)

sidebars.ts (1)

34-34: LGTM!

The sidebar entry is correctly added to the Advanced category and follows the existing structure.

[notAreYouScared]

Please address the conflicts

[m3ow-dev]

I dont think the pelican panel project is going to incorporate podman natively soon, meaning i will close this issue until the project is out of beta.

[parkervcp]

@m3ow-dev I am not against podman support. Keeping this around as a draft that you can update while the panel goes through changes may be a better idea.

[m3ow-dev]

All good, will continue to develop on this podman integration documentation

[m3ow-dev]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive guide for deploying the Panel with Rootless Podman using Quadlets, covering prerequisites, configuration, systemd integration, SELinux handling, startup, maintenance, verification, logs, and data management.
  • Added Podman-specific configuration guidance for Wings, including tmp directory changes, permissions/SELinux remediation, service unit examples, and an OOM-killer note.
  • Added new Advanced docs navigation entry.

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

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	b5ab719
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/6941bc2fc819ce0008a0a4fe
😎 Deploy Preview	https://deploy-preview-179--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.

[coderabbitai]

Walkthrough

Adds new Podman deployment documentation and updates Wings Podman guidance, plus a sidebar entry linking the new Podman doc; changes are documentation-only and do not modify runtime code or public APIs.

Changes

Cohort / File(s)	Summary
Podman Deployment Documentation docs/panel/advanced/podman.mdx	New full guide for deploying the Pelican Panel with Rootless Podman and Quadlets: prerequisites, directory/config layouts (Caddyfile, Pod YAML), systemd Quadlet usage, SELinux notes, startup/maintenance, verification, logs, and Podman volumes
Wings Podman Configuration Guide docs/wings/optional-config.mdx	Appended Podman-specific instructions: enabling Podman, changing tmp directory, SELinux/permission remediation, sample Wings systemd unit, restart steps, and OOM killer note for game servers
Documentation Navigation sidebars.ts	Added panel/advanced/podman entry to the Advanced category in the documentation sidebar

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Documentation-only changes across a few files; verify content accuracy and formatting.
• Pay attention to:
  • docs/panel/advanced/podman.mdx for correctness of commands, YAML blocks, and SELinux instructions.
  • docs/wings/optional-config.mdx for the tmp_directory and log_config examples and the custom systemd unit sample.
  • sidebars.ts entry placement and import/path consistency.

Poem

🐰 I dug a doc, neat and sound,
Quadlets planted in Podman ground,
SELinux politely bowed,
Systemd hums soft and proud,
Pelican panel hops around 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'podman documentation' is vague and generic, lacking specificity about what aspect of Podman documentation is being added or modified.	Consider a more descriptive title such as 'Add Podman deployment guide for Pelican Panel' or 'Document rootless Podman setup with Quadlets' to clearly convey the main change.

✅ 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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2bd8c03 and b5ab719.

📒 Files selected for processing (1)

• docs/panel/advanced/podman.mdx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/panel/advanced/podman.mdx

---

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.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (2)

docs/wings/optional-config.mdx (2)

183-183: Add space after # in shell comment.

Shell comments should have a space after the # for better readability, following standard shell scripting conventions.

Apply this diff:

-#Chown to the pelican's uid+# Chown to the pelican's uid

---

209-210: Provide more context for the OOM killer requirement.

The statement that "OOM killer must always be enabled... or else the wings will crash" is critical but lacks explanation. Consider adding:

• Why this is a Podman-specific requirement
• Where in the game server settings this is configured
• What causes Wings to crash without it

Consider expanding this to:

### Important for Podman: OOM Killer Configuration
The OOM (Out-of-Memory) killer must always be enabled in the game servers' settings when using Podman. Without it, Wings will crash on server start due to [brief technical reason].
To configure this:
1.[Step-by-step instructions or link to relevant panel settings]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 274ddb6 and 2bd8c03.

📒 Files selected for processing (3)

• docs/panel/advanced/podman.mdx (1 hunks)
• docs/wings/optional-config.mdx (1 hunks)
• sidebars.ts (1 hunks)

🔇 Additional comments (1)

sidebars.ts (1)

34-34: LGTM!

The sidebar entry is correctly added to the Advanced category and follows the existing structure.

[notAreYouScared]

Please address the conflicts

[m3ow-dev]

I dont think the pelican panel project is going to incorporate podman natively soon, meaning i will close this issue until the project is out of beta.

[parkervcp]

@m3ow-dev I am not against podman support. Keeping this around as a draft that you can update while the panel goes through changes may be a better idea.

[m3ow-dev]

All good, will continue to develop on this podman integration documentation

[m3ow-dev]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive guide for deploying the Panel with Rootless Podman using Quadlets, covering prerequisites, configuration, systemd integration, SELinux handling, startup, maintenance, verification, logs, and data management.
  • Added Podman-specific configuration guidance for Wings, including tmp directory changes, permissions/SELinux remediation, service unit examples, and an OOM-killer note.
  • Added new Advanced docs navigation entry.

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

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	b5ab719
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/6941bc2fc819ce0008a0a4fe
😎 Deploy Preview	https://deploy-preview-179--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.

[coderabbitai]

Walkthrough

Adds new Podman deployment documentation and updates Wings Podman guidance, plus a sidebar entry linking the new Podman doc; changes are documentation-only and do not modify runtime code or public APIs.

Changes

Cohort / File(s)	Summary
Podman Deployment Documentation docs/panel/advanced/podman.mdx	New full guide for deploying the Pelican Panel with Rootless Podman and Quadlets: prerequisites, directory/config layouts (Caddyfile, Pod YAML), systemd Quadlet usage, SELinux notes, startup/maintenance, verification, logs, and Podman volumes
Wings Podman Configuration Guide docs/wings/optional-config.mdx	Appended Podman-specific instructions: enabling Podman, changing tmp directory, SELinux/permission remediation, sample Wings systemd unit, restart steps, and OOM killer note for game servers
Documentation Navigation sidebars.ts	Added panel/advanced/podman entry to the Advanced category in the documentation sidebar

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Documentation-only changes across a few files; verify content accuracy and formatting.
• Pay attention to:
  • docs/panel/advanced/podman.mdx for correctness of commands, YAML blocks, and SELinux instructions.
  • docs/wings/optional-config.mdx for the tmp_directory and log_config examples and the custom systemd unit sample.
  • sidebars.ts entry placement and import/path consistency.

Poem

🐰 I dug a doc, neat and sound,
Quadlets planted in Podman ground,
SELinux politely bowed,
Systemd hums soft and proud,
Pelican panel hops around 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'podman documentation' is vague and generic, lacking specificity about what aspect of Podman documentation is being added or modified.	Consider a more descriptive title such as 'Add Podman deployment guide for Pelican Panel' or 'Document rootless Podman setup with Quadlets' to clearly convey the main change.

✅ 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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2bd8c03 and b5ab719.

📒 Files selected for processing (1)

• docs/panel/advanced/podman.mdx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/panel/advanced/podman.mdx

---

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.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (2)

docs/wings/optional-config.mdx (2)

183-183: Add space after # in shell comment.

Shell comments should have a space after the # for better readability, following standard shell scripting conventions.

Apply this diff:

-#Chown to the pelican's uid+# Chown to the pelican's uid

---

209-210: Provide more context for the OOM killer requirement.

The statement that "OOM killer must always be enabled... or else the wings will crash" is critical but lacks explanation. Consider adding:

• Why this is a Podman-specific requirement
• Where in the game server settings this is configured
• What causes Wings to crash without it

Consider expanding this to:

### Important for Podman: OOM Killer Configuration
The OOM (Out-of-Memory) killer must always be enabled in the game servers' settings when using Podman. Without it, Wings will crash on server start due to [brief technical reason].
To configure this:
1.[Step-by-step instructions or link to relevant panel settings]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 274ddb6 and 2bd8c03.

📒 Files selected for processing (3)

• docs/panel/advanced/podman.mdx (1 hunks)
• docs/wings/optional-config.mdx (1 hunks)
• sidebars.ts (1 hunks)

🔇 Additional comments (1)

sidebars.ts (1)

34-34: LGTM!

The sidebar entry is correctly added to the Advanced category and follows the existing structure.

[notAreYouScared]

Please address the conflicts

[m3ow-dev]

I dont think the pelican panel project is going to incorporate podman natively soon, meaning i will close this issue until the project is out of beta.

[parkervcp]

@m3ow-dev I am not against podman support. Keeping this around as a draft that you can update while the panel goes through changes may be a better idea.

[m3ow-dev]

All good, will continue to develop on this podman integration documentation

[m3ow-dev]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive guide for deploying the Panel with Rootless Podman using Quadlets, covering prerequisites, configuration, systemd integration, SELinux handling, startup, maintenance, verification, logs, and data management.
  • Added Podman-specific configuration guidance for Wings, including tmp directory changes, permissions/SELinux remediation, service unit examples, and an OOM-killer note.
  • Added new Advanced docs navigation entry.

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

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	b5ab719
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/6941bc2fc819ce0008a0a4fe
😎 Deploy Preview	https://deploy-preview-179--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.

[coderabbitai]

Walkthrough

Adds new Podman deployment documentation and updates Wings Podman guidance, plus a sidebar entry linking the new Podman doc; changes are documentation-only and do not modify runtime code or public APIs.

Changes

Cohort / File(s)	Summary
Podman Deployment Documentation docs/panel/advanced/podman.mdx	New full guide for deploying the Pelican Panel with Rootless Podman and Quadlets: prerequisites, directory/config layouts (Caddyfile, Pod YAML), systemd Quadlet usage, SELinux notes, startup/maintenance, verification, logs, and Podman volumes
Wings Podman Configuration Guide docs/wings/optional-config.mdx	Appended Podman-specific instructions: enabling Podman, changing tmp directory, SELinux/permission remediation, sample Wings systemd unit, restart steps, and OOM killer note for game servers
Documentation Navigation sidebars.ts	Added panel/advanced/podman entry to the Advanced category in the documentation sidebar

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Documentation-only changes across a few files; verify content accuracy and formatting.
• Pay attention to:
  • docs/panel/advanced/podman.mdx for correctness of commands, YAML blocks, and SELinux instructions.
  • docs/wings/optional-config.mdx for the tmp_directory and log_config examples and the custom systemd unit sample.
  • sidebars.ts entry placement and import/path consistency.

Poem

🐰 I dug a doc, neat and sound,
Quadlets planted in Podman ground,
SELinux politely bowed,
Systemd hums soft and proud,
Pelican panel hops around 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'podman documentation' is vague and generic, lacking specificity about what aspect of Podman documentation is being added or modified.	Consider a more descriptive title such as 'Add Podman deployment guide for Pelican Panel' or 'Document rootless Podman setup with Quadlets' to clearly convey the main change.

✅ 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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2bd8c03 and b5ab719.

📒 Files selected for processing (1)

• docs/panel/advanced/podman.mdx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/panel/advanced/podman.mdx

---

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.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (2)

docs/wings/optional-config.mdx (2)

183-183: Add space after # in shell comment.

Shell comments should have a space after the # for better readability, following standard shell scripting conventions.

Apply this diff:

-#Chown to the pelican's uid+# Chown to the pelican's uid

---

209-210: Provide more context for the OOM killer requirement.

The statement that "OOM killer must always be enabled... or else the wings will crash" is critical but lacks explanation. Consider adding:

• Why this is a Podman-specific requirement
• Where in the game server settings this is configured
• What causes Wings to crash without it

Consider expanding this to:

### Important for Podman: OOM Killer Configuration
The OOM (Out-of-Memory) killer must always be enabled in the game servers' settings when using Podman. Without it, Wings will crash on server start due to [brief technical reason].
To configure this:
1.[Step-by-step instructions or link to relevant panel settings]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 274ddb6 and 2bd8c03.

📒 Files selected for processing (3)

• docs/panel/advanced/podman.mdx (1 hunks)
• docs/wings/optional-config.mdx (1 hunks)
• sidebars.ts (1 hunks)

🔇 Additional comments (1)

sidebars.ts (1)

34-34: LGTM!

The sidebar entry is correctly added to the Advanced category and follows the existing structure.

[notAreYouScared]

Please address the conflicts

[m3ow-dev]

I dont think the pelican panel project is going to incorporate podman natively soon, meaning i will close this issue until the project is out of beta.

[parkervcp]

@m3ow-dev I am not against podman support. Keeping this around as a draft that you can update while the panel goes through changes may be a better idea.

[m3ow-dev]

All good, will continue to develop on this podman integration documentation

[m3ow-dev]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive guide for deploying the Panel with Rootless Podman using Quadlets, covering prerequisites, configuration, systemd integration, SELinux handling, startup, maintenance, verification, logs, and data management.
  • Added Podman-specific configuration guidance for Wings, including tmp directory changes, permissions/SELinux remediation, service unit examples, and an OOM-killer note.
  • Added new Advanced docs navigation entry.

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

[netlify]

✅ Deploy Preview for pelica ready!

Name	Link
🔨 Latest commit	b5ab719
🔍 Latest deploy log	https://app.netlify.com/projects/pelica/deploys/6941bc2fc819ce0008a0a4fe
😎 Deploy Preview	https://deploy-preview-179--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.

[coderabbitai]

Walkthrough

Adds new Podman deployment documentation and updates Wings Podman guidance, plus a sidebar entry linking the new Podman doc; changes are documentation-only and do not modify runtime code or public APIs.

Changes

Cohort / File(s)	Summary
Podman Deployment Documentation docs/panel/advanced/podman.mdx	New full guide for deploying the Pelican Panel with Rootless Podman and Quadlets: prerequisites, directory/config layouts (Caddyfile, Pod YAML), systemd Quadlet usage, SELinux notes, startup/maintenance, verification, logs, and Podman volumes
Wings Podman Configuration Guide docs/wings/optional-config.mdx	Appended Podman-specific instructions: enabling Podman, changing tmp directory, SELinux/permission remediation, sample Wings systemd unit, restart steps, and OOM killer note for game servers
Documentation Navigation sidebars.ts	Added panel/advanced/podman entry to the Advanced category in the documentation sidebar

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Documentation-only changes across a few files; verify content accuracy and formatting.
• Pay attention to:
  • docs/panel/advanced/podman.mdx for correctness of commands, YAML blocks, and SELinux instructions.
  • docs/wings/optional-config.mdx for the tmp_directory and log_config examples and the custom systemd unit sample.
  • sidebars.ts entry placement and import/path consistency.

Poem

🐰 I dug a doc, neat and sound,
Quadlets planted in Podman ground,
SELinux politely bowed,
Systemd hums soft and proud,
Pelican panel hops around 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'podman documentation' is vague and generic, lacking specificity about what aspect of Podman documentation is being added or modified.	Consider a more descriptive title such as 'Add Podman deployment guide for Pelican Panel' or 'Document rootless Podman setup with Quadlets' to clearly convey the main change.

✅ 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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2bd8c03 and b5ab719.

📒 Files selected for processing (1)

• docs/panel/advanced/podman.mdx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/panel/advanced/podman.mdx

---

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.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (2)

docs/wings/optional-config.mdx (2)

183-183: Add space after # in shell comment.

Shell comments should have a space after the # for better readability, following standard shell scripting conventions.

Apply this diff:

-#Chown to the pelican's uid+# Chown to the pelican's uid

---

209-210: Provide more context for the OOM killer requirement.

The statement that "OOM killer must always be enabled... or else the wings will crash" is critical but lacks explanation. Consider adding:

• Why this is a Podman-specific requirement
• Where in the game server settings this is configured
• What causes Wings to crash without it

Consider expanding this to:

### Important for Podman: OOM Killer Configuration
The OOM (Out-of-Memory) killer must always be enabled in the game servers' settings when using Podman. Without it, Wings will crash on server start due to [brief technical reason].
To configure this:
1.[Step-by-step instructions or link to relevant panel settings]

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 274ddb6 and 2bd8c03.

📒 Files selected for processing (3)

• docs/panel/advanced/podman.mdx (1 hunks)
• docs/wings/optional-config.mdx (1 hunks)
• sidebars.ts (1 hunks)

🔇 Additional comments (1)

sidebars.ts (1)

34-34: LGTM!

The sidebar entry is correctly added to the Advanced category and follows the existing structure.

[notAreYouScared]

Please address the conflicts

[m3ow-dev]

I dont think the pelican panel project is going to incorporate podman natively soon, meaning i will close this issue until the project is out of beta.

[parkervcp]

@m3ow-dev I am not against podman support. Keeping this around as a draft that you can update while the panel goes through changes may be a better idea.

[m3ow-dev]

All good, will continue to develop on this podman integration documentation