v0.6.0

Update github output syntax @max-lobur (#10)

## what Update github output syntax

why

Following github docs

references

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

v0.5.0

Update to pritunl 1.29.2664.67 and Ubuntu 18.04 @Nuru (#9)

## what - Update pritunl 1.29.2435.70 -> 1.29.2664.67 - Update Ubuntu 16.04 -> 18.04 - Ensure that specified pritunl version is actually the one installed

why

• Multiple bug fixes
• Bug fixes
• Previously the version installed would be the latest one available when the Docker build ran, which could produce inconsistent and misleading results.

references

https://github.com/pritunl/pritunl/releases

v0.4.0

Fixing Docker Hub publishes @danjbh (#7)

## what?!

I had originally modeled the Github action build triggers against another project, and upon further analysis, I don't think the project I modeled is actually working properly. In a nutshell, the release created trigger wasn't firing when the auto-release workflow was executed, which means we were never getting Docker images with actual semver tags in Docker Hub.

In addition, I had to cleanup some of the expression logic to properly match github.ref.

Anyhow, I was able to test it in my branch before merging to master by just pushing a new tag, and I'm happy to report it's working. Here's the behavior...

• If you're pushing a new commit against a non-forked PR, it will build/push a new image to Docker hub (with both an sha-<sha> AND a pr-<num>-merge tag
• If a new tag (or release) is created, it will build an image and upload it to Docker hub using the proper semver format (generated by auto-release, but without the leading v)

What I haven't tested is the auto-release portion, but I'm fairly certain it should work with this method. Of course, I thought the past couple attempts would work, and I think I'm starting to question my own sanity at this point.

Updating conditional to build-and-push Github workflow @danjbh (#6)

## what & why?

We need to build/publish master when triggered. The added logic triggers the steps if the branch is master but not if it's a pull request (since the source branch in a forked repo could also be master).

Adding Docker login to Github bulid-and-push job @danjbh (#5)

## what & why?

• Adding Docker login step to build-and-push job since it's currently borked

references

docker/build-push-action#88 (comment)

Adding auto-release Github workflow @danjbh (#4)

## why?

So we can get automated Docker image publishes w/ semver tags!

Adding dnspython module install to Dockerfile @danjbh (#3)

## what? - Adding the `python-dnspython` apt package to Dockerfile

why?

• This module is need to support mongodb+srv URIs

0.3.0

Update pritunl to `1.29.2435.70`

0.2.1

Update Makefile

0.2.0

Update Dockerfile

0.1.0: Init (#2)

## What
* Created pritunl container

## Why
* To run pritunl on k8s