SSL Software Suite Changes Primer Tutorial
It was kind of sad us not envisaging SSL requirements down the track with a lot of our software here at RJM Programming. Kind of sad, but also “kind of useful”, as we like to revisit code, and we’ll be soon outlining another reason, the essence of which is the platforms you work on can change their rules too. But more on that later. Today, we are showing you a semi-automated approach to compartmentalizing SSL change work to do by …
- Identify a “software set” as a “suite of software” in your mind to compartmentalize a big job into “littler job chunks” … ours, today, is our Google Charts interfacing (PHP) suite of software web applications, which all sit in subfolders off our RJM Programming domain’s public https://www.rjmprogramming.com.au/PHP/ web server place
- Download from the public (ours is Apache/PHP/MySql Linux CentOS virtual web server) domain everything (ie. more than you will actually alter) from that (hopefully up at the public domain) foldered web server file organizational structure, to a local web server (and ours is an Apache/PHP/MySql MAMP local web server on a Mac OS X MacBook Pro system) … we use the great FileZilla these days for this (s)ftp file transferring … serves two purposes …
- at MAMP will be a backup of a snapshot in time of that “suite of software” (with all the context of both changed files, and ones that weren’t)
- a place to make lots of semi-automated edits and be able to validate those edits (via “php -l [phpFile]”) and, as required, unit test the changes via (local MAMP web server) URLs like http://localhost:8888/PHP/PieChart/pie_chart.php
- Make those semi-automated edits in equivalent of MAMP http://localhost:8888/PHP ( which is /Applications/MAMP/htdocs/PHP on a lot of Mac OS X systems) via …
- first round of “fgrep ‘file_get_contents(‘ */*.php” to check out a few exceptional cases where we’ll call into play the rule (around here) that we never, in an automated way, change uppercase “HTTP:” usages, which we’ll actually call into play for “file_get_content(‘http:” scenarios (we discovered the issue with back at SSL Recent Post ImageMagick Thumbnail Tutorial)
- main round of lots of strung together (aided by the Terminal application’s Edit menu’s Copy and Paste options) “vi” commands of relevant PHP files to edit in that ” <ESC> key … g/http:/s///g … wq! ” approach
- Upload to the public (ours is Apache/PHP/MySql Linux CentOS virtual web server) domain each relevant (MAMP) local web server folder’s most recently changed PHP files (aided by FileZilla’s Date Modified sorting functionality)
This approach above is obviously just a guideline, and you may prefer to involve source control, or have to. Either way, there will be a Downloading aspect, and a Make Changes aspect and an Uploading aspect to many of the approaches out there to achieve the same ends.
Again, though, we have to emphasise here, how good is MAMP … so … “How good is MAMP, man person!?” … (the installing of which would have to be) the first piece of advice we’d ever suggest to anyone interested in PHP development … I’d even say the same to people who only want to get into HTML and Javascript only, as it is really good just to have this local web server going on, as much as anything for testing purposes in a local web server system using proper http: protocol URLs at the web browser address bar. You can see some of all this happening with our tutorial picture today.
If this was interesting you may be interested in this too.
