You know what the word, bot implies yet shouldn't something be said about FOSSbot? FOSS remains for nothing, open-source programming. This Steem voting bot which made is free and open-source. I just sent my FOSSbot a couple of days prior and needed to impart this unimaginable asset to you so you can profit moreover. The reason I favor this voting bot is that I have control over my private keys and don't need to confide in any other person.
GitHub
Heroku
Heroku is a cloud supplier. This implies you won't need to run your bot all alone PC. It will keep running on the Heroku cloud. While making your free Heroku account, it will request your Mastercard data. This is on account of some dynos can cost cash on Heroku however steem-fossbot-voter was intended to work inside the free record. Indeed, even a few duplicates won't break into the paid administrations that Heroku gives. It won't utilize your charge card without you overhauling your record physically. Coincidentally, I don't work for Heroku. I'm just a client. Up until now, I'm utilizing the voting bot as a free record.
Image source
In GitHub, go to the steem-fossbot-voter venture.
Look down until the point when you get to installation'.
Tap THE PURPLE Catch: Convey TO HEROKU
Image source
FILL IN THESE FIELDS:
STEEM_USER: Put your Steem account name here without the @
POSTING_KEY_PRV: Your private posting key goes here
BOT_API_KEY: a secret key for your bot
Note: this ought not have any spaces and be irregular, for instance:
AOUNA039NA9SDJ
THAT IS ALL THE REQUIRED Data YOU FILL IN.
You can leave these clear:
EMAIL_ADDRESS_TO
EMAIL_ADDRESS_SENDER
SENDGRID_API_KEY
You can leave these as the default:
COOKIE_SECRET
VERBOSE_LOGGING
HIT THE Convey Catch
Hold up a couple of minutes. The organization can take a few minutes and beneath the convey catch you will see it happening. Give it an opportunity to finish. On the off chance that you have a disappointment on account of sendgrid you can contact Heroku support and they will settle it. I needed to make a help ticket in Heroku for the sendgrid issue, however it was settled rapidly.
The reason you have to fork the undertaking is to guarantee that your voting bot gets consequently refreshed when changes are made to the GitHub venture.
Come back to the steem-fossbot-voter on GitHub.
At the upper right you will see a dim catch that says FORK.
Snap that FORK catch to make your own storehouse. You can utilize it for at least one bots you just need to fork it once.
Since it is forked you will come back to Heroku and tap the purple hexagon symbol for your voting bot application in the Dashboard.
Inside the Heroku dashboard for that application you will see a Send tab, click it.
Select GitHub as the organization strategy and sort steem-fossbot-voter in the hunt box.
Select your vault when it discovers it.
To naturally refresh your voting bot when rolls out an improvement look down and click Empower Programmed UPDATES.
Image source
Presently you have to influence your bot to vote hourly, and furthermore disclose to it which creators to vote in favor of. There are a wide range of parts of your bot's calculation to arrange, yet for effortlessness, we are just going to set the bot to vote each hour, and to vote in favor of specific creators.
Go to the Assets tab in your Heroku Dashboard and tap on the HEROKU SCHEDULER.
Another program tab or window will open with the extra settings.
Tap the Include New Occupation catch.
Sort in hub bot.js in to the content box.
Set the recurrence from Day by day to Each Hour.
Tap the Spare catch.
The undertaking has now been made.
To add creators to your voting bot, you have to Tap THE OPEN Application Catch
At that point Tap ON Alter CONFIG
Add the names of creators to a whitelist, putting a clear space in the middle of each name.
YOU'RE Finished!
This is an extremely barebones instructional exercise, and to get the most out of your voting bot, you'll have to explore different avenues regarding the distinctive parameters of the calculation
warning
Use it at your own risk
If you like then