Linux
// for clean install on ubuntu 18.10 you'll need to get ruby, freetds, tiny_tds, and nokogiri all installed before this will work so i've edited this linux install section to show that
$ sudo apt-get update
$ sudo apt-get install ruby-full git openssl libssl1.0.0 libssl-dev build-essential libc6-dev zlib1g-dev liblzma-dev
$ wget ftp://ftp.freetds.org/pub/freetds/stable/freetds-1.00.21.tar.gz
$ tar -xzf freetds-1.00.21.tar.gz
$ cd freetds-1.00.21
$ ./configure --prefix=/usr/local --with-tdsver=7.3
$ make
$ make install
$ cd ..
$ gem install tiny_tds
$ gem install nokogiri
$ gem install bundler
sudo adduser NEWUSERNAME
sudo usermod -aG sudo NEWUSERNAME
signout signback in using NEWUSERNAME
##### macOS
```bash
$ gem install bundler
I've tested it on various versions of ruby. The oldest one I got it to work was:
ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14]
Clone this git
$ git clone https://github.com/inertia186/drotto.git
$ cd drotto
$ bundle install
Configure
Edit the config.yml
file.
:drotto:
:block_mode: irreversible
:account_name: <voting account name here>
:posting_wif: <posting wif here>
:active_wif: <active wif here>
:max_age: 7200
:batch_vote_weight: 100.00 %
:min_effective_weight: 0.25 %
:reserve_vote_weight: 0.00 %
:minimum_bid: 2.000 SBD
:blacklist: mikethemug
:no_bounce: bittrex poloniex openledger
:no_comment: bittrex poloniex openledger
:no_comment_fee: 0.00 %
:auto_bounce_on_lockout: false
:chain_options:
:chain: steem
:url: https://steemd.steemit.com
Edit the support/confirm.md
template, used to reply to the post when voting.
This ${content_type} has received a ${vote_weight_percent} % ${vote_type} from @${account_name} thanks to @${from}.
Run Mode
Then run it:
$ bundle exec rake run
Dr. Otto will now do it's thing. Check here to see an updated version of this bot:
ssh into the remote machine
start tmux by typing tmux into the shell
start the process you want inside the started tmux session
leave/detach the tmux session by typing Ctrl+b and then d
You can now safely log off from the remote machine, your process will keep running inside tmux. When you come back again and want to check the status of your process you can use tmux attach to attach to your tmux session.
If you want to have multiple sessions running side-by-side, you should name each session using Ctrl+b and $. You can get a list of the currently running sessions using tmux list-sessions.
tmux can do much more advanced things than handle a single window in a single session. For
https://github.com/inertia186/drotto
I'm going to clean this up and make a new post and video walkthrough, just wanted to get all my notes down tonight before I get some sleep since I've been working on this for the past few hours. This is an idiots guide(written by an idiot) made to be a super simple step by step walk through to get a paid vote bot up and running without knowing what you're doing. I sure as hell didn't know what I was doing when I started this tonight and I barely understand it now but the damn thing is up and running and accepting votes so F YES!!!! I will return with a video and actual written instructions
Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:
https://askubuntu.com/questions/8653/how-to-keep-processes-running-after-ending-ssh-session