Add switch to choose between OVPN and conf file extensions #11
Comments
@ezaquarii Hi! I was wondering if you could provide some more input about this issue? First timer here, so I'll probably have a lot of redundant questions, apologies in advance for that. |
Pls see updated ticket description. This will require some work with Python & Django, JavaScript & Vue.js. |
Is anyone working on this still? I'd like to submit a pull request and help out if not. |
Go ahead!
…On June 12, 2019 12:42:34 AM UTC, nhughey ***@***.***> wrote:
Is anyone working on this still? I'd like to submit a pull request and
help out if not.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#11 (comment)
|
I want to take this up as no one else has submitted a PR till now. Also, I've added a draft PR. Please let me know if this is the way you want to fix it. |
Hi, is this feature still free for the taking? Is it still needed? No one took it already? |
When you download (or send) the config file, it has extension
conf
. This works well for Linux, but Mac and Windows users expect profile files to have extensionovpn
. I believe this should be a configurable option.There is couple of things to do.
URL creation:
vpnathome.apps.openvpn.serializers.ClientSerializer
vpnathome.apps.openvpn.serializers.ServerSerializer
Filename is model attribute:
vpnathome.apps.openvpn.models.Client.filename
vpnathome.apps.openvpn.models.Server.filename
Filename generation should be probably moved to serializer and extension injected via context.
Frontend requires another settings page and file extension setting should be added to:
vpnathome.apps.management.models.Settings
.Unit tests are a must.
The text was updated successfully, but these errors were encountered: