The second round of the Playoffs has come to a close, and it’s been a nice mixture of surprises and things that went almost exactly as anticipated.
1. Cavs vs 4. Hawks
Despite my Cavs in six prediction, early in the series it was clear that Atlanta didn’t stand a real chance against these Cavs, that have now a full 10-men rotation in place, and that have found an exceptionally great mojo from downtown. They played four games in both of their rounds so far, which means not so much playing time and lots of rest, which will surely come in handy in the conference finals.
2. Raptors vs 3. Heat
Could I have been any more wrong about this? I don’t think so. The injuries to Valanciunas and Whiteside proved to be tough to overcome, but the series has given us plenty of highlights: Dwyane shining like its 2010, the initial struggle of Lowry that was able to recover from his slump and make huge plays in games 5, 6 and 7, and Bismack Biyombo running for Toronto’s mayor office. The Raptors reached the conference finals for the first time in their history: they won’t get much farther away than that, but boy was this a great playoff run!
1. Warriors vs 5. Trail Blazers
I predicted Portland to be able to win at least a couple in the series, but I clearly though that Curry’s injury would impact the Warriors much more severely. What Steph has done in game 4 is something, yet another thing, that you’ll likely tell your grandchildren. Golden State went through some moments though in which they didn’t look completely in control, and will have to get some things in order (Green techs, for one) before the conference finals, since…
2. Spurs vs 3. Thunder
… the Thunder pulled off the biggest surprise in these Playoffs so far, by convincingly slamming away the Spurs in six games. Westbrook wasn’t probably at his best, Durant looked great, which is something that we haven’t seen in a while, and their phisical presence was phenomenal against a San Antonio team that failed at doing what they do best than everyone else, which is executing on offense. Two names stand above the others: Steven Adams, a true presence in the paint, and Billy Donovan, a rookie coach straight from college that has made the one thing that few, me included, thought possible, which was instilling a winning mentality in his guys.
Conference finals predictions
1. Cavs vs 2. Raptors
Toronto won the season series against Cleveland, but it’s clear that these Cavs are something else. They’re playing with confidence, and if the shots are going in like they have, it’ll all be over soon. Still, the Raptors have the men to guard both the perimeter and the paint (also, how about giving James Johnson some minutes now?), and if DeRozan gets a little confidence (that’s a giant “if”), they might be able to sneak a couple of wins. Cavs in 5.
1. Warriors vs 3. Thunder
This series is much closer to call than it would seem. OKC have the confidence on their side, they lost the regular season series against Golden State, but they were the ones that looked best against the Warriors. Again, Golden State must regain some composure and some flow, they desperately need to have Green mentally in control, and they need to have Harrison Barnes back in it, since he has been a non-factor so far. Steph gonna Steph, KD gonna KD, Russ gonna Russ, and the Thunder better pound the inside, with Adams and Kanter. All I want for Christmas is this series to last seven games. Warriors in 7.
If you’re like me and began to do what you do more than a decade ago, you’ll definitely remember how we all used to push updates to our production servers via FTP. There’s no shame in that: we’ve all been beginners.
Using FTP might even be fine today for teeny-weeny projects, but two things are for sure:
- it’s slow,
- it will almost always lead to uncertainty regarding the syncronization between your local copy of the project, and the remote one on the server (even if I hear that some people still develop directly on a server, but that’s a rant for another occasion).
Luckily for us, we have version control systems such as Git and our work is never really lost.
So how can we avoid using FTP to upload updates to our production servers?
You set up a new repository that’s hosted on the very same production server you’ll project will end up on and also push updates to that repository.
So let’s assume that you have developed a theme for WordPress and you want to keep it in sync with your local copy.
I wouldn’t want to have the theme folder on the production server to host the repository itself, so I’d opt to set it up in a folder outside
public_html and then listen for
push events on that repository and perform a checkout of the project to the actual theme folder.
So, since I’m lazy, I’ve created a little script to make my life easier:
#!/bin/sh rm -rf $1.git mkdir -p $1.git cd $1.git git --bare init cat <<EOF >hooks/post-receive #!/bin/sh mkdir -p $2 export GIT_WORK_TREE=$2 git checkout -f EOF chmod +x hooks/post-receive
You can create a file (let’s say
create-repo.sh) in the folder that will host your repositories on the server, adjust the file permissions so that it can be executed (
chmod +x ./create-repo.sh), and launch it with the following syntax:
./create-repo.sh repository-name path-to-actual-folder
This script does the following things in sequence:
- remove any pre-existing repository with the specified name,
- set up a new blank repository in a specific folder whose name is indicated by the first parameter (in our case
- create a hook that is triggered upon receiving a
pushthat will perform the checkout in the actual project folder (second parameter passed to the script, in our case
So, assuming that you have a standard WordPress installation in the root directory, you could create a repository that points to the themes folder:
./create-repo.sh your-theme-name /home/your-user/public_html/wp-content/themes/your-theme-name
The only remaining thing is to upload stuff to the production server, for which you’ll have to create a new
remote pointing to the newly created repository through SSH and then execute a
push towards said
assuming that you’ve created the repository in a
repos folder in your home directory, which I’d recommend.
As you can see, this is nothing too complex, but it’s a pretty nice time saver nonetheless.
In Genova we’ve got a word that defines the typical narrow intricate street that form the historic center of our city, and that word is caruggio. There are hundreds and hundreds of those streets.
So today I found myself wandering around a few of them in search for a place to eat, and given the particularly pleasant weather, I took a couple of shots.