What's already configured out of the box
The one-click deployment pulls the official getmeili/meilisearch Docker image, mounts a persistent data volume, and starts the engine in production mode with a randomly generated master key — this single automated step covers what would otherwise be manual one click automation for Meilisearch setup: image pull, volume mount, and key generation. Meilisearch listens on port 7700 by default and requires no separate database; all indexes live inside its own storage engine.
First login and authentication
Meilisearch has no traditional admin panel with a username/password login — access is entirely API-key based. The master key generated at deployment is required to create and query indexes; you'll find it either in the Leneex panel's environment variables view or in deployment logs.
Working with your instance
Once you have the master key, use it to call the REST API directly (POST /indexes/{index}/documents) or connect one of the official SDKs (JavaScript, Python, PHP, Ruby, Go, Rust) to start adding and querying documents. For anything beyond a quick curl test, generating scoped API keys through the /keys endpoint — rather than using the master key in client-facing code — is the documented security practice.
Back up your data periodically using Meilisearch's dump export feature before major version upgrades, since dumps are the supported path for migrating between releases.