Deploy LinkDrop with livemy.app and test three accounts

Inspect the repository before deployment

Thanks to livemy.app for sponsoring this video.

The recording starts with LinkDrop working on localhost. Its public repository is linked with the video so the demonstrated app can be inspected.

1. Confirm the intended repository and working version.
2. Follow the GitHub deployment path shown at 1:17.
3. Check the detected stack and deployment result rather than assuming localhost behaviour carries over.
4. If a secure-connection error appears, diagnose it through the hosting configuration; do not bypass a browser security warning.

Connect the coding agent and deploy the upgraded build

The later sequence connects livemy.app through MCP and adds a real database and authentication. Those additions need a new deployment and new tests.

1. Use the demonstrated MCP setup with the coding client you use.
2. Define the saved profile data and account access requirements.
3. Deploy the upgraded build and inspect the deployment report or logs.
4. Open the public URL independently of the local development session.

Test separate users and persistence

Luke tests three accounts using throwaway data. A single logged-in preview cannot establish isolation.

1. Create three test accounts and give each distinct profile values.
2. Save, sign out and sign back in to check persistence.
3. Confirm one account cannot inspect or change another account’s profile.
4. Review the available logs, backups and domain controls, then record anything still unresolved before release.

The takeaway

The roughly two-minute edited deployment sequence is specific to this run. A public URL still needs authentication, data and recovery checks.