What's already configured
After the one-click deploy, Memos runs as a single Docker container (the official neosmemo/memos image) with its data volume already mounted, so notes, tags, and attachments persist across container restarts. The container is set to auto-restart, so a server reboot brings Memos back online without manual intervention. By default the app stores its database as a local SQLite file inside that data volume — no separate database server to configure unless you've explicitly switched to PostgreSQL or MySQL. The web interface listens on port 5230 inside the container.
First login
Open your server's address in a browser to reach the Memos web interface. On a fresh instance there are no existing accounts, so the first screen you see is a sign-up form rather than a login prompt — the first account you register becomes the instance's admin/host account, with full access to server settings and user management.
Practical first steps
Once logged in, set your workspace visibility default (private, protected, or public) under the admin settings before inviting anyone else, since this controls what new memos default to. If you plan to write from a phone or automate note capture, generate an API access token from your account settings rather than reusing your admin password anywhere else.