What's already configured
One-click deployment brings up the Botpress server container connected to a PostgreSQL database that stores your flows, conversation history, and trained NLU models — that connection is set at install time, so nothing needs wiring by hand. The container restarts automatically if the server reboots, and BPFS (Botpress's internal file storage) persists your bot's files inside the database rather than the container's own disk, so redeploying the image doesn't wipe your work.
First login
Open the domain or IP pointed at your VPS — the admin panel is typically served on port 3000 by default, though Leneex's deployment usually maps this to your domain so you don't need the raw port. Botpress doesn't ship a default admin account: the first person to open the panel and register becomes the workspace administrator, so there's no factory password to hunt down in a config file. From there, create your first bot and connect a channel — Telegram and web-widget both just need a webhook URL, which is why HTTPS on your domain matters from day one.
About the engine version
This is the open-source Botpress v12 engine, distributed as a community-maintained Docker image rather than the vendor's newer cloud product — worth knowing if you're cross-referencing tutorials, since some newer documentation on Botpress's own site now covers Cloud-only features that don't apply here.