User:Prd: Difference between revisions
More actions
No edit summary |
No edit summary |
||
| (35 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=====10/11===== | |||
Mediawiki 1.43.1 -> 1.43.5, then back to business. | |||
=====10/21===== | |||
Quick update, this one's gonna be extra spicy. Experimenting with Blazor, as per the C#-based local tooling for extraction, creating a connective meshing between the extractions, outputs, formatting of, server request-response and manifest management end to end. This lays the groundwork for a privatized pipeline to push new and update with respect to older manifests...eventually allowing for a pathway to achieve the same outcomes in a public manner. Once manifests can be handled to satisfaction the feature oriented development of the map will continue in earnest. Soon after will follow an API/UI refinement and mass pruning of the initially imported templates & modules as well as a general reduction in extension usage. Slash and burn remains in effect. | |||
[https://www.youtube.com/watch?v= | =====10/22===== | ||
Manifest management pipeline underway! New site is up - concurrently building up the admin panel and app connector. In order but not particularly, construct server layer API (incoming, outgoing, on-site, server instructions), build private connection (first, then "public"), build extraction bundler, create file & zip delivery & unpacking routines... and then basically improve controls in preparation for updating the wiki's observational manager. DotNET is, in my humble opinion, a sleeping giant of a framework in the realm of web development. I'm no Java expert - and I never will be - but what the C# team have cobbled together over the years, now made more apparent by picking up Blazor (server), is downright impressive given how easy VSC is to integrate via SSH. 9 out of 10, would dev again, their docs are like swimming through a swamp - it's great. | |||
=====10/23===== | |||
[https://www.youtube.com/watch?v=fO7ih6Nu3MA No one would believe me and it wouldn't matter to whom it was said. There's gold in them there hills, I tell ya. I've seen it with my own eyes, I swear upon it - won't you lend your ears? What was once impossible is no longer so. Time makes a mockery of our grandest plans. I followed the river, as the trees advised, happening upon the grove of secrets. I'm not asking you to believe. Just wait and wonder.] | |||
=====10/25===== | |||
: | [https://www.youtube.com/watch?v=azSsMG6h8k0 Sometimes the best thing to do is nothing] | ||
: | =====10/26===== | ||
: | A brief explainer of what's being assembled... | ||
--- | :A "Manifestor" admin panel (site), such that I can intercept and manage requests - specifically speaking about token authorization for incoming manifest uploads and spot actions for adjusting data on the backend. | ||
:The Blazor API handles the site's actions, while the server itself hooks to OAuth for generating approved user tokens - this by enabling login capabilities via the app, granting wiki-sided permissions and then passing the requests on to the upload queue. | |||
:Reworking login (my own) to adhere to .NET environment practices, in preparation for setting up the public-private paradigm of the pipeline. | |||
:Due to the (seeming) ease of DB connectivity and calling thereof... some time is being spent overhauling the job runner dashboard to revisit, improve upon and expand monitoring capabilities. This in part due to the upcoming mass pruning of the wiki... which will follow the creation of the pipeline and return to feature creation (notably, unification of the manifest management) for the map. | |||
:Blazor (server) won't be rolled into the map - but Typescript will. PHP's usage will be restricted down to wiki-centric operations. There will be no further exploration of web frameworks, nor is there any need for toiling with C, Python, Go (and even C++). Instead, most needs can be met by C# - which is supplemented by the suite of standard web-server languages (HTML, CSS, JS, Typescipt, PHP, MySQL/MariaDB, Bash/Shell, systemd daemons, Nginx/Varnish, etc). | |||
---- | ---- | ||
Update, decisions being made. | |||
:Upgrade to 1.43.5 complete. Monitoring. | |||
:SMW removed - an update from 5.1.0 to 6.0.0 would likely fix the depricated call - instead I'm opting for removal until warranted addition and experimentation with at a later point. '''Site feels faster?''' Keeping Cargo, PageForms, etc - because they have reasonable potential. | |||
:Adding OAuth to adhere to obligatory practices for establishing the secure data flow - need legitimate bearer tokens for proper authorization routine. As per analysis of AWB - works for me, works for you, whatever it takes to get us there. | |||
:More extensions will go over time. The wiki may be unstable, because I'm back to breaking things, and I can summon it from the grave whenever I please. Cloud-external backups have been running for quite some time, with both DB & total server iterations available. | |||
:Followup - fuck yeah it's faster. VROOM! | |||
:OAuth functional, consumer registered, DataTools being connected for external login purposes. Yey! | |||
:Citizen updated to latest, 3.9.0. | |||
:Updates on the DataTools delivery system, Manifestor pipeline and refinements to the wiki's special page UIs to follow. | |||
---- | ---- | ||
=====10/27===== | |||
[https://www.youtube.com/watch?v=GwPhmsazh4c It's not 2018 anymore. Better shape up!] | |||
---- | ---- | ||
====10/29==== | |||
[https://www.youtube.com/watch?v=Q-9DcFVLDYs If only you knew.] | |||
---- | ---- | ||
= | ===10/30=== | ||
[https://www.youtube.com/watch?v=MSb_31SUEXE Let me show you.] | |||
---- | ---- | ||
[https://www.youtube.com/watch?v=dKmuCBFPY3g Give people a chance] | |||
[ | |||
Latest revision as of 19:31, 30 October 2025
10/11
Mediawiki 1.43.1 -> 1.43.5, then back to business.
10/21
Quick update, this one's gonna be extra spicy. Experimenting with Blazor, as per the C#-based local tooling for extraction, creating a connective meshing between the extractions, outputs, formatting of, server request-response and manifest management end to end. This lays the groundwork for a privatized pipeline to push new and update with respect to older manifests...eventually allowing for a pathway to achieve the same outcomes in a public manner. Once manifests can be handled to satisfaction the feature oriented development of the map will continue in earnest. Soon after will follow an API/UI refinement and mass pruning of the initially imported templates & modules as well as a general reduction in extension usage. Slash and burn remains in effect.
10/22
Manifest management pipeline underway! New site is up - concurrently building up the admin panel and app connector. In order but not particularly, construct server layer API (incoming, outgoing, on-site, server instructions), build private connection (first, then "public"), build extraction bundler, create file & zip delivery & unpacking routines... and then basically improve controls in preparation for updating the wiki's observational manager. DotNET is, in my humble opinion, a sleeping giant of a framework in the realm of web development. I'm no Java expert - and I never will be - but what the C# team have cobbled together over the years, now made more apparent by picking up Blazor (server), is downright impressive given how easy VSC is to integrate via SSH. 9 out of 10, would dev again, their docs are like swimming through a swamp - it's great.
10/23
10/25
Sometimes the best thing to do is nothing
10/26
A brief explainer of what's being assembled...
- A "Manifestor" admin panel (site), such that I can intercept and manage requests - specifically speaking about token authorization for incoming manifest uploads and spot actions for adjusting data on the backend.
- The Blazor API handles the site's actions, while the server itself hooks to OAuth for generating approved user tokens - this by enabling login capabilities via the app, granting wiki-sided permissions and then passing the requests on to the upload queue.
- Reworking login (my own) to adhere to .NET environment practices, in preparation for setting up the public-private paradigm of the pipeline.
- Due to the (seeming) ease of DB connectivity and calling thereof... some time is being spent overhauling the job runner dashboard to revisit, improve upon and expand monitoring capabilities. This in part due to the upcoming mass pruning of the wiki... which will follow the creation of the pipeline and return to feature creation (notably, unification of the manifest management) for the map.
- Blazor (server) won't be rolled into the map - but Typescript will. PHP's usage will be restricted down to wiki-centric operations. There will be no further exploration of web frameworks, nor is there any need for toiling with C, Python, Go (and even C++). Instead, most needs can be met by C# - which is supplemented by the suite of standard web-server languages (HTML, CSS, JS, Typescipt, PHP, MySQL/MariaDB, Bash/Shell, systemd daemons, Nginx/Varnish, etc).
Update, decisions being made.
- Upgrade to 1.43.5 complete. Monitoring.
- SMW removed - an update from 5.1.0 to 6.0.0 would likely fix the depricated call - instead I'm opting for removal until warranted addition and experimentation with at a later point. Site feels faster? Keeping Cargo, PageForms, etc - because they have reasonable potential.
- Adding OAuth to adhere to obligatory practices for establishing the secure data flow - need legitimate bearer tokens for proper authorization routine. As per analysis of AWB - works for me, works for you, whatever it takes to get us there.
- More extensions will go over time. The wiki may be unstable, because I'm back to breaking things, and I can summon it from the grave whenever I please. Cloud-external backups have been running for quite some time, with both DB & total server iterations available.
- Followup - fuck yeah it's faster. VROOM!
- OAuth functional, consumer registered, DataTools being connected for external login purposes. Yey!
- Citizen updated to latest, 3.9.0.
- Updates on the DataTools delivery system, Manifestor pipeline and refinements to the wiki's special page UIs to follow.
10/27
It's not 2018 anymore. Better shape up!