After resolving an issue with the default.ovpn symlink, it was bugging me that each time the container ran it would download all of the NordVPN configs. After a bit of research I found a url where I could download just one ovpn file. A bit of rework and now only downloads the applicable config based off of NordVPNs api. No more 4000+ configs.
User can configure this using either NORDVPN_COUNTRY to connect to the best server in that country or a specific config using the OPENVPN_CONFIG parameter. If neither are specified config will be selected based off of NordVPN api and if both are specified it will connect to OPENVPN_CONFIG server first using the api to decide on a backup 'default.ovpn' config in case it fails.
In my rewriting of this I also realised there was no need for the updateConfigs.sh script anymore, but to keep everything in keeping I replaced the contents of the updateConfigs.sh script with the NordVPN_selector one and removed the latter.
container was being stopped due to sed not liking default.ovpn symlink. Updated so that sed skipped this symlink. container was then also being stopped due to updateConfigs.sh script erroring if default.ovpn existed when trying to create symlink. Added option 'f' so that the symlink would be recreated even if existed
Added NordVPN Variables to docker file
Update start.sh
Update NordVPN.sh
Update NordVPN configs on run
NordVPN was missing server files. Have updated to run the nordvpn updateConfigs.sh script on start
Update NordVPN_Server_Selector.sh
Update start.sh
Moved Selector script to NordVPN directory
Update NordVPN_Server_Selector.sh
Update NordVPN_Server_Selector.sh
Update updateConfigs.sh
Update updateConfigs.sh
Added auto-update of NordVPN
container will auto-update NordVPN files on start. This increases the start up time by a bit. But ensures that all configs are present for the auto-selector script
Create default.ovpn
Update default.ovpn
Tom Humphrey