How to Configure Repocket with Email and API Key in InternetIncome

Set your Repocket credentials in the properties.conf file using the variables REPOCKET_EMAIL and REPOCKET_API, then run ./internetIncome.sh --start to launch the container automatically.

The engageub/internetincome repository orchestrates passive income applications inside Docker containers. Configuring Repocket requires editing a single configuration file so the main script can authenticate with Repocket's servers on your behalf.

Configuration File Structure

The script stores user credentials in properties.conf at the repository root. Lines 11–13 define the Repocket-specific variables:

• REPOCKET_EMAIL – Your registered Repocket email address.
• REPOCKET_API – Your Repocket API key from the account dashboard.

When the container starts, these values are mapped to the internal environment variables RP_EMAIL and RP_API_KEY expected by the official repocket/repocket Docker image.

Startup Logic in internetIncome.sh

Starting at line 528, internetIncome.sh validates that both variables are non-empty before pulling the image:

if [[ $REPOCKET_EMAIL && $REPOCKET_API ]]; then
    echo -e "${YELLOW}Starting Repocket container..${NOCOLOUR}"
    sudo docker pull repocket/repocket
    check_container_exists repocket$UNIQUE_ID$i
    sudo docker run -d \
        --name repocket$UNIQUE_ID$i \
        --restart=always \
        $NETWORK_TUN $LOGS_PARAM $DNS_VOLUME \
        -e RP_EMAIL=$REPOCKET_EMAIL \
        -e RP_API_KEY=$REPOCKET_API \
        repocket/repocket
else
    echo -e "${RED}Repocket Email or Api is not configured. Ignoring Repocket..${NOCOLOUR}"
fi

If either variable is missing, the script skips Repocket and continues with other enabled apps.

Step-by-Step Configuration Guide

1. Edit properties.conf

Open the configuration file in your preferred editor:

vi properties.conf

Locate the Repocket section (around lines 11–13) and add your credentials. Use single quotes to protect special characters:

REPOCKET_EMAIL='your.email@example.com'
REPOCKET_API='abcd1234efgh5678ijkl9012mnop3456'

Save and exit the editor.

2. Start the Service

Execute the main script with the --start flag to launch all configured containers, including Repocket:

sudo bash internetIncome.sh --start

You should see output similar to:

Starting Repocket container..
Container repocket<unique-id> started successfully.

3. Verify Container Operation

Confirm the container is running and view its logs:

sudo docker logs -f repocket<unique-id>

Replace <unique-id> with the suffix displayed during startup. The logs will show Repocket's internal status messages and indicate whether the API key authentication succeeded.

Docker Networking and Proxy Support

The container attaches to the optional proxy network defined by $NETWORK_TUn (configured via proxies.txt). This routes Repocket traffic through any proxies you have enabled, allowing you to run multiple instances across different IP addresses without modifying the Repocket configuration itself.

Summary

• Credential location: properties.conf variables REPOCKET_EMAIL and REPOCKET_API (lines 11–13).
• Internal mapping: Script passes these as RP_EMAIL and RP_API_KEY to the container.
• Validation: internetIncome.sh checks for empty strings at line 528 and aborts the Repocket step if credentials are missing.
• Image: Uses the official repocket/repocket image with --restart=always for persistence.
• Networking: Automatically integrates with the proxy network if $NETWORK_TUN is defined.

Frequently Asked Questions

What are the exact variable names for Repocket credentials?

Use REPOCKET_EMAIL and REPOCKET_API inside properties.conf. The script maps these to RP_EMAIL and RP_API_KEY when launching the Docker container, matching the official Repocket image's requirements.

Can I run Repocket through a proxy with InternetIncome?

Yes. If you have configured proxies in proxies.txt, the script includes $NETWORK_TUN in the docker run command, attaching the Repocket container to the proxy network. Traffic will route through the assigned proxy automatically.

How do I check if Repocket is running correctly?

Run sudo docker logs -f repocket<unique-id> to view real-time logs. Successful authentication will show status updates from the Repocket client. If the API key is invalid, the logs will display authentication errors.

What happens if I leave the Repocket fields empty?

The startup script detects empty variables and prints "Repocket Email or Api is not configured. Ignoring Repocket.." in red text. It then skips the Repocket container and proceeds to start any other enabled applications.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}