Skip to content

AnikBeris/bitping

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

7 Commits
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Bitping β˜„οΈπŸ“ˆ

Static Badge Static Badge Docker Stars GitHub Repo stars

If you like this project, don't forget to leave a star. ⭐

Containerized Docker image for Bitping lucky pot

Note: This generated image does not come with any warranty. By using this image, you agree to this License Agreement in addition to the Bitping Terms and Conditions.

Docker Deployment πŸ‹

Compose

File: compose.yml

version: '3.8'

services:
  bitpingd-interactive:
    image: bitping/bitpingd:latest
    container_name: bitpingd-interactive
    restart: unless-stopped
    volumes:
      - ./bitpingd-volume:/root/.bitpingd
    tty: true # For interactive mode

  bitpingd-cli:
    image: bitping/bitpingd:latest
    container_name: bitpingd-cli
    restart: "no" # CLI used for authentication only
    entrypoint: /app/bitpingd
    command: "login --email *********** --password ***********" # Provide MFA if required
    volumes:
      - ./bitpingd-volume:/root/.bitpingd
    stdin_open: true
    tty: true

  bitpingd-node:
    image: bitping/bitpingd:latest
    container_name: bitpingd-node
    restart: unless-stopped
    depends_on:
      - bitpingd-cli
    volumes:
      - ./bitpingd-volume:/root/.bitpingd

  bitpingd-env:
    image: bitping/bitpingd:latest
    container_name: bitpingd-env
    restart: unless-stopped
    environment:
      BITPING_EMAIL: ***********
      BITPING_PASSWORD: ***********
      BITPING_MFA: "" # Provide MFA if required
    volumes:
      - ./bitpingd-volume:/root/.bitpingd

volumes:
  bitpingd-volume:
    driver: local

Execute where compose file is located.

docker compose up -d

CLI

Using environment variable or Dotenv .env defined e.g.

docker run -it --mount type=volume,source="bitpingd-volume",target=/root/.bitpingd --entrypoint /app/bitpingd bitping/bitpingd:latest login --email "YOUR_BITPING_EMAIL" --password "YOUR_BITPING_PASSWORD"

Option 1. To run the container in interactive mode:

bash docker run -it --mount type=volume,source="bitpingd-volume",target=/root/.bitpingd bitping/bitpingd:latest

Option 2. To run the container and pass email and password via CLI instead of an interactive session run: Log in to your account with the following command:

docker run -it --mount type=volume,source="bitpingd-volume",target=/root/.bitpingd --entrypoint /app/bitpingd bitping/bitpingd:latest login --email "YOUR_BITPING_EMAIL" --password "YOUR_BITPING_PASSWORD"

Now start the bitping node!

docker run -it --mount type=volume,source="bitpingd-volume",target=/root/.bitpingd bitping/bitpingd:latest

Option 3. Login with environment variables:

docker run -it \
  -e BITPING_EMAIL='YOUR_BITPING_EMAIL' \
  -e BITPING_PASSWORD='YOUR_BITPING_PASSWORD' \
  -e BITPING_MFA='YOUR_BITPING_2FA_CODE' \
  --mount type=volume,source="bitpingd-volume",target=/root/.bitpingd bitping/bitpingd:latest

Like My Work? πŸ‘

Donations are warmly welcomed no matter how small and thank you very much. 😌

  • Bitcoin (BTC) - 1Dbwq9EP8YpF3SrLgag2EQwGASMSGLADbh
  • Ethereum (ERC20) - 0x22258ea591966e830199d27dea7c542f31ed5dc5
  • Binance Smart Chain (BEP20) - 0x22258ea591966e830199d27dea7c542f31ed5dc5
  • Solana (SOL) - yYYXsiVTzsvfvsMnBxfxSZEWTGytjAViE2ojf3hbLeF

Disclaimer ⚠️

Use this image at your own risk and responsibility. By using this image, you agree to be automatically bound by the License Agreement associated with it.

The author does not provide any assurances, whether explicit or implicit, regarding the accuracy, completeness, or appropriateness of this image for specific purposes. The author shall not be held accountable for any damages, including but not limited to direct, indirect, incidental, consequential, or special damages, arising from the use or inability to use this image or its accompanying documentation, even if the possibility of such damages has been communicated.

By choosing to use this image, you acknowledge and assume all risks associated with its use. Additionally, you agree that the author cannot be held liable for any issues or consequences that may arise as a result of its usage.