You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Currently, Snipe-IT uses the APP_URL value defined in the .env file (or Docker container) as the base URL for all generated links, including those embedded in QR codes on asset labels. This is limiting for installations where the application runs on an internal IP (e.g. http://192.168.1.100), but where asset labels need to be scannable and accessible externally or separate VLAN for Wifi (e.g. http://public-ip-or-domain).
Proposed Solution:
Introduce a new environment variable (e.g. QR_CODE_URL_OVERRIDE) or an admin-configurable setting that overrides the base URL only for generating QR codes on asset labels. If set, this value would be used instead of APP_URL in the label generation process.
Benefits:
Allows organizations to keep the main web app on a private/internal IP for security while still generating externally usable labels.
Eliminates the need to frequently switch APP_URL manually or patch the codebase.
Improves usability for hybrid deployments where labels are used offsite.
Thank you for considering this feature!
This would greatly improve flexibility for installations that need both internal and external label accessibility.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
Currently, Snipe-IT uses the APP_URL value defined in the .env file (or Docker container) as the base URL for all generated links, including those embedded in QR codes on asset labels. This is limiting for installations where the application runs on an internal IP (e.g. http://192.168.1.100), but where asset labels need to be scannable and accessible externally or separate VLAN for Wifi (e.g. http://public-ip-or-domain).
Proposed Solution:
Introduce a new environment variable (e.g. QR_CODE_URL_OVERRIDE) or an admin-configurable setting that overrides the base URL only for generating QR codes on asset labels. If set, this value would be used instead of APP_URL in the label generation process.
Benefits:
Allows organizations to keep the main web app on a private/internal IP for security while still generating externally usable labels.
Eliminates the need to frequently switch APP_URL manually or patch the codebase.
Improves usability for hybrid deployments where labels are used offsite.
Thank you for considering this feature!
This would greatly improve flexibility for installations that need both internal and external label accessibility.
Beta Was this translation helpful? Give feedback.
All reactions