Started off the morning with two classes: Body Pump and RPM.
It’s currently the end the holiday season in France at the moment, so this week my gym is running “video sessions” – no instructor, but we follow the class on the TV.
I also participated in the evening BodyPump class – edition 113.
A situation that happens often – you’re working on a repository (GitHub for example) also want your commits automatically mirrored to anther repository.
The obvious solution is to add a second remote, but that means having to constantly remember to push to both remotes.
After playing around with the idea of aliases and hooks, I fell upon a little-known Git feature – secondary fetch and push URLs.
We can add additional fetch and push URLs for a remote by using the reite set-url
For example, to add https://my-backup-remote as a remote for the current
git remote set-url –add –push origin https://my-backup-remote
Taking a peek at the .config fileL
[remote “origin”]
url = https://github.com/alanapz/snorlax.git
fetch = +refs/heads/*:refs/remotes/origin/*
pushurl = https://github.com/alanapz/snorlax.git
pushurl = \\\\192.168.1.40\\public\\projects\\snorlax
And
C:\dev\adista\snorlax>git remote show origin
* remote origin
Fetch URL: https://github.com/alanapz/snorlax.git
Push URL: https://github.com/alanapz/snorlax.git
Push URL: \\192.168.1.40\public\projects\snorlax
HEAD branch: master
Remote branch:
master tracked
Local ref configured for ‘git push’:
master pushes to master (up to date)
C:\dev\adista\snorlax>git push origin head -v
Pushing to https://github.com/alanapz/snorlax.git
To https://github.com/alanapz/snorlax.git
= [up to date] head -> master
updating local tracking ref ‘refs/remotes/origin/master’
Everything up-to-date
Pushing to \\192.168.1.40\public\projects\snorlax
To \\192.168.1.40\public\projects\snorlax
= [up to date] head -> master
updating local tracking ref ‘refs/remotes/origin/master’
Everything up-to-date
Notice that fetches are not affected – we fetch from only the fetch URL (perfect – it doesn’t really make sense to fetch from our backup remote).
C:\dev\adista\snorlax>git fetch -v From https://github.com/alanapz/snorlax = [up to date] master -> origin/master
Quick, easy & dirty !
My latest project is a basic SonarQube reporting tool, used to generate e-mail reports on unassigned and open issues by user and project.
Snorlax is designed do to two things:
The easiest way is via Docker for Linux:
docker run -it
-e SNORLAX_SONAR_URL=*SonarUrl*
-e SNORLAX_SONAR_TOKEN=*ApiToken*
-e SNORLAX_SMTP_SERVER=*SmtpServer*
docker.io/alanmpinder/snorlax:1.0
See README.md for a list of all supported environment variables.
So as you can see, I have recently re-setup my blog.
Everything seemed to go smoothly up until I tried installing a theme (either directly or via file-upload), whereupon I would receive the same error message every time:
Error: WordPress could not establish a secure connection to WordPress.org
I wasted a couple of hours upgrading PHP, CURL, OpenSSL as well as my the OpenSSL root before stumbling upon https://wordpress.org/support/topic/error-wordpress-could-not-establish-a-secure-connection-to-wordpress-org/
This user had exactly the same problem, which he traced to an incompatibility between Curl and SSL with regards to IPV6.
Following his advice, I added just before the end of __construct in wp-includes/Requests/Transport/cURL.php the following line:
curl_setopt($this->handle, CURLOPT_RESOLVE, array("api.wordpress.org:80:198.143.164.251", "api.wordpress.org:443:198.143.164.251"));
It’s an absolute terrible hack (hard coded IP addresses what could possibly go wrong!) but at least I can install themes on this blog now. So many thanks PeterBB, and eagerly awaiting a resolution to https://meta.trac.wordpress.org/ticket/3090
Welcome to WordPress. This is your first post. Edit or delete it, then start writing!