GIGIlistening…

Build Journal

Deploy Improvements & Wallet Disconnect Feature — April 16, 2026

I improved the deploy process and added a wallet disconnect feature to the portal. Here's how I tackled these updates solo using AI.

3 changes3 min readby Rob

What shipped

  • Improved Deployment WorkflowExtracted deploy script for local and CI SSH deployments.
  • Optimized Rsync ProcessExcluded .git directory from rsync to production.
  • Wallet Disconnect FeatureAdded DELETE API endpoint for linked-wallet management.
  • Keyword Scanner FixesResolved keyword bid ranks application issue on map.

Today, I worked on improving our deployment process and added the ability to disconnect wallets from the portal. I wanted to simplify my deployment process, as it has been somewhat complicated and to provide users with better control over their Web3 badges. What went live today includes a script for deployment and wallet disconnect functionality.

The first commit I worked on was moving the `deploy-vps-remote.sh` script. Before my process for deployments was getting really messy. I had everything jumbled up and it was hard to keep track of what deployments were in which environment. Now that I’ve separated out this script I can much more easily control deployments for both local and CI environments. It took me about a half hour to sort out the script, define the parameters, and verify that everything was working as expected. I asked Claude Code in VS Code to save me time with the smart things.

After that, I moved onto the rsync process. In my second commit I excluded the `.git` directory from being sent to production, which was a logical decision because I had been including the entire Git history which added unnecessary size to the deployment package. This exclusion was not only good practice for size but also sped up the transfer, which is really important for efficiency. I spent another 15 minutes testing to ensure that the only desired files were being synced and it worked perfectly.

I moved forward with my wallet disconnect feature. Users need to have vaults manage themselves and being able to disconnect a wallet gives users control. The new API endpoint `DELETE /api/me/linked-wallet` allows users to disconnect vaults safely. It only took me 20 minutes to implement and test, and I was happy to see how well it worked with the current Web3 badge control in the portal.

I reflected a lot as I did these updates about the implications each feature holds for my future as a solo developer. Each enhancement to the portal functions bolsters my belief in my vision to build a solo company valued at a billion dollars. Each step takes a while, but every commit brings me closer.

I fixed a few small bugs during the day with the keyword scanner on the map. I noticed that keyword bid ranks were not being applied when the portal param was present in the URL. I was able to resolve that issue by making sure the system did not make unnecessary replacements. That added about 15 minutes of work for me, but it was a good learning experience to manage state and parameters in the system better.

I'm happy with all the progress I made on these features. The updates on deployment will help my work process go along a lot smoother, and the wallet disconnect feature helps the users gain more control. I am eager to see the impact of these changes on user engagement and retention while I continue to build the agentic web and refine the portal. Each step forward reminds me of how powerful it is to let AI work as my team and help me handle the challenges of building the platform all by myself. I'm excited about the next challenges and the features that await.

← Back to the full build journal