[GH-ISSUE #495] Add configurable APT-Cacher-NG (LXC) default proxy option for local helper script installations #143

New issue

Open

opened 2026-02-26 12:40:18 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:40:18 +03:00

Owner

Originally created by @YamonBot on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE-Local/issues/495

🌟 Briefly describe the feature

Add configurable APT-Cacher-NG (LXC) default proxy option for local helper script installations

📝 Detailed description

🚀 Feature Request

I would like to request support for configuring an APT-Cacher-NG instance (running in LXC) as an optional default package proxy for local helper script installations.

Specifically, I want to:

Define the address of an APT-Cacher-NG instance in environment settings.
Control whether locally installed scripts should use that proxy by default.

🧩 Background

In my infrastructure:

APT-Cacher-NG runs inside an LXC container.
It acts as a persistent APT package proxy.
The proxy endpoint is stable and reused across multiple deployments.

Currently, when installing local helper scripts, there is no clean way to:

Define a persistent APT proxy endpoint.
Toggle default proxy usage behavior.

This forces manual edits or environment-specific patching.

🎯 Proposed Solution

1️⃣ Environment-Level Configuration

Allow defining proxy configuration via environment variables (or equivalent configuration system), for example:

APT_PROXY_ADDRESS=10.x.x.x:3142
APT_PROXY_ENABLED=true

2️⃣ Installation-Time Default Behavior Control

During local helper script installation:

If APT_PROXY_ENABLED=true → automatically configure APT to use the specified APT-Cacher-NG instance.
If false → proceed without proxy configuration.

This behavior should be configurable without modifying core installation scripts.

✅ Expected Outcome

A clean and configurable mechanism that:

Accepts an LXC-based APT-Cacher-NG endpoint.
Allows enabling/disabling default usage.
Integrates seamlessly into local helper script installation flow.

💡 Why is this useful?

Improves reproducibility in LXC-based environments.

Reduces repetitive manual configuration.

Makes proxy usage explicit and controllable.

Useful for users operating persistent local infrastructure.

Originally created by @YamonBot on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE-Local/issues/495 ### 🌟 Briefly describe the feature Add configurable APT-Cacher-NG (LXC) default proxy option for local helper script installations ### 📝 Detailed description ## 🚀 Feature Request I would like to request support for configuring an **APT-Cacher-NG instance (running in LXC)** as an optional default package proxy for local helper script installations. Specifically, I want to: 1. Define the address of an `APT-Cacher-NG` instance in environment settings. 2. Control whether locally installed scripts should use that proxy by default. --- ## 🧩 Background In my infrastructure: * `APT-Cacher-NG` runs inside an LXC container. * It acts as a persistent APT package proxy. * The proxy endpoint is stable and reused across multiple deployments. Currently, when installing local helper scripts, there is no clean way to: * Define a persistent APT proxy endpoint. * Toggle default proxy usage behavior. This forces manual edits or environment-specific patching. --- ## 🎯 Proposed Solution ### 1️⃣ Environment-Level Configuration Allow defining proxy configuration via environment variables (or equivalent configuration system), for example: ``` APT_PROXY_ADDRESS=10.x.x.x:3142 APT_PROXY_ENABLED=true ``` --- ### 2️⃣ Installation-Time Default Behavior Control During local helper script installation: * If `APT_PROXY_ENABLED=true` → automatically configure APT to use the specified APT-Cacher-NG instance. * If `false` → proceed without proxy configuration. This behavior should be configurable without modifying core installation scripts. --- ## ✅ Expected Outcome A clean and configurable mechanism that: * Accepts an LXC-based APT-Cacher-NG endpoint. * Allows enabling/disabling default usage. * Integrates seamlessly into local helper script installation flow. ### 💡 Why is this useful? Improves reproducibility in LXC-based environments. Reduces repetitive manual configuration. Makes proxy usage explicit and controllable. Useful for users operating persistent local infrastructure.