CRNRSTN :: HOME

Welcome ::

Welcome to the CRNRSTN Suite :: documentation and support website! CRNRSTN is a free open source PHP class library that facilitates the operation of a LAMP application within multiple server environments (e.g. localhost, stage, production, .etc) effectively and properly joining the "wall of SERVER" to the "wall of application"...creating the two into one house. With this tool, data and functionality possessing characteristics which inherently create distinctions from one environment to the next...such as IP address restrictions, error logging profiles, and database authentication credentials...can all be managed through one framework for an entire application. CRNRSTN also provides a layer of encryption which can be configured for both cookie and session data.
 

Thank you for taking the time to check out the CRNRSTN Suite ::. If you would like to contribute to this project, consider following/watching this project on GitHub. View the project photo gallery.
 

As a "hat tip" to King Abdullah Bin Abdul Aziz's bold move to provide 500 tons of wheat to Syrian refugees in Jordan (as reported by Al Arabiya), as of today (1/16/2013 @ 0600), I am undertaking a slightly less noble...but just as sincere...effort to "help the people" through my creation of an open source enterprise level PHP class library for the management of a web application's integration into n+1 hosting ($_SERVER) environments. This body of code is completely new, and I am only leveraging resources and knowledge as is readily and freely available to the open source PHP community at large for the benefit of exactly the same. No part of any application that I developed whilst under the employ of any agency or for-profit business entity has been lifted and placed into this work. Due to the fact that I am currently being subjected to extensive surveillance protocols by an entity which bears an inscription...even written upon it's very forehead...which reads as "AMALEKITE PRINCESS", I have a high degree of confidence that the genesis of this project has been recorded and documented in a very thorough manner; there are witnesses who can vouch for the originality of this work.

History ::

When I entered the workforce in 2006 as an HTML developer making $35 an hour (after having to to step away from my internet start up company...where I was a full stack developer who was to be compensated through a stock offering upon going public), within the first few DAYS on the job, I was quietly using PHP to stand up tools to help me control the quality my HTML code via rendering it in an email to myself so that I could QA my code (and tweak it if necessary) before submitting my work to the team for the next step of the email marketing process. The quality of my email HTML code went from zero (0) to one hundred (100) real quick (within a day or so), and I (and our small team) knew immediately that things were going to work out. As far as I know, HTML email developers at Moxie are using the tools that I put together to test HTML email quality and rendering to this very day.

Through out the course of my career at Moxie, I would use PHP to put together various portals, a file sharing and project management extranet complete with MySQL powered search and user administration, and...heck...even web services for EMAIL and SMS real-time messaging. Sadly however, I never had the time to carve out for myself a solid and reusable PHP class library for the gaining of efficiencies in product maintenance, development and deployment. While working at Moxie (2006-2012), I really could have used an out-of-the-box/plug-n-play LAMP stack class library with the capability of facilitating an application's compliance with the RTM processes of a mature development shop.

In 2012 (after my exodus from Moxie with...according to what I have been told..."a bang") on a 09' model unibody Macbook Pro that I purchased with my own personal money while at Moxie...for my web application development at Moxie, I began work on just such a solution...coining the project name CRNRSTN, because I was going to use this "stone" to properly join the "wall of server environment" and the "wall of application codebase" together into one house. In hindsight (when I look at archived code from the period of the CRNRSTN genesis)...the approach of my execution in the code was a little off...leaning hard on achieving light and fast performance and completely abandoning flexibility and usability. My mind needed to be uplifted; I needed to experience a paradigm shift. Well...between October of 2012 and Jan 16, 2013, I took a break from programming to go deep in my study of the Bible together with books of ministry to strengthen the foundation of my faith, deepen my daily walk with the Lord Jesus Christ, and validate my moment by moment Christian experience against the teaching and fellowship of the apostles.

While following the leading of the Spirit in my study of the Word of God...during this sabbatical of sorts..., I also began to reconsider the CRNRSTN project and what I wanted this tool to be able to do. By that point, I had thoroughly re-read (cover to cover a couple of times) my second edition copy of High Performance MySQL that was purchased for me by Moxie on the professional development budget.

<flashback> While at Moxie and when I was approaching a massive redesign (LAMP) for a client extranet that was growing in number of users and activity, I requested to be enrolled in a MySQL course from Oracle. That request was denied with audible laughs. Not giving up on my quest for the knowledge...I then found and purchased the best 2 books I could on the topics of interest (High Performance MySQL and Ajax Design Patterns) and then requested for Moxie to recoup my investment. This request was approved...but I got a stern talking to about making future purchases without getting all of the approvals first. No problem. I've read the MySQL book maybe 5 times by now, and it has changed the way that I architect data drive applications. I also have a loose development roadmap which will be directing my ongoing R&D for the CRNRSTN Suite ::. Any useful results from this research will be incorporated into the CRNRSTN Suite in a future release. </flashback>

So beginning in Jan of 2013...while I continued my study of the Holy Scriptures...I picked up the CRNRSTN project and (starting from scratch with a much more insightful approach) began to architect and build out this tool. Between July of 2013 and March of 2016 all application development was moved to my pre-Moxie development machine...a circa 2005 Toshiba Portege M100 running Windows XP® pro and Apache as a service (via Xampp). The AC power adapter for my 09' unibody Macbook Pro had broken, and I did not feel to move in a direction to resolve that problem...so good bye for now dear 09' Macbook Pro. The bulk of this second (fresh from the ground up) iteration of CRNRSTN development was done from within the Windows environment.

Fast-forward to March of 2016,...the broken power adapter for my 09' Macbook Pro was replaced by a good friend of mine, and I immediately copied the CRNRSTN project (which was approximately 90% complete) from my 2005 Widows XP Toshiba Portege M100 laptop back to my 09' Macbook Pro. I then began to painstakingly crawl through both the CRNRSTN Suite :: class library and it's accompanying documentation web site...testing all the work I had done within the Windows environment on my Toshiba in my 09' Mac localhost hosting environment. Once I got CRNRSTN in shape on my Macbook Pro, a couple of other projects (including a redesign of my personal website jony5.com) fell on my plate, and so I had opportunity to test the implementation of CRNRSTN on these new projects and new hosting environments and make changes wherever it made sense.

December of 2017 came around along with a renewed desire to pick up, complete and release the CRNRSTN project, but my 09' Macbook Pro began to freeze up on me and was not up for the task at hand. I shared my frustrations with my dad, and he offered to get me a new laptop. On Dec. 28 2017, a new 2017 Macbook Pro was purchased for me from the Apple store at Perimeter Mall in Atlanta, GA; I copied all my project files along with my XP and Ubuntu virtual machines from my 09' Macbook Pro to the new 2017 Macbook Pro. I then upgraded my Ubuntu Server VM to the latest which brought with it PHP7 (previously, I had only supported PHP5) and the extra work of having to crawl through CRNRSTN and the documentation website making updates to account for the new version of PHP. Both PHP5 and PHP7 are now supported by the CRNRSTN Suite ::!

Between Dec of 2017 and April of 2018, I completed a third iterative pass through the CRNRSTN class library and the accompanying documentation web site. On top of making updates for PHP7 compatibility, the code for the CRNRSTN Suite :: was tightened up a little more, the session and cookie encryption layers were updated to stand on the openssl encryption cipher library (as opposed to the deprecated[PHP5] and removed[PHP7] mcrypt library), and the documentation with the accompanying code examples were thoroughly fleshed out and checked against the CRNRSTN Suite :: codebase for clarity and accuracy.

It is now June 20, 2018, and a hard launch date of July 4, 2018 has been set. The CRNRSTN Suite :: version 1.0.0 documentation has been pushed to production, and the GitHub repository for this project has been updated with the latest release. We have now entered into the realm of soft launch for the CRNRSTN Suite :: version 1.0.0. Over the next couple of weeks leading up to the official release date, there will be plenty of "tire kicking", fine tuning, and copy tweaks. After a solid 6 years spent in thoughtful contemplation and faithful laboring, we are finally ready to go! Thank You, Lord Jesus!