-
Notifications
You must be signed in to change notification settings - Fork 40
C) Manual Setup
If you don't want to use the automatic setup scripts you can follow these alternative steps to do the manual setup.
Using your preferred method get the latest version of this project and unzip it. For example you can go to the Releases tab to download the latest version.
Using the following referral links, register on the apps' sites. You should also receive a welcome bonus and at the same time you will effortlessly show that you appreciate my work (thank you so much).
- If you're using login with google remember to set also a password for your app account!
- Go to Earnapp
- Go to HoneyGain
- Go to IPROYAL
- Go to PACKETSTREAM
- Go to PEER2PROFIT
- Go to TRAFFMONETIZER
- Go to REPOCKET
- Go to BITPING
Edit and fill in the fields of the .env file with your data. The mandatory fields are shown below:
- Device_name: set any name you like
- Earnapp_Device_uuid: it must start with sdk-node- followed by an md5sum of a string of your choice
- HoneyGain _email and _password: just insert your account credentials
- Iproyalpawns _email and _password: just insert your account credentials
- Peer2profit_email: just enter your account email
- Packetstream_cid: enter the cid of your account. It's like a short token and you can find it in your packetstream's dashboard
- traffmonetizer_token: enter your token you can copy it from your traffmonetizer's dashboard
- Repocket _email and _password: just insert your account credentials
In the .env file you can also optionally configure proxies for each app and notifications about updates. Note that if you also set these optional fields you will also have to modify the docker-compose.yml file by uncommenting the relative lines.
- If you don't want to use an app just comment or delete the corresponding section in docker-compose.yml.
- Some apps have multiple configurations in the compose file to choose from (like the usage of docker volumes instead of volumes binding to folder). if you want to change the configuration from the default one, commenting on the options you don't want to use.
- This step is not needed if bitping is not used. Bitping needs to be started at least once in interactive mode for the first connection: before running the entire stack with all the apps. You can configure the bitping data opening a terminal and using the following command in the folder where you have already put the .env and docker-compose.yml files:
sudo docker run --rm -it -v ${PWD}/.data/.bitping/:/root/.bitping bitping/bitping-node:latestThis will create a subfolder containing all the necessary data, then enter your credential when prompted. Once this is done, use CTRL+C to stop the container and then proceed to the standard startup as shown in 4.b).
- Start all the apps just opening a terminal in the same folder where the .env and docker-compose.yml files are placed and using the command below:
sudo docker compose up -dAfter a few minutes you should be able to see the device in the dashboards of the various apps as active, connected and earning.
- This step is not needed if EarnApp is not used. For EarnApp after the first start-up phase it is necessary to claim your device in your account. To do so just go to the earnapp dashboard and then register it by copying the node_UUID previously saved in the .env file in this URL prototype (https://earnapp.com/r/<your_device_uuid>) and then copy the resulting real URL into your web browser. Your url should look like this: https://earnapp.com/r/sdk-node-dtrbf9f1437a4287947fd58b5ka4d7. Navigating to your url should register your node in your dashboard.
- Keep in mind if you have several ip, you can run a stack on each ip to increase revenue, but running several time this stack on same ip should not give you more. You can also install some of this apps on your smartphone and use also your mobile network to earn.
- While the docker stack is running you can acess the web dashboard navigating with your browser to http://localhost:8081/