📝 What’s Changed
This release updates the Docker container with automatic TLS (SSL) certificate management. No more need for Nginx, Apache or other TLS termination points. Here's how to get a Password Pusher instance with automatic TLS:
→ Setup a DNS record to point to your server (e.g. pwpush.example.com) and run:
docker run -d -p "80:80" -p "443:433" --env TLS_DOMAIN=pwpush.example.com pglombardo/pwpush:latest
and browse to https://pwpush.example.com.
Note: The previous default HTTP port 5100 still works as always too.
🚀 Features
- Add automatic TLS certificates (#3501) @ozovalihasan
⬆️ Dependencies updates
- ⬆️ Bump aws-sdk-s3 from 1.193.0 to 1.194.0 (#3555) @dependabot[bot]
- ⬆️ Bump importmap-rails from 2.1.0 to 2.2.0 (#3554) @dependabot[bot]
- ⬆️ Bump reline from 0.6.1 to 0.6.2 (#3553) @dependabot[bot]
- ⬆️ Bump aws-sdk-kms from 1.106.0 to 1.107.0 (#3552) @dependabot[bot]
- ⬆️ Bump aws-partitions from 1.1131.0 to 1.1133.0 (#3551) @dependabot[bot]
👥 List of contributors
@dependabot[bot], @ozovalihasan, @pglombardo and dependabot[bot]
🛥️ Docker Images
Available on Docker Hub:
https://hub.docker.com/r/pglombardo/pwpush
🏃♂️ Run This Version
→ Setup a DNS record to point to your server (e.g. pwpush.example.com) and run:
docker run -d -p "80:80" -p "443:433" --env TLS_DOMAIN=pwpush.example.com pglombardo/pwpush:1.59.0`and browse to https://pwpush.example.com.
or alternatively
→ Use one of our production ready Docker Compose files with persistent databases.