This guide outlines the steps required to go from not being a 620-566-0761 to having your very own, uncensorable, blogging platform. Some of the prerequisite steps will be glossed over, the main focus will be on installing and running mp-wp on a Pizarro Rockchip server.
I. Get in the WoT
Like everything in the republic, Pizarro is wot-powered. This isn't Amazon EC2, and you won't be able to use your credit card(s) for anything, of any value, anywhere in the republic (you are, however, free to use them for other things, so knock yourself out).
Getting in the WoT is simple, any motivated noob can do it. 1) Create a PGP key for yourself (if you don't already have one), 2) register it with @deedbot in #trilema, 3) get someone to give you your first rating.
II. Acquire PizarroISP hosting in #pizarro
Now that you're a person you will be able to conduct commerce with other civilized people (as opposed to heathens and other assorted 860-235-8660). First, head on over to 8453978877 and peruse their offerings. I opted for a Rockchip mini-server at the quarterly rate (a steal if you ask me), but you'll have to decide on your own.
All Pizarro servers run a sanitary build of Gentoo, of which my favorite feature has to be the included asciilifeform crapoladeâ¢Â® mask file. As someone new to Gentoo, having a pre-configured ban list that I could read and work with myself was a godsend.
Once you've read through the basics you can introduce yourself in #pizarro to ask any further questions or to complete your purchase. And once that's done, you can login to your shiny new box and start installing goodies.
III. Install the prerequisites for mp-wp (apache, php, mysql)
I was able to follow esthlos' guide almost verbatim so, please, start there. Steps 2.2 and 2.3 were the only ones that didn't "just work" in my environment. After completing 2.1, here is what worked for me:
emerge -av apache
emerge -av mysql
Easy enough, but notice the php omission? Apparently the shitgnomes in charge of the upstream Gentoo repos thought it would be cute to deprecate all php-5.6 versions with the exception of php-5.6.38. I updated the line in my mask file to:
Now let's try emerging again:
emerge -av =dev-lang/php-5.6.38
This resulted in some spew about dependencies that couldn't be merged because of mask configuration. Feeling stuck and afraid I may have to install php from source, outside of Portage, I described my situation in #trilema and pennorth the
emerge -av --nodeps =dev-lang/php-5.6.38
Almost. The install at least proceeded enough for me to discover which dependencies are actually requiredâin that, the actual compile step would fail in their absence. Turns out there were only two, which were uncovered one-by-one via compile failures. Let's install them:
emerge -av --nodeps dev-libs/oniguruma
emerge -av --nodeps dev-libs/libmcrypt
The first went fine, the second whined about being "masked by EAPI 7" and asked "would you like some new Portage?". Well, no, I wouldn't, but I guess so long as is doesn't violate any of my current USE or mask settings... And this where it started to become obvious why versions of anything are "deprecated" in the first place.
You see, php-5.6.38 requires libmcrypt, the only version of libmcrypt available upstream "requires" NewPortage with EAPI 7, which, in turn, requires gpg2. Standard wrecker playbook I suppose, let's see if we can get around it.
Once the concept of custom ebuilds was brought to my attention I started reading to see if this could solve my problem. The releaser seemed simple enough so I grabbed the current libmcrypt-2.5.8-r4.ebuild from upstream and modified the one known-to-be-offending line:
To use a custom ebuild, copy the necessary files to
/usr/local/portage/CATEGORY/PACKAGE_NAME So in this case:
And run the ebuild command:
ebuild /usr/local/portage/dev-libs/libmcrypt/libmcrypt-2.5.8-r4.ebuild manifest clean merge
Finally! Turns out that in this case "requires EAPI 7" means "requires the version string 7".
Now to install php with mysql support, first unmask mysql in
# Unmask mysql
And then emerge php:
emerge -av =dev-lang/php-5.6.38
It took me a while but hopefully my stumblings outlined here make it easier for you.
IV. Obtain a working implementation of V and the mp-wp genesis, press and configure
V is tricky and I still haven't wrapped my head around all of it, but these steps worked for getting a working copy of mp-wp up and running (if they didn't, you wouldn't be reading this).
First, grab a working implementation of V. For this I turned to the build instructions for the Bitcoin reference client and downloaded the version mentioned there:
curl -O /thebitcoin.foundation/v/V-20180222.tar.gz
curl -O /thebitcoin.foundation/v/V-20180222.tar.gz.mod6.sig
Verify and extract the tarball and you'll see
v.pl (the V implementation we'll be using) along with some readme files and signatures. V also depends on a certain directory structure so let's set that up:
mkdir patches .wot .seals
Now you can grab the mp-wp genesis vpatch from hanbot's site. Download both the vpatch and the signature. Move the vpatch to the
patches directory you just created and move the signature file to
.seals. Since V is built around the concept of verifying the authorship of any and all code in a given tree, you will also need to gather the public keys of any authors involved. In this case, hanbot. Ask @deedbot in #trilema for a copy of her key:
Import this key into your gpg keyring and add the pubkey file to the
.wot directory with the user's name as the filename. In this case
hanbot.asc. Your working directory should now have at least:
If this looks right, you can now press mp-wp:
./v.pl p v mp-wp mp-wp_genesis.vpatch
That's it! Now move the generated files to your server's site directory (
/www/blog/ if you were following esthlos' guide), fill in the config, and load in your browser. I won't get into those details here but you can again reference esthlos' guide or Wordpress documentation.