I would like to suggest an alias feature for Filedrops. My company uses Filedrops and they publish the URL in many places, web, PDFs, printouts, etc. If they request for the URL to change (for whatever reason), then I have to create a new Filedrop with the new desired name, and have to keep the old one around to preserve all previous published URLs. Any future changes to the Filedrop and I have to make changes to both Filedrops (new and old one). An obvious solution to this would be for me to add a redirect in the NGINX configuration, but that has to be performed outside of LiquidFiles, which is undesirable. Also, I am unsure if custom configurations to NGINX are captured in backups. My idea is to add an alias field(s) in the Filedrop configuration so that LiquidFiles could add the redirects to NGINX behind the scene. The alias field should be aware of all other Filedrop names and aliases to prevent duplicate URLs. Thanks, -German
