What's already configured
The one-click Mealie SQLite install runs as a single container with the API and frontend served together — there's no separate database container to manage, since SQLite lives inside the app's own data volume. Recipe images, the database file, and any UI-created backups are stored under /app/data inside the container, which is the standard Mealie data path regardless of hosting provider. The container runs with restart: unless-stopped by default in most Mealie deployments, so it comes back up automatically after a reboot.
First login
Mealie ships with a default administrator account — username changeme@example.com, password MyPassword — and you'll want to change both immediately after your first login, since the sign-up button disappears once you do. Where exactly this login screen appears (your assigned domain, subdomain, or IP:port combination) depends on how Leneex exposes the app after deployment.
Getting your first recipes in
The fastest way to populate an empty Mealie instance is pasting URLs from recipe websites you already use — the scraper pulls ingredients, steps, and a photo automatically for most sites that use standard recipe markup. From there, set your Households and Groups structure before inviting family members, since recipe visibility and meal-plan separation both depend on that setup being done early rather than restructured later.