PATH environment for binary of softether about sa-vpn-softether HOT 5 CLOSED

Are you talking about use case for "client" use or "server" use ?

Because on server I just have softether service up, and connect to it mostly via openVPN native software.

from sa-vpn-softether.

i.e. you can submit PR, but in
defaults/main.yml introduce

option_add_to_path=false

and than

- name: SoftEther | Add {{softether_home}} to path
  lineinfile:
    dest: /etc/profile.d/softether.sh
    state: present
    create: yes
    regexp: '^export PATH'
    line: 'export PATH=$PATH:{{softether_home}}'
  become: yes
  when: option_add_to_path
  tags:
    - softether

from sa-vpn-softether.

Sorry, i'm not a expert in git & i failed to make a PR only with this change( it's asking me to push request with all my commit) ...

see the commit here
roumano@f96b613

from sa-vpn-softether.

@roumano

Good time to learn new trick

Step (A)
https://help.github.com/articles/configuring-a-remote-for-a-fork/

See (B)
https://help.github.com/articles/syncing-a-fork/

This is most regular operation you would do, when working with opensource repos via fork

When synced, issue new PR as you did previously.

from sa-vpn-softether.

In other case, our branches will diverge and it will be a way harder to sync back

from sa-vpn-softether.