first setup configuration

README.md

@@ -191,7 +191,7 @@ New users created by an administrator are email-unverified and cannot sign in un
 
 The full set of supported variables is listed in `.env.example`. Application variables are passed into the container by Compose; Docker and Traefik variables are used by Compose itself.
 
-Build and start the application and local Traefik proxy:
+Build and start the application:
 
 ```sh
 docker compose up --build
@@ -199,12 +199,11 @@ docker compose up --build
 
 The services are available at:
 
-- LinkLog through Traefik: <http://example.com/>
 - Direct application port: <http://localhost:8000/>
 
 
-The Compose configuration routes the hostname `localhost` through Traefik. The SQLite database is stored in the named Docker volume `linklog_data`, mounted at `/app/backend/data`.
-The application runs as a non-root user and reports container health through `/health`; Traefik waits for the application health check before starting.
+The SQLite database is stored in the named Docker volume `linklog_data`, mounted at `/app/backend/data`.
+The application runs as a non-root user and reports container health through `/health`; 
 
 Stop the stack without deleting its database:
 
@@ -218,7 +217,7 @@ Stop the stack and delete the named database volume:
 docker compose down -v
 ```
 
-For a real deployment, replace the `localhost` router rule, configure TLS, protect the Traefik dashboard, avoid exposing the direct application port, and provide production secrets and authentication. The included Compose file is a local/prototype deployment scaffold, not a production security configuration.
+For a real deployment, start with the docker-compose-example.yaml file. replace the router rule, configure TLS, protect the Traefik dashboard, avoid exposing the direct application port, and provide production secrets and authentication. The included Compose file is a local/prototype deployment scaffold, not a production security configuration.
 
 ## Mastodon Configuration