7/2/2023 0 Comments Keybase files![]() ![]() vendor/bin/jigsaw serve to preview that our file shows up as expected at Once I commited the changes and the site deployed, everything was fine on the Keybase side! Now we can run php /vendor/bin/jigsaw build to create our build and. Just remember the path will be relative to where config.php is located. Since I already dropped my keybase.txt file into the source folder I went ahead and used this path. So we'll want to add this value to our config.php: You'll note our GenerateKeybaseFile class introduces a hard dependency on having a configuration value keyBaseFilePath. $events->afterBuild(App\Listeners\GenerateKeybaseFile::class) Mkdir($jigsaw->getDestinationPath().'/.well-known') įile_put_contents($jigsaw->getDestinationPath().'/.well-known/keybase.txt', $keyBaseFile) Īnd called my new class from bootstrap.php: If (!is_dir($jigsaw->getDestinationPath().'/.well-known')) $keyBaseFile = file_get_contents($pathToFile) $pathToFile = $jigsaw->getConfig('keyBaseFilePath') I created a new listener class in listeners/GenerateKeybaseFile.php: My own familiarity with Laravel came in handy as I opened up bootstrap.php to see an example of creating a PHP class to listen to the events emitted by Jigsaw. I wanted to check out Jigsaw as it is built using Laravel. I specifically chose Jigsaw for my static site generator because I've previously used and enjoyed. ![]() Fair enough, Jigsaw makes no such claims and I read in the documentation there are events that I can create listeners for. I noticed this assumption was incorrect when I ran php vendor/bin/jigsaw build production the. When I tried this, I added the file to source/.well-known/keybase.txt thinking that Jigsaw may automatically pick that file up and place it in the root of my build folder, and thus it would get deployed automatically to my Netlify host. Since I left my WordPress server running it is no big deal for me to grab the file and drop it into the repo. Keybase sent me an email with the subject "your web () proof just broke" letting me know that I needed to replace the file or revoke the proof. I recently converted my WordPress site over to a static site (using TightenCo's Jigsaw and ran into a problem I figured others might also: my Keybase.io web site verification failed because the URL to my verification file no longer exists. ![]()
0 Comments
Leave a Reply. |