Bump version to 0.15.1 (#729)

Bumps the npm_and_yarn group with 1 update in the /browser-extension directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite).


Updates `vite` from 6.2.0 to 6.2.3
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v6.2.3/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.2.3/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>

.env.example

@@ -1,10 +1,106 @@
+# ----------------------------------------------------------------------------
+# AliasVault configuration file.
+#
+# Note: we recommend using the provided install.sh script to install and
+# configure AliasVault, as this will automatically set all of the following
+# variables for you and allow you to easily change them later via the CLI.
+# It also allows for easily updating AliasVault to a newer version in the
+# future.
+#
+# However if you still wish to manually install or configure AliasVault,
+# you can do so below.
+#
+# After changing settings here, make sure to restart all AliasVault
+# Docker containers to apply the changes.
+# ----------------------------------------------------------------------------
+
+# Set the ports that your AliasVault will be accessible at.
+# These are the default ports that will be used by the `reverse-proxy` and `smtp` containers.
+# You can change these to any other ports that are available on your system.
+HTTP_PORT=80
+HTTPS_PORT=443
+SMTP_PORT=25
+SMTP_TLS_PORT=587
+
+# Set the hostname that your AliasVault will be accessible at.
+# E.g. `aliasvault.mydomain.com` or if you're running it on your local machine, choose `localhost`.
 HOSTNAME=
+
+# Set a random 32 character string for the JWT key.
+# This can be generated using the following command:
+# $ openssl rand -base64 32
 JWT_KEY=
+
+# Set the password for the data protection certificate.
+# This can be generated using the following command:
+# $ openssl rand -base64 32
 DATA_PROTECTION_CERT_PASS=
-ADMIN_PASSWORD_HASH=
-ADMIN_PASSWORD_GENERATED=2024-01-01T00:00:00Z
-PRIVATE_EMAIL_DOMAINS=
-SMTP_TLS_ENABLED=false
-LETSENCRYPT_ENABLED=false
+
+# ----------------------------------------------------------------------------
+# Database configuration
+# ----------------------------------------------------------------------------
+# These are the credentials that are used by the PostgreSQL container
+# on startup to create the database and user, and for the application to
+# connect to the database.
+POSTGRES_DB=aliasvault
+POSTGRES_USER=aliasvault
+
+# Set the password for the database user.
+# This can be generated using the following command:
+# $ openssl rand -base64 32
 POSTGRES_PASSWORD=
+
+# Note: in order to change the password for an existing installation
+# refer to https://docs.aliasvault.net/misc/dev/database-operations.html
+
+# ----------------------------------------------------------------------------
+# Admin user configuration
+# ----------------------------------------------------------------------------
+# Set the password for the admin user. This is an encrypted hash that needs
+# to be generated using the `aliasvault-cli` tool. This allows you to login
+# to the admin panel at https://your-hostname/admin.
+#
+# For example:
+# docker run --rm ghcr.io/lanedirt/aliasvault-installcli:latest hash-password "my-password"
+#
+# Then copy the output and paste it into the ADMIN_PASSWORD_HASH variable below.
+# When changing the hash, update the ADMIN_PASSWORD_GENERATED variable to the current date and time
+# and then restart the AliasVault docker containers to apply the changes.
+ADMIN_PASSWORD_HASH=
+
+# Set the date and time the admin password was last generated. When changing the
+# admin password hash manually, make sure to increase this value so the system
+# knows that the password has been changed and should be overwritten with the new hash.
+ADMIN_PASSWORD_GENERATED=2024-01-01T00:00:00Z
+
+# ----------------------------------------------------------------------------
+# Email server configuration for email aliases
+# ----------------------------------------------------------------------------
+# In order to use AliasVault's private email domains feature, you need to configure
+# your DNS. Please refer to the full documentation for more instructions on DNS:
+# https://docs.aliasvault.net/installation/install.html#3-email-server-setup
+#
+# Set the private email domains below that are allowed to be used (comma separated values).
+# Example: PRIVATE_EMAIL_DOMAINS=example.com,example2.org
+# To disable the private email domains feature, set this to "DISABLED.TLD"
+PRIVATE_EMAIL_DOMAINS=DISABLED.TLD
+
+# Set whether TLS is enabled for SMTP.
+SMTP_TLS_ENABLED=false
+
+# ----------------------------------------------------------------------------
+# Let's Encrypt configuration
+# ----------------------------------------------------------------------------
+# Set whether Let's Encrypt is enabled. This is only supported through
+# the install.sh script.
+LETSENCRYPT_ENABLED=false
+
+# ----------------------------------------------------------------------------
+# Optional configuration settings
+# ----------------------------------------------------------------------------
+PUBLIC_REGISTRATION_ENABLED=true
+IP_LOGGING_ENABLED=true
+
+# Set the support email address which is shown to users in the main web app.
+# Keep this blank if you don't want to show a support email.
 SUPPORT_EMAIL=

.github/workflows/release.yml

@@ -52,10 +52,10 @@ jobs:
         uses: softprops/action-gh-release@v2
         with:
           files: |
-            dist/aliasvault-browser-extension-*-chrome.zip
-            dist/aliasvault-browser-extension-*-firefox.zip
-            dist/aliasvault-browser-extension-*-edge.zip
-            dist/aliasvault-browser-extension-*-sources.zip
+            browser-extension/dist/aliasvault-browser-extension-*-chrome.zip
+            browser-extension/dist/aliasvault-browser-extension-*-firefox.zip
+            browser-extension/dist/aliasvault-browser-extension-*-edge.zip
+            browser-extension/dist/aliasvault-browser-extension-*-sources.zip
           token: ${{ secrets.GITHUB_TOKEN }}
 
   build-and-push-docker:

README.md

@@ -81,7 +81,7 @@ The install script will output the URL where the app is available. By default th
 > Note: If you want to change the default AliasVault ports you can do so in the `.env` file.
 
 ## Documentation
-For more detailed information about the installation process and other topics, please see the official documentation website:
+For more information about the installation process, manual setup instructions and other topics, please see the official documentation website:
 - [Documentation website (docs.aliasvault.net) 📚](https://docs.aliasvault.net)
 
 ## Security Architecture
@@ -108,7 +108,7 @@ AliasVault is under active development with new features being added regularly.
 - [x] Firefox and MS Edge browser extension
 - [x] Safari and Brave browser extension
 - [x] Add and associate TOTP MFA tokens to credentials
-- [ ] Add GUI to allow customizing password generation options (length, special chars etc.) (https://github.com/lanedirt/AliasVault/issues/167)
+- [x] Add GUI to allow customizing password generation options (length, special chars etc.) (https://github.com/lanedirt/AliasVault/issues/167)
 - [ ] Import passwords from existing password managers (https://github.com/lanedirt/AliasVault/issues/542)
 - [ ] Add support for connecting custom user domains to cloud hosted version (https://github.com/lanedirt/AliasVault/issues/485)
 

browser-extension/package-lock.json

@@ -12449,9 +12449,9 @@
       }
     },
     "node_modules/vite": {
-      "version": "6.2.0",
-      "resolved": "https://registry.npmjs.org/vite/-/vite-6.2.0.tgz",
-      "integrity": "sha512-7dPxoo+WsT/64rDcwoOjk76XHj+TqNTIvHKcuMQ1k4/SeHDaQt5GFAeLYzrimZrMpn/O6DtdI03WUjdxuPM0oQ==",
+      "version": "6.2.3",
+      "resolved": "https://registry.npmjs.org/vite/-/vite-6.2.3.tgz",
+      "integrity": "sha512-IzwM54g4y9JA/xAeBPNaDXiBF8Jsgl3VBQ2YQ/wOY6fyW3xMdSoltIV3Bo59DErdqdE6RxUfv8W69DvUorE4Eg==",
       "license": "MIT",
       "dependencies": {
         "esbuild": "^0.25.0",

browser-extension/safari-xcode/AliasVault/AliasVault.xcodeproj/project.pbxproj

@@ -530,7 +530,7 @@
 					"@executable_path/../Frameworks",
 				);
 				MACOSX_DEPLOYMENT_TARGET = 10.14;
-				MARKETING_VERSION = 0.15.0;
+				MARKETING_VERSION = 0.15.1;
 				OTHER_LDFLAGS = (
 					"-framework",
 					SafariServices,
@@ -569,7 +569,7 @@
 					"@executable_path/../Frameworks",
 				);
 				MACOSX_DEPLOYMENT_TARGET = 10.14;
-				MARKETING_VERSION = 0.15.0;
+				MARKETING_VERSION = 0.15.1;
 				OTHER_LDFLAGS = (
 					"-framework",
 					SafariServices,

browser-extension/src/utils/AppInfo.ts

@@ -6,7 +6,7 @@ export class AppInfo {
   /**
    * The current extension version. This should be updated with each release of the extension.
    */
-  public static readonly VERSION = '0.15.0';
+  public static readonly VERSION = '0.15.1';
 
   /**
    * The minimum supported AliasVault server (API) version. If the server version is below this, the

browser-extension/wxt.config.ts

@@ -7,7 +7,7 @@ export default defineConfig({
   manifest: {
     name: "AliasVault",
     description: "AliasVault Browser AutoFill Extension. Keeping your personal information private.",
-    version: "0.15.0",
+    version: "0.15.1",
     content_security_policy: {
       extension_pages: "script-src 'self' 'wasm-unsafe-eval'; object-src 'self';"
     },

docs/installation/advanced/build-from-source.md

@@ -2,7 +2,7 @@
 layout: default
 title: Build from Source
 parent: Advanced
-nav_order: 1
+nav_order: 2
 ---
 
 # Build from Source
@@ -26,7 +26,7 @@ cd AliasVault
 chmod +x install.sh
 ./install.sh build
 ```
-> **Note:** The build process can take a while depending on your hardware (5-15 minutes).
+> **Note:** The complete build process can take a while depending on your hardware (5-15 minutes).
 
 3.  After the script completes, you can access AliasVault at:
   - Client: `https://localhost`

docs/installation/advanced/database.md

@@ -2,7 +2,7 @@
 layout: default
 title: Database Backup
 parent: Advanced
-nav_order: 2
+nav_order: 3
 ---
 
 # Database Backup

docs/installation/advanced/manual-setup.md

@@ -2,171 +2,109 @@
 layout: default
 title: Manual Setup
 parent: Advanced
-nav_order: 3
+nav_order: 1
 ---
 
 # Manual Setup
 
-If you prefer to manually set up AliasVault, this README provides step-by-step instructions. Follow these steps if you prefer to execute all statements yourself.
+If you prefer to manually set up AliasVault instead of using the `install.sh` script, this README provides step-by-step instructions.
+
+{: .toc }
+* TOC
+{:toc}
+
+---
 
 ## Prerequisites
 
 - Docker and Docker Compose installed on your system
+- Knowledge of working with direct Docker commands
+- Knowledge of .env files
 - OpenSSL for generating random passwords
 
 ## Steps
 
-1. **Create required directories**
+1. **Clone the git repository**
+   ```bash
+   # Clone repository
+   git clone https://github.com/lanedirt/AliasVault.git
+
+   # Navigate to the AliasVault directory
+   cd AliasVault
+   ```
+
+2. **Create required directories**
 
    Create the following directories in your project root:
    ```bash
+   # Create required directories
    mkdir -p certificates/ssl certificates/app database/postgres
    ```
 
-2. **Create .env file**
+3. **Create .env file**
 
-   Copy the `.env.example` file to create a new `.env` file:
    ```bash
+   # Copy the .env.example file to create a new .env file
    cp .env.example .env
    ```
 
-3. **Set HOSTNAME**
+4. **Set all required settings in .env**
+
+   Open the .env file in your favorite text editor and fill in all required variables
+   by following the instructions inside the file.
 
-   Update the .env file with your hostname (default is localhost):
    ```bash
-   HOSTNAME=localhost
+   # Open the .env file with your favorite editor, e.g. nano.
+   nano .env
    ```
 
-4. **Set default ports**
+5. **Start the docker containers**
 
-   Update the .env file with the ports you want to use for the AliasVault components. The values defined here are used by the docker-compose.yml file.
+   After you are done configuring your .env file, you can start the Docker Compose stack:
    ```bash
-   HTTP_PORT=80
-   HTTPS_PORT=443
-   SMTP_PORT=25
-   SMTP_TLS_PORT=587
+   # Start the docker compose stack
+   docker compose up -d
    ```
 
-5. **Generate and set JWT_KEY**
-
-   Generate a random 32-char string for JWT token generation:
-   ```bash
-   openssl rand -base64 32
-   ```
-
-   Add the generated key to the .env file:
-   ```bash
-   JWT_KEY=your_generated_key_here
-   ```
-
-6. **Generate and set DATA_PROTECTION_CERT_PASS**
-
-   Generate a random password for the data protection certificate:
-   ```bash
-   openssl rand -base64 32
-   ```
-
-   Add it to the .env file:
-   ```bash
-   DATA_PROTECTION_CERT_PASS=your_generated_password_here
-   ```
-
-7. **Configure PostgreSQL Settings**
-
-   Set the following PostgreSQL-related variables in your .env file:
-   ```bash
-   # Database name (default: aliasvault)
-   POSTGRES_DB=aliasvault
-
-   # Database user (default: aliasvault)
-   POSTGRES_USER=aliasvault
-
-   # Generate a secure password for PostgreSQL
-   POSTGRES_PASSWORD=$(openssl rand -base64 32)
-   ```
-
-8. **Set PRIVATE_EMAIL_DOMAINS**
-
-   Update the .env file with allowed email domains. Use DISABLED.TLD to disable email support:
-   ```bash
-   PRIVATE_EMAIL_DOMAINS=yourdomain.com,anotherdomain.com
-   ```
-   Or to disable email:
-   ```bash
-   PRIVATE_EMAIL_DOMAINS=DISABLED.TLD
-   ```
-
-9. **Set SUPPORT_EMAIL (Optional)**
-
-   Add a support email address if desired:
-   ```bash
-   SUPPORT_EMAIL=support@yourdomain.com
-   ```
-
-10. **Generate admin password**
-
-   Build the Docker image for password hashing:
-   ```bash
-   docker build -t installcli -f src/Utilities/AliasVault.InstallCli/Dockerfile .
-   ```
-
-   Generate the password hash:
-   ```bash
-   docker run --rm installcli "your_preferred_admin_password_here"
-   ```
-
-   Add the password hash and generation timestamp to the .env file:
-   ```bash
-   ADMIN_PASSWORD_HASH=<output_from_previous_command>
-   ADMIN_PASSWORD_GENERATED=2024-01-01T00:00:00Z
-   ```
-
-11. **Optional configuration**
-   Enable or disable public registration of new users:
-   ```bash
-   PUBLIC_REGISTRATION_ENABLED=false
-   ```
-
-12. **Build and start Docker containers**
-
-    Build the Docker Compose stack:
-    ```bash
-    docker compose -f docker-compose.yml -f docker-compose.build.yml build
-    ```
-
-    Start the Docker Compose stack:
-    ```bash
-    docker compose -f docker-compose.yml -f docker-compose.build.yml up -d
-    ```
-
-13. **Access AliasVault**
+6. **Access AliasVault**
 
     AliasVault should now be running. You can access it at:
 
     - Admin Panel: https://localhost/admin
         - Username: admin
-        - Password: [Use the password you set in step 9]
+        - Password: [Use the password you set in the .env file]
 
     - Client Website: https://localhost/
         - Create your own account from here
 
+   > Note: if you changed the default ports from 80/443 to something else in the .env file, use those ports to access AliasVault here.
+
+7. **Configuring private email domains**
+
+   By default, the AliasVault private email domains feature is disabled. If you wish to enable this so you can use your own private domains to create email aliases with, please read the `Email Server Setup` section in the main installation guide [Basic Install](../install.md#3-email-server-setup).
+
+   For more information, read the article explaining the differences between AliasVault's [private and public domains](../../misc/private-vs-public-email.md).
+
+
 ## Important Notes
 
 - Make sure to save both the admin password and PostgreSQL password in a secure location.
-- If you need to reset the admin password in the future, repeat step 9 and restart the Docker containers.
 - Always keep your .env file secure and do not share it, as it contains sensitive information.
 - The PostgreSQL data is persisted in the `database/postgres` directory.
+- The docker-compose.yml file uses the `:latest` tag for containers by default. This means it always uses the latest available AliasVault version. In order to update AliasVault to a newer version at a later time, you can pull new containers when they are available with this command:
+```
+docker compose pull && docker compose down && docker compose up -d
+```
 
 ## Troubleshooting
-
 If you encounter any issues during the setup:
 
 1. Check the Docker logs:
    ```bash
    docker compose logs
    ```
-2. Ensure all required ports (80, 443, and 5432) are available and not being used by other services.
-3. Verify that all environment variables in the .env file are set correctly.
+2. Ensure all required ports (80, 443, 25, 587 and 5432) are available and not being used by other services.
+3. Verify that all variables in the .env file are set correctly.
 4. Check PostgreSQL container logs specifically:
    ```bash
    docker compose logs postgres

docs/installation/install.md

@@ -27,13 +27,16 @@ To get AliasVault up and running quickly, run the install script to pull pre-bui
 ### Installation steps
 1. Download the install script to a directory of your choice. All AliasVault files and directories will be created in this directory.
 ```bash
-curl -o install.sh https://raw.githubusercontent.com/lanedirt/AliasVault/main/install.sh
+# Download the install script
+curl -o install.sh https://github.com/lanedirt/AliasVault/releases/latest/download/install.sh
 ```
+
 2. Make the install script executable.
 ```bash
 chmod +x install.sh
 ```
-3. Run the install script. This will create the .env file, pull the Docker images, and start the AliasVault containers. Follow the on-screen prompts to configure AliasVault.
+
+3. Run the installation wizard.
 ```bash
 ./install.sh install
 ```
@@ -43,6 +46,8 @@ chmod +x install.sh
   - Client: `https://localhost`
   - Admin: `https://localhost/admin`
 
+> Note: if you do not wish to run the `install.sh` wizard but want to use Docker commands directly, follow the [manual setup guide](advanced/manual-setup.md). We do however encourage the use of `install.sh` as it will guide you through all configuration steps and allow for easy updating your AliasVault instance later.
+
 ---
 
 ## 2. SSL configuration

install.sh

@@ -1,5 +1,5 @@
 #!/bin/bash
-# @version 0.15.0
+# @version 0.15.1
 
 # Repository information used for downloading files and images from GitHub
 REPO_OWNER="lanedirt"
@@ -294,6 +294,16 @@ main() {
     esac
 }
 
+# Function to get the latest release version from GitHub
+get_latest_version() {
+    local latest_version=$(curl -s "https://api.github.com/repos/${REPO_OWNER}/${REPO_NAME}/releases/latest" | grep -o '"tag_name": *"[^"]*"' | cut -d'"' -f4)
+    if [ -z "$latest_version" ]; then
+        printf "${RED}> Failed to get latest version from GitHub.${NC}\n" >&2
+        return 1
+    fi
+    echo "$latest_version"
+}
+
 # Function to create required directories
 create_directories() {
     printf "${CYAN}> Checking workspace...${NC}\n"
@@ -411,13 +421,26 @@ print_logo() {
 create_env_file() {
     printf "${CYAN}> Checking .env file...${NC}\n"
     if [ ! -f "$ENV_FILE" ]; then
-        if [ -f "$ENV_EXAMPLE_FILE" ]; then
-            cp "$ENV_EXAMPLE_FILE" "$ENV_FILE"
-            printf "  ${GREEN}> New.env file created from .env.example.${NC}\n"
-        else
-            touch "$ENV_FILE"
-            printf "  ${YELLOW}> New blank .env file created.${NC}\n"
+        if [ ! -f "$ENV_EXAMPLE_FILE" ]; then
+            # Get latest release version
+            local latest_version=$(get_latest_version) || {
+                printf "  ${YELLOW}> Failed to check latest version. Creating blank .env file.${NC}\n"
+                touch "$ENV_FILE"
+                return 0
+            }
+
+            printf "  ${CYAN}> Downloading .env.example...${NC}"
+            if curl -sSf "${GITHUB_RAW_URL_REPO}/${latest_version}/.env.example" -o "$ENV_EXAMPLE_FILE" > /dev/null 2>&1; then
+                printf "\n  ${GREEN}> .env.example downloaded successfully.${NC}\n"
+            else
+                printf "\n  ${YELLOW}> Failed to download .env.example. Creating blank .env file.${NC}\n"
+                touch "$ENV_FILE"
+                return 0
+            fi
         fi
+
+        cp "$ENV_EXAMPLE_FILE" "$ENV_FILE"
+        printf "  ${GREEN}> New .env file created from .env.example.${NC}\n"
     else
         printf "  ${GREEN}> .env file already exists.${NC}\n"
     fi
@@ -616,10 +639,19 @@ update_env_var() {
     local value=$2
 
     if [ -f "$ENV_FILE" ]; then
-        sed -i.bak "/^${key}=/d" "$ENV_FILE" && rm -f "$ENV_FILE.bak"
+        # Check if key exists
+        if grep -q "^${key}=" "$ENV_FILE"; then
+            # Update existing key inline
+            sed -i.bak "s|^${key}=.*|${key}=${value}|" "$ENV_FILE" && rm -f "$ENV_FILE.bak"
+        else
+            # Key doesn't exist, append it
+            echo "$key=$value" >> "$ENV_FILE"
+        fi
+    else
+        # File doesn't exist, create it with the key-value pair
+        echo "$key=$value" > "$ENV_FILE"
     fi
 
-    echo "$key=$value" >> "$ENV_FILE"
     printf "  ${GREEN}> $key has been set in $ENV_FILE.${NC}\n"
 }
 
@@ -815,6 +847,8 @@ handle_install() {
 # Function to handle build
 handle_build() {
     printf "${YELLOW}+++ Building AliasVault from source +++${NC}\n"
+    create_env_file || { printf "${RED}> Failed to create .env file${NC}\n"; exit 1; }
+    
     # Set deployment mode to build to ensure container lifecycle uses build configuration
     set_deployment_mode "build"
     printf "\n"
@@ -838,7 +872,6 @@ handle_build() {
     fi
 
     # Initialize environment with proper error handling
-    create_env_file || { printf "${RED}> Failed to create .env file${NC}\n"; exit 1; }
     set_support_email || { printf "${RED}> Failed to set support email${NC}\n"; exit 1; }
     populate_jwt_key || { printf "${RED}> Failed to set JWT key${NC}\n"; exit 1; }
     populate_data_protection_cert_pass || { printf "${RED}> Failed to set certificate password${NC}\n"; exit 1; }
@@ -1331,7 +1364,10 @@ handle_update() {
     fi
 
     current_version=$(grep "^ALIASVAULT_VERSION=" "$ENV_FILE" | cut -d '=' -f2)
-    latest_version=$(curl -s "https://api.github.com/repos/${REPO_OWNER}/${REPO_NAME}/releases/latest" | grep '"tag_name":' | sed -E 's/.*"([^"]+)".*/\1/')
+    latest_version=$(get_latest_version) || {
+        printf "${RED}> Failed to check for updates. Please try again later.${NC}\n"
+        exit 1
+    }
 
     if [ -z "$latest_version" ]; then
         printf "${RED}> Failed to check for updates. Please try again later.${NC}\n"
@@ -1413,7 +1449,10 @@ check_install_script_update() {
     printf "${CYAN}> Checking for install script updates...${NC}\n"
 
     # Get latest release version
-    local latest_version=$(curl -s "https://api.github.com/repos/${REPO_OWNER}/${REPO_NAME}/releases/latest" | grep '"tag_name":' | sed -E 's/.*"([^"]+)".*/\1/')
+    local latest_version=$(get_latest_version) || {
+        printf "${RED}> Failed to check for install script updates. Continuing with current version.${NC}\n"
+        return 1
+    }
 
     if [ -z "$latest_version" ]; then
         printf "${RED}> Failed to check for install script updates. Continuing with current version.${NC}\n"
@@ -1506,13 +1545,18 @@ handle_install_version() {
 
     # If latest, get actual version number from GitHub API
     if [ "$target_version" = "latest" ]; then
-        local actual_version=$(curl -s "https://api.github.com/repos/${REPO_OWNER}/${REPO_NAME}/releases/latest" | grep '"tag_name":' | sed -E 's/.*"([^"]+)".*/\1/')
+        local actual_version=$(get_latest_version) || {
+            printf "${RED}> Failed to get latest version. Please try again later.${NC}\n"
+            exit 1
+        }
         if [ -n "$actual_version" ]; then
             target_version="$actual_version"
         fi
     fi
 
     printf "${YELLOW}+++ Installing AliasVault ${target_version} +++${NC}\n"
+    create_env_file || { printf "${RED}> Failed to create .env file${NC}\n"; exit 1; }
+
     # Set deployment mode to install to ensure container lifecycle uses install configuration
     set_deployment_mode "install"
     printf "\n"
@@ -1558,7 +1602,6 @@ handle_install_version() {
     handle_docker_compose "$target_version"
 
     # Initialize environment
-    create_env_file || { printf "${RED}> Failed to create .env file${NC}\n"; exit 1; }
     set_support_email || { printf "${RED}> Failed to set support email${NC}\n"; exit 1; }
     populate_jwt_key || { printf "${RED}> Failed to set JWT key${NC}\n"; exit 1; }
     populate_data_protection_cert_pass || { printf "${RED}> Failed to set certificate password${NC}\n"; exit 1; }
@@ -2033,25 +2076,27 @@ handle_hostname_configuration() {
 
     # Get current hostname
     CURRENT_HOSTNAME=$(grep "^HOSTNAME=" "$ENV_FILE" | cut -d '=' -f2)
-    printf "${CYAN}Removing current hostname ${CURRENT_HOSTNAME}${NC}...\n"
+    printf "Current hostname: ${CYAN}${CURRENT_HOSTNAME}${NC}\n"
     printf "\n"
 
-    # Force hostname to be empty so populate_hostname will ask for a new one
-    sed -i.bak "/^HOSTNAME=/d" "$ENV_FILE" && rm -f "$ENV_FILE.bak"
+    # Ask for new hostname
+    while true; do
+        read -p "Enter new hostname (e.g. aliasvault.net): " NEW_HOSTNAME
+        if [ -n "$NEW_HOSTNAME" ]; then
+            break
+        else
+            printf "${YELLOW}> Hostname cannot be empty. Please enter a valid hostname.${NC}\n"
+        fi
+    done
 
-    # Reuse existing hostname population logic
-    populate_hostname
+    # Update the hostname
+    update_env_var "HOSTNAME" "$NEW_HOSTNAME"
 
-    if [ $? -eq 0 ]; then
-        printf "New hostname: ${CYAN}${HOSTNAME}${NC}\n"
-        printf "\n"
-        printf "${MAGENTA}=========================================================${NC}\n"
-    else
-        printf "${RED}> Failed to update hostname. Please try again.${NC}\n"
-        printf "\n"
-        printf "${MAGENTA}=========================================================${NC}\n"
-        exit 1
-    fi
+    printf "\n"
+    printf "${GREEN}Hostname updated successfully!${NC}\n"
+    printf "New hostname: ${CYAN}${NEW_HOSTNAME}${NC}\n"
+    printf "\n"
+    printf "${MAGENTA}=========================================================${NC}\n"
 }
 
 # Function to handle IP logging configuration

src/Shared/AliasVault.Shared.Core/AppInfo.cs

@@ -30,7 +30,7 @@ public static class AppInfo
     /// <summary>
     /// Gets the patch version number.
     /// </summary>
-    public const int VersionPatch = 0;
+    public const int VersionPatch = 1;
 
     /// <summary>
     /// Gets the minimum supported AliasVault client version. Normally the minimum client version is the same