What's already configured out of the box
After a one click automation Appsmith deploy, Docker Compose starts a single container running the Appsmith server, mapped to ports 80 and 443 with restart: unless-stopped, so it comes back up automatically after a server reboot. All app definitions, datasource credentials, and plugins persist in the appsmith-stacks volume mounted into the container — that folder is what you'd back up if you ever need to migrate the instance.
First login and admin setup
Open your server's IP address or domain in a browser after deployment — the first boot can take several minutes while internal services finish starting. There's no default username or password to dig up: Appsmith shows a signup form on first visit, and whatever email and password you enter there becomes the workspace's administrator account. From that point on, invite additional users from inside the Appsmith admin settings rather than sharing the original login.
Connecting data sources
New datasource connections — PostgreSQL, MongoDB, a REST API, whatever the app needs — are added from inside the Appsmith UI under Datasources, not through server configuration files. If the database you're connecting to lives on the same Leneex VPS, keep the connection on the internal network rather than routing it through the public internet. For anything reached over the public internet, make sure the VPS firewall allows outbound traffic to that database's port before adding the connection.