Skip to content

Conversation

SunFlowerOwl
Copy link

@SunFlowerOwl SunFlowerOwl commented Sep 4, 2025

🛑 New scripts must first be submitted to ProxmoxVED for testing.
PRs for new scripts that skip this process will be closed.


✍️ Description

Create ct maker script
Create installation script
Create web json config file
Add version in version.json
=> Need to create header

🔗 Related PR / Issue

[Script request]: docker-transmission-openvpn => transmission-openvpn #7402
Link: # community-scripts/ProxmoxVE#7402

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No breaking changes – Existing functionality remains intact.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔍 Code & Security Review (X in brackets)

  • Follows Code_Audit.md & CONTRIBUTING.md guidelines
  • Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
  • No hardcoded credentials

📋 Additional Information (optional)

I could not test with my fork because of hardcoded url referencing official ProxmoxVED.

@CrazyWolf13
Copy link
Member

@SunFlowerOwl Why do you request a review from me?
You didn't make a single commit to adress the problems I reviewed.

@SunFlowerOwl
Copy link
Author

@SunFlowerOwl Why do you request a review from me? You didn't make a single commit to adress the problems I reviewed.

As I was preparing my upcoming push, I was looking for a feature that would let me list remarks and show the corresponding code that resolves them, instead of just marking them as resolved after the push. Since this is my first ever pull request on GitHub, I thought that button was for that purpose — but I later realized it wasn’t, and it sent you a re-review request without confirmation and with no way to cancel. Sorry about that.

The push is coming soon; I just need to fix some issues with the cron job after testing on my Proxmox installation.

@CrazyWolf13
Copy link
Member

alright, sure no worries ^^

@CrazyWolf13
Copy link
Member

@SunFlowerOwl please mark the review commands that you believe you solved as resolved.

@SunFlowerOwl
Copy link
Author

@SunFlowerOwl please mark the review commands that you believe you solved as resolved.

Alright, I was unsure if it was on my side.

alright, sure no worries ^^

^^ sometimes curiosity

@SunFlowerOwl
Copy link
Author

SunFlowerOwl commented Sep 7, 2025

✅ Test Checklist

  • Container installs without errors
  • /dev/net/tun automatically added to LXC container at installation
  • Update function works → upgrade without loss of config or data
  • VPN connection established and public IP masked
  • ⚠️ Access to Transmission UI (port 9091) 🚨 Not working because with release it look for transmission bin in usr/local/bin/
  • Access to Privoxy (port 8118) => Not working sometimes
  • Testing Web UI

@SunFlowerOwl
Copy link
Author

✅ Test Checklist

  • Container installs without errors
  • /dev/net/tun automatically added to LXC container at installation
  • Update function works → upgrade without loss of config or data
  • VPN connection established and public IP masked
  • Access to Transmission UI (port 9091) (Custom config for a Cyberghost provider)
  • Access to Privoxy (port 8118)
  • Testing Web UI

@tremor021
Copy link
Member

I'm sorry, i just realised, while doing some checks on the repositories you pull from. These are apps without a commit in 6 or more years. I can't allow such apps to be included in our repo, if nothing else but for security reasons.

@community-scripts/contributor

@SunFlowerOwl
Copy link
Author

SunFlowerOwl commented Sep 13, 2025

sorry, i just realised, while doing some checks on the repositories you pull from. These are apps without a commit in 6 or more years. I can't allow such apps to be included in our repo, if nothing else but for security reasons.

@community-scripts/contributor

Hi,

Thank you for your multiple review with @CrazyWolf13 ,

I think you’re talking about the Transmission UI. No worries... I was also surprised. That may explain why they don’t have a release repo on their GitHub. For me, these WebUIs are not mandatory, and the original Transmission UI is more than enough to make it work. I can remove them if you think it could be acceptable without.

@SunFlowerOwl
Copy link
Author

SunFlowerOwl commented Sep 13, 2025

@tremor021 I’ve removed them all, and I think it’s better this way since the WebUIs are only cosmetic. The main app itself hasn’t received any commits for three months. Is that acceptable for you?

Just to let you know: The UIs are still compatible, but users will need to add them on their own and at their own risk.

✅ Test Checklist

  • Container installs without errors
  • /dev/net/tun automatically added to LXC container at installation
  • Update function works → upgrade without loss of config or data
  • VPN connection established and public IP masked
  • Access to Transmission UI (port 9091) (Custom config for a Cyberghost provider)
  • Access to Privoxy (port 8118)

TRANSMISSION_RATIO_LIMIT_ENABLED="true"
TRANSMISSION_RATIO_LIMIT="0"
TRANSMISSION_RPC_WHITELIST_ENABLED="false"
TRANSMISSION_RPC_WHITELIST="127.0.0.1,192.168.*.*"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldnt that include all private Networks (10.0.0.0/8 and 172.16.0.0/12)?

Copy link
Author

@SunFlowerOwl SunFlowerOwl Sep 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have to admit that I’m not a network expert, and I don’t know the specific details of these IP addresses. However, I think it depends on your network configuration. What I’m providing here is just a minimal configuration to access the main application on a standard local network.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my point of view, it may be unconventional, and it should be left to users as a custom configuration if they want more. But I may be wrong.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont know either, but i have a 10.0.0.0/8 address range in my lan. would this work out of the box for me or not?
This is the spirit of the script. keep the configs minimal, but also it should run by default for anyone. Can you check that pls?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants