Merge pull request #122 from sandialabs/powered-by-snl-atlas

Add "Powered By Sandia ATLAS" logo to lower right of Welcome Screen.

Author: garland3

.env.example

@@ -51,7 +51,12 @@ ENVIRONMENT=development
 #############################################
 
 # Frontend build-time app name (Vite will inject this into index.html)
-VITE_APP_NAME=Chat UI 13
+VITE_APP_NAME=ATLAS
+
+# Frontend build-time flag to show the "Powered By Sandia ATLAS" badge
+# on the welcome screen. Other deployments can set this to false
+# to hide the badge while still customizing the main logo.
+VITE_FEATURE_POWERED_BY_ATLAS=false
 
 # OpenTelemetry configuration (optional - for future use)
 # OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317

agent_start.sh

@@ -68,6 +68,13 @@ setup_environment() {
     cd "$PROJECT_ROOT"
     . .venv/bin/activate
 
+    # Load environment variables from .env if present
+    if [ -f "$PROJECT_ROOT/.env" ]; then
+        set -a
+        . "$PROJECT_ROOT/.env"
+        set +a
+    fi
+    
     echo "Setting MCP_EXTERNAL_API_TOKEN for testing purposes."
     if [ -z "$MCP_EXTERNAL_API_TOKEN" ]; then
         export MCP_EXTERNAL_API_TOKEN="test-api-key-123"
@@ -100,7 +107,11 @@ build_frontend() {
     echo "Building frontend..."
     cd "$PROJECT_ROOT/frontend"
     npm install
-    export VITE_APP_NAME="Chat UI"
+    # Use VITE_* values from the environment / .env instead of hardcoding.
+    # If VITE_APP_NAME is not already set, fall back to the example default.
+    if [ -z "$VITE_APP_NAME" ]; then
+        export VITE_APP_NAME="Chat UI 13"
+    fi
     npm run build
     cd "$PROJECT_ROOT"
 }

backend/main.py

@@ -198,6 +198,12 @@ async def logo_png():
         path = static_dir / "logo.png"
         return FileResponse(str(path))
 
+    @app.get("/sandia-powered-by-atlas.png")
+    async def logo2_png():
+        path = static_dir / "sandia-powered-by-atlas.png"
+        return FileResponse(str(path))
+
+
 # WebSocket endpoint for chat
 @app.websocket("/ws")
 async def websocket_endpoint(websocket: WebSocket):

docs/admin/configuration.md

@@ -32,6 +32,7 @@ Key settings in the `.env` file include:
 *   **API Keys**: `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, etc.
 *   **Authentication Header**: `AUTH_USER_HEADER` configures the HTTP header name used to extract the authenticated username from your reverse proxy (default: `X-User-Email`).
 *   **Feature Flags**: Enable or disable major features like `FEATURE_AGENT_MODE_AVAILABLE`.
+*   **Branding Flags**: Control frontend branding such as `VITE_APP_NAME` and the optional `VITE_FEATURE_POWERED_BY_ATLAS` badge on the welcome screen.
 *   **S3 Connection**: Configure the connection to your S3-compatible storage. For local testing, you can set `USE_MOCK_S3=true` to use an in-memory mock instead of a real S3 bucket. **This mock must never be used in production.**
 *   **Log Directory**: The `APP_LOG_DIR` variable points to the folder where the application log file (`app.jsonl`) will be stored. This path must be updated to a valid directory in your deployment environment.
 *   **Security Headers**: Configure Content Security Policy (CSP) and other security headers. See the Security Configuration section below for details.

docs/archive/app_name.md

@@ -7,6 +7,7 @@ This document explains how to configure the application name that appears in the
 The app name can be configured in two places:
 - **Frontend (Browser Title)**: Set at build time using `VITE_APP_NAME`
 - **Backend (API Response)**: Set at runtime using `APP_NAME`
+ - **Optional Powered-By Badge**: Controlled via `VITE_FEATURE_POWERED_BY_ATLAS`
 
 ## Frontend Configuration (Browser Title)
 
@@ -25,6 +26,14 @@ cd frontend
 npm run build
 ```
 
+You can also control whether the "Powered By Sandia ATLAS" badge appears on the welcome screen:
+
+```bash
+VITE_FEATURE_POWERED_BY_ATLAS=true  # show powered-by badge
+```
+
+Other deployments can set this flag to `false` (or omit it) to hide the badge while still customizing the primary logo and app name.
+
 ### Docker Builds
 
 Use the `VITE_APP_NAME` build argument: