Assemble (Html + Json) Data Components
2. Platform/Framework Independent Abstraction defined in Html/Json Files and Folder/File Names and Organization
Currently the tool consists of Assembler which implements the abstraction and also a tool/runtime for facilitating hot reloading, deployment to multiple fly.io regions/machiens, git integration, performance testing from multiple regions, client side load balancing*, proxy for multiple apps deployed in same fly.io machines etc
The Html/Json assembler will be extracted from the tool and the source will be published using MIT License.
The tool and the application using the MIT Licensed assembler/abstraction will be proprietory.
Some intersting links to showcase the abstraction. View the hidden Inspect Toolbar at the top to know other features
Main Page explaining the abstraction
Main : https://appweb.fly.dev
Just add Meta to the end of the page to view the Metadata Json
Meta : https://appweb.fly.dev/meta
Test Page to show case the different abstractions for assembling Html + Json
Can be deployed in fly.io machines across all regions but charged based on actual usage since the runtime will auto shutdown after a idle time of 30 seconds
Can check the performance of the webpage by clicking the hidden button at the bottom left corner of any page
"Click Bottom Left Corner to View Page Performance tooltip".
Can check the metadata of the assembeled components by opening the Inspect Toolbar by clicking the invisible top bar and clicking the view button
"Click Top Hiddent Toolbar to View Inspect Toolbar".
"Inspect Toolbar".
Can view the Source Hierarchy of the Page (WIP)
"View Component Source Hierarchy".
Can edit the Data Source Hierarchy of the Page after login
"Edit Component Data Source Hierarchy".
Clone the repo and run the appropriate appweb.web asp.net core application for the respective platform
On first run the application will run the asp.net core kestrel server
If the source of the Html + Json is required, set the appconfig.json parameter UnPackAppSites to true for the server to extract the AppSites Html + Json to be root folder. Modifying any of the Html + Json should update the Browser UI by hot reload (WIP)
Run the Docker Image arshucs/appweb as below
Fly.io provides free options which should be more than sufficient to host any web app for testing since the machine will auto shutdown after a idle time configured using Environment Flag
Prerequisite is Install the Fly Command Line Program from fly site and login using the fly command line program using fly auth login
Initial Step 1 : Create a Fly App for Machines flyctl apps create --machines --name [appname] --org personal Optional to Delete the [appname] rem flyctl apps destroy [appname] --yes Initial Step 2 : Allocation IPv4 and IPv6 for the App flyctl ips allocate-v6 --app [appname] flyctl ips allocate-v4 --app [appname] flyctl ips list --app [appname] Initial Step 3 : Create a Fly Machine [NOT A FLY APP] flyctl apps create --machines --name [appname] --org personal Initila Step 4 : Upload the Docker Image to Fly Docker Registry Change directory to the linux64_musl Directory flyctl deploy . --build-only --remote-only --push --image-label latest -a [appname] Initial Step 5 : Deploy the Machine to Fly flyctl machine run registry.fly.io/webimages:appweb --name appweb-sin-1 --port 443:8080/tcp:tls --port 80:8080/tcp:http --env INITIAL_TIME_IN_SEC="30" --env IDLE_TIME_IN_SEC="30" --config fly.toml --app [appname] Update Step 6 After Deploy after every change in the deploy folder deploy the docker image to Fly Docker Registry flyctl deploy . --build-only --remote-only --push --image-label latest -a [appname] Retrive the Machine ID flyctl machine list --app [appname] Update the Machine flyctl machine update [machineID] --image registry.fly.io/[appname]:latest --port 443:8080/tcp:tls --port 80:8080/tcp:http --env INITIAL_TIME_IN_SEC="150" --env IDLE_TIME_IN_SEC="150" --config fly.toml --app [appname] --skip-health-checks --yes
To Reset the Login Details delete the contents of the App_Data Directory and disable the loading of the AppWeb.Web.dll assets as below in appconfig.json file before starting the server.
{
"AssetTypeName": "AppWeb.Web.AssetRegister",
"AssetDll": "AppWeb.Web.dll",
"IsEnabled": false
}
Run the Server and it will prompt for the Initial Users ID which can be used to login and explore the other features of the application.
- Direct composition :
Url - / or /Index/Main - [AppSite]/[AppView]
UI Namespace is AppSite - Mapped to Directory Structure under AppSites Root Directory
UI Context is Main AppView - Mapped to File Name Prefix of Component
Index.html
<div>
{{MainHeader}}
</div>
<div>
{{MainContent}}
</div>
<div>
{{MainFooter}}
</div>
The Runtime will search the wwwroot folder arranged in correct folder structure and auto replace the mustache definition with the actual html component recursively. Reorganizing the Html Components in the appropirate folders has no impact to composition.
- Context Sensitive composition:
Abstraction for Composing where the Parent Component is composed with Child Components based on Context
When Context is https://appweb.com/Index/Main vs https://appweb.com/Index/About
MetaData of the Pages are
https://appweb.com/Index/Main/Meta
https://appweb.com/Index/About/Meta
The Main Prefix of a Mustache is replaced with the AppView Context (About) to render a different page retaining the same index.html page.
Url : /Index/About - [AppSite]/[AppView]
UI Namespace is AppSite - Mapped to Directory Structure under AppSites Root Directory
UI Context is About AppView - Mapped to File Name Prefix of Component
Index.html
<div>
{{MainHeader}} => {{MainHeader}}
</div>
<div>
{{MainContent}} => {{AboutContent}} -- If Available else {{MainContent}}
</div>
<div>
{{MainFooter}} => {{MainFooter}}
</div>
- Inner Composition:
Abstraction for Composing Inner Components of a Parent Component defined in the page where the Component is used
Center.html
<div>
{{$HTMLPLACEHOLDER}}
</div>
Index.html
<div>
{{#Center}} => {{Center}}
{{@HTMLPLACEHOLDER}}
{{MainContent}} => {{MainContent}} under the Center Html PlaceHolder
{{/HTMLPLACEHOLDER}}
{{/Center}}
</div>
- Placeholder Data Composition
Title.html
<div>
{{$Title}}
</div>
Title.json
{
"Title" : "Name"
}
- Section Array Composition
List.html
<div>
{{@List}}
{{$TaskName}}
{{/List}}
</div>
List.json
{
"List" : [
{
"TaskName" : "Task 1"
}
]
}
- Data Flow Composition
Component State
Parent Components State
Context State
Global State
Data Defined at the Any Data Level can be Overwriten by the Previous Precedence Data if allowed by $ Suffix to the Json Key
Title.json
{
"Title$" : "Name" ==> Allow Override with Parent Data if Available
}
- Abstractions for Assembling Dynamic Components is by adding a {{ViewPlaceHolder}} where the system will auto generate a View ID for accessing from Javascript
Center.html
<div>
{{ViewPlaceHolder}}
</div>
- Currently state flow between components is completed. State flow between global state, context state, parent state and component state where the component state overwrite all the previous state is implemented. Viewing the Metadata of the Page gives the State Flow.
Component State
Parent Components State
Context State
Global State
Components should be grouped into AppSites and AppViews Folders for providing URL Context
AppSites are like namespaces which is used to separate components into libraries
AppSite's are created under AppSites Root Directory under the Application Root Folder
AppView's can be grouped into Views/ViewsDefer Root Directory under Respective AppSite Directory.
General Components can be added to Component/Common Directory under Respective AppSite Directory
Page Components can be added to AppView Directory under Views/ViewsDefer Directory
Url to access a page is https://[Hosting Domain]/[AppSite]/[AppView]