Odds are -ck deleted it from his
pool thread because:
a) your post had nothing to do with the solo pool itself that he runs and -ck really wants to have nothing more to do with supporting the
publicly available ckpool code. Hell, last year ck was considering closing the solo pool... It took some
fools folks donating to him to pay for the servers that made him keep it open. Turns out it was good that he took them up on the offer considering he made a nice bit of coin off of his 2% cut of the several blocks the folks in the pool found since then... As he posted in the pool thread the other day it was more than enough to pay for the next year of running the pool
b) Since he locked the ckpool software thread (and his git for it) long ago you should have opened a new topic in the
Mining Software area - not the pools area.
That said, the ckpool software is
not something that you just download, install, and run. There's good reason that the folks behind Laurentia pool paid -ck a hefty consultant fee to set it up for their project.
There are a lot of tweaks (settings) that the operator must do to even be able to run it some of which are not pre-coded - you have to know how/what to edit and/or add code to suit your needs. Um, things like having the block payout automatically sent to the main recipient be it a solo miner or a pool wallet for distribution to the pool members + a % of total rewards
that you set to the pool operator wallet. That starts the history of newly generated coins with a perfectly clear record of where the new coins came from and were they were 1st sent to start their life as part of the
BTC blockchain.
BTW: that initial identification of the 'parents' the coins went to is an entirely different thing vs the diversion of hash rate that several hacked miner firmwares use to enforce the fee for using their hacked (which by being closed source, violates the cgminer GPL) firmware.
Odds are the various readme files cover the bulk of you have to do.