EasyRSA Generation including environment variables to set parameters

[ClashTheBunny]

Hi there,
I've been working on some improvements to dockvpn. There is a new master helper script call 'runDockVPN.sh'. It currently creates a volume only container, as suggested in:
http://docs.docker.io/use/working_with_volumes/
that containes the /etc/openvpn configuration files, so that they survive between runs.

In that directory is created an EasyRSA CA from the environment variables that you pass to it. (edit runDockVPN.sh)

The configuration files are compatible with:
TunnelBlick, NetworkManager, Android and iPhone OpenVPN connect, and anything else you can imagine, I'm sure.

It then starts up on the ports that you request and spits out the directory on the docker server where your config files are stored. Those can either be rsync'd with the command in the README or using docker's exporting of volumes.

Currently broken is the auto-hosting of the VPN config file because I no longer create the server pem like previously.

It may need some cleaning up, but it works on my amd64 and armel boxes as long as you are willing to rsync the ovpn config files down. This, after all is more of a security feature than a bug, but it may be harder to get the file on one's phone.

This is my first fully functioning Docker project, so thanks so much for a starting place!

Randall Mason

[paimpozhil]

@jpetazzo this looks interesting please give a look at this PR 👍

[jpetazzo]

Hi @ClashTheBunny, sorry, I couldn't review that earlier (such a big pull request scared me :-))

I'm afraid that I won't have enough time to review it properly, but I see that you have put a lot of work in it. Maybe I should tag the current version as 0.1, then merge your PR into master?

I wish there were a "survival guide for the open source maintainer that can't commit to maintain all his stuff" :-o

[ClashTheBunny]

There are other good branches of your initial great work. This does make
great progress, and I use it daily, but we could work on some design ideas
to combine all of them and end up with something better than this PR. This
would also probably be a good starting point, but it may be good to make it
a feature branch, and not master.

Specifically this fork has
some great ideas both parallel and orthogonal to my changes. If we could
get some consensus, we could join the top two results for 'openvpn docker'
on Google.
On Aug 24, 2014 2:59 AM, "Jérôme Petazzoni" notifications@github.com
wrote:

Hi @ClashTheBunny https://github.com/ClashTheBunny, sorry, I couldn't
review that earlier (such a big pull request scared me :-))

I'm afraid that I won't have enough time to review it properly, but I see
that you have put a lot of work in it. Maybe I should tag the current
version as 0.1, then merge your PR into master?

I wish there were a "survival guide for the open source maintainer that
can't commit to maintain all his stuff" :-o

—
Reply to this email directly or view it on GitHub
#8 (comment).

[jpetazzo]

That sounds like a really great idea. I don't want to prevent you guys from making progress on this with my slow pace. What would we best? Should I update the README to point to one of your forks? Should I grant you commit access so that you can manage pull requests directly? Let me know what would be the best option for you.

[jpetazzo]

Hi,

If you're still working on this and maintaining it, we could update the README for my project to mention something like:

This repository contains the initial version, which aims at remaining simple enough to be a tutorial about running OpenVPN in Docker containers. However, if you want a more complete project, we recommend that you check this other github repo which adds features X, Y, and Z.

What do you think?