allanger/container-openvpn
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Activity

README: Clarify volume naming convention

Browse Source 
* Use a better default that works with systemd service out of the box.
* Update upstart init script to follow convention.
This commit is contained in:
Kyle Manna 2017-05-10 08:14:51 -07:00
parent 861ed05c48
commit f996bbaa8e
2 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -18,9 +18,12 @@ a corresponding [Digital Ocean Community Tutorial](http://bit.ly/1AGUZkq).
## Quick Start ## Quick Start
* Pick a name for the `$OVPN_DATA` data volume container, it will be created automatically. * Pick a name for the `$OVPN_DATA` data volume container. It's recommended to
use the `ovpn-data-` prefix to operate seamlessly with the reference systemd
service. Users are encourage to replace `example` with a descriptive name of
their choosing.
OVPN_DATA="ovpn-data" OVPN_DATA="ovpn-data-example"
* Initialize the `$OVPN_DATA` container that will hold the configuration files and certificates * Initialize the `$OVPN_DATA` container that will hold the configuration files and certificates

2
init/upstart.init
View File

@ -4,5 +4,5 @@ start on filesystem and started docker
stop on runlevel [!2345] stop on runlevel [!2345]
respawn respawn
script script
exec docker run -v ovpn-data:/etc/openvpn --rm -p 1194:1194/udp --cap-add=NET_ADMIN kylemanna/openvpn exec docker run -v ovpn-data-example:/etc/openvpn --rm -p 1194:1194/udp --cap-add=NET_ADMIN kylemanna/openvpn
end script end script