I’m going to change my photography portfolio from a custom (albeit poorly coded) JavaScript app to a WordPress photo-blog this weekend to simply make it better while I focus on getting aFrame out of beta, and complete some lab apps for Zend certification.
Once I have that certificate showcasing my awesomeness, I’ll either toss away the WordPress install or wrap it in aFrame.
It’s online, and empty at the moment. I need to organize my projects into it’s directory structure, after I work out my authentication model.
I decided to give myself a proper development lab for all of my projects to sit in, like a sandbox behind a 256/2048 bit SSL certificate. Now I just need to finish the authentication gateway for the dashboard on avoidwork, my photography portfolio and a few other apps that are in development or on the planning table.
Keeping myself busy is turning out to be too easy, thank god Jenz makes me go outside on weekends!
Celcius was offline for most of Friday, and some of Saturday. At first this was due to a software conflict, which then turned into an opportunity to do a hardware swap / upgrade to prepare for an OCZ Revo PCIe based SSD. I also took this time to install a wildcard SSL certificate for avoidwork, which I mentioned in the previous post.
No data was lost, we just experienced a little downtime.
I decided to look into wildcard SSL certificate providers this weekend and was blown away by the price difference between my usual registrar and GoDaddy. After a little more research, I decided to get a ‘Standard’ wildcard for avoidwork which I plan to use across a lot of services and URIs; including a proper secure online lab.
The first things I encrypted was the client area (project manager) and a brand new webmail.
The new database behind a PHP5 interface.
NoRel design using Views on a MyISAM table. Pure speed.
A rule table to apply bit permissions to entities. The entity.owner value comes from another db/service (openid style, decoupled ’cause it should be). When creating a new entity if the owner is not null (ie, not a system entity) a perm of 4 (read/write/delete) is applied, otherwise only 1 (read) is set via trg_ins. A cascade delete is handled by trg_del.
Views are used to create categories, based on an entity.parent value of 0. In theory this is both the navigation and primary content channels.
Groups are possible via the same auth service, so this is basically gen 1 of Spiral. That version will rely on Doctrine ORM and have a more robust dashboard compared to avoidwork.com.
The recent decision to move to a NoSQL database was coming for a long time. There’s obvious benefits to the schema design for certain scenarios, and I’m betting on them.
I was so quick to create the code base to allow me to use the new schema that I forgot I was missing the Authentication service on the secure application gateway I launched a few weeks ago.
Considering it’s close to midnight, I’m going to finish up tomorrow or later this week depending if the sun comes out tomorrow.
avoidwork.com is getting a behind the scenes upgrade by moving to a NoSQL schema powering my PHP5 code. I’ve also refactored the directory structure to be more secure with ‘best practices’ in mind.
A major component for the SaaS project that’s driving aFrame development went live today! The URI based, SSL encrypted Gateway is online and ready for a bunch of resources to be enabled when the other pieces of this scalable application are ready.
It’s going to be killer.
Today I managed to squeeze a few hours in for development and banged out a final version of the AJAX/REST classes for DELETE, GET, POST & PUT. I also re-organized some classes, and created a few new ones including array{} which has alternative methods to native ones such as contains() in lieu of indexOf(), and remove() in lieu of slice()/splice().
More prototyping of aFrame onto JavaScript objects has also been occurring, and it’s starting to turn into a great framework to create applications with.
