CRNRSTN :: 2.00.0000 PRE-ALPHA-DEV (Lightsaber)

Welcome to CRNRSTN ::.

This is the intro demo page for a vanilla implementation.

Recent Activity ::

For now, current activity related to the direction of the project will be posted here:

Monday, November 21, 2022 @ 1003 hrs

The project has received about twenty (20) new system constants (integer), and these will be used to seamlessly drive planned third party JS and CSS framework integrations. The current project lead is in the middle of making a rough pass through all of these new resources to set them squarely on top of the asset mapping architecture of CRNRSTN ::. This is definitely a rough pass, friends.

A second pass will need to be made in order to clear all of the 404 return responses from broken library dependencies (mostly images...png, gif, jpg). As is the case with any vanilla application, a URL from CRNRSTN :: which points directly to any JS framework's source on the server will enable that framework to access all of it's own supporting assets as intended,...itself. So, for example, a JS application (running in the browser) would know where to find all of it's "internal" images. This would be the fruit borne from operating according to a more traditional approach...or (in this case) the fruit of setting $tunneling_active = false when calling $oCRNRSTN->config_init_asset_mapping_js().

On a side note...by default, $tunneling_active is set to TRUE,...which is the lead dev's recommendation and which will eventually allow CRNRSTN :: to do some pretty cool shit like bind resources to sessions and quietly return ANY resource from ANY authorized server (think...spontaneous file server).

In our case, however, 404 error are being returned after the use of a URL to a JS framework that takes CRNRSTN :: itself as the intended endpoint and...consequently and among other things...exposes no specific information about the location of the resource being requested. In fact, a filename (or filename plus one (1) directory) is the most that ever need be revealed. Therefore, in all of these situations, I...I mean...the current lead developer will need to have CRNRSTN :: step up and do the work of providing these resources directly to said JS framework...on top of having already made CRNRSTN :: to do the work of providing the very JS framework that is now seeking said resources.

With great power comes great responsibility, my friends.

[2022-11-21 10:03:29.330436]

Demonstration ::

Pulling custom data out of the system resource configuration ^†file:

WETHRBUG_APP = https://wethrbug.jony5.com/

†

See '/_crnrstn/_config/config.system_resource.secure/_crnrstn.system_resource.inc.php'.

Check out the CRNRSTN :: v1.0.0 Facebook photo album!

   _|_|_|  _|_|_|    _|      _|  _|_|_|      _|_|_|  _|_|_|_|_|  _|      _|              
 _|        _|    _|  _|_|    _|  _|    _|  _|            _|      _|_|    _|      _|  _|  
 _|        _|_|_|    _|  _|  _|  _|_|_|      _|_|        _|      _|  _|  _|              
 _|        _|    _|  _|    _|_|  _|    _|        _|      _|      _|    _|_|              
   _|_|_|  _|    _|  _|      _|  _|    _|  _|_|_|        _|      _|      _|      _|  _|