Conversation
Contributor
|
Great job! No new security vulnerabilities introduced in this pull request |
mimartin12
reviewed
Apr 9, 2026
|
Member
Author
Thanks. Had to fix one item in the readme |
michalchecinski
approved these changes
Apr 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📔 Objective
Adds Bitwarden Lite variants of the existing AWS, Azure, and DigitalOcean marketplace VM images. Where the standard images deploy the full multi-container stack via bitwarden.sh, the Lite images deploy the single all-in-one ghcr.io/bitwarden/lite container via Docker Compose.
On first boot, cloud-init automatically pulls the Lite image, generates a random database password, writes a pre-configured settings.env, and starts the stack. No interactive setup is required. Database migrations run automatically on startup. Users only need to update BW_DOMAIN, BW_INSTALLATION_ID, and BW_INSTALLATION_KEY in /home/bitwarden/settings.env and restart — the MOTD dynamically reads the current config and flags any required settings that still need attention.
A new CommonMarketplaceLite/ directory holds the Lite-specific first-boot and MOTD files. Shared provisioning scripts (01-setup-first-run.sh, 02-ufw-bitwarden.sh, 90-cleanup.sh) are reused from CommonMarketplace/ unchanged, with a minor guard added to 01-setup-first-run.sh so it only chmods install-bitwarden.sh if that file exists. Each platform gets a marketplace-image-lite.pkr.hcl Packer template and a 99-img-check-lite.sh validation script. Three new release workflows mirror their standard counterparts and are triggered automatically from release.yml alongside the existing marketplace builds.