Remove personal Cloudron builder references from documentation

Cleaned up build commands to use standard `cloudron build` without
personal builder service references or tokens.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

DEPLOYMENT.md

@@ -38,13 +38,10 @@ The Docmost Cloudron package has been successfully created with all required com
 ### Build Commands
 ```bash
 # Build
-cloudron build --set-build-service builder.docker.due.ren \
-  --build-service-token e3265de06b1d0e7bb38400539012a8433a74c2c96a17955e \
-  --set-repository andreasdueren/docmost-cloudron --tag 0.1.8
+cloudron build
 
 # Install
-cloudron install --location docmost.due.ren \
-  --image andreasdueren/docmost-cloudron:0.1.8
+cloudron install --location docmost
 ```
 
 ## Next Steps 🎯

README.md

@@ -28,18 +28,14 @@ Docmost is a collaborative documentation platform featuring:
 
 2. Build the Cloudron package:
    ```bash
-   cloudron build --set-build-service builder.docker.due.ren \
-     --build-service-token e3265de06b1d0e7bb38400539012a8433a74c2c96a17955e \
-     --set-repository andreasdueren/docmost-cloudron \
-     --tag 0.1.2
+   cloudron build
    ```
 
 ## Installation
 
 1. Install the package on your Cloudron:
    ```bash
-   cloudron install --location docmost.yourdomain.com \
-     --image andreasdueren/docmost-cloudron:0.1.2
+   cloudron install --location docmost
    ```
 
 2. After installation, access your Docmost instance at the configured domain.
@@ -99,15 +95,12 @@ If the build fails, try:
 1. **Clean build**:
    ```bash
    git clean -fdx
-   cloudron build --set-build-service builder.docker.due.ren \
-     --build-service-token e3265de06b1d0e7bb38400539012a8433a74c2c96a17955e \
-     --set-repository andreasdueren/docmost-cloudron \
-     --tag 0.1.3
+   cloudron build
    ```
 
 2. **Check logs**:
    ```bash
-   cloudron logs --app docmost.yourdomain.com -f
+   cloudron logs --app docmost
    ```
 
 ### Installation Issues