C-Liu: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
 
(611 intermediate revisions by the same user not shown)
Line 1: Line 1:
<html><div  style="background-color: #372F22; color: #FAF9F6; "></html><br/>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp;    &nbsp; &nbsp;  <sup>&#8480;</sup><br>
<span style="position: relative; top: -15px;font-size: 34px;>  &nbsp; C六 </span>
<html><script> if (screen.width >= 1024) document.write(
"<img style='position: relative; top: -30px;left: -50px;' align=right width=175 src=https://meansofproduction.biz/img/front_1.jpg>");</script>
<blockquote>
<div style="text-align: justify;width: 80%;">
<br>
<center style="position:relative;top:-15px;"><span style="font-size:20px;"></html>
<b><i>A PHP 
<span class=plainlinks> [https://devops1.sameboat.network/geo_node <span style="color: lime;"> network</span>]</span>  <span class=plainlinks">[[:en:Content management system| <span style="color: lime;">DCMS</span>]]</span> fa&ccedil;ade </span></i></b><br>
<span style="font-size:10px;">C六 was derived from Drupal 7 for use in MCP contexts.</span><br>
<span style="background-color:black;font-size:8px;position:relative;top:-8px;">Outside sameboat, the curated modules are mostly unaltered and others will generally work if they did in final D7.</span>
</center>
<br>
<table style="background-color: #372F22; color: #FAF9F6; " width=100%><tr><td valign=absmiddle width=30%>
<center style="position:relative;top:-5px;">C-Liu (C6*):  part of DCMS, reuses final  [[PHPCMS|<span style="color: lime;">D7</span>]]<html></center> "DCMS"  is domain content management in the large
outside of  </html>[[MCP|<span style="color: lime;">DCP</span>]] not just C六.  C六 runs in a php 7 [[MCPCELL|MCP cell]], I support only for that context but it is mostly unaltered
D7 modules. <br><span style="position:relative;top:8px;">To be clear, generally in DCMS, i.e. in mediawiki, WordPress, php is at the supported level, e.g. 8 or whatever the php code requires. DCMS aims to realize  CMS generalization via <html><a style="color: lime;" href=https://github.com/haskell-beam/beam>beam</a> and <a style="color: lime;" href=https://github.com/pa-ba/compdata>compdata</a></html> based unification of the relational schema of the constiuent  backend CMSes.<ref><span style="font-size:10px;"> As an antipode to my metadatabase concept c. 1986 (EER on JDCM.pdf).</span></ref></span></td>
<td width=3%></td><td> <center style="position:relative;top:-19px;"><html><a style="color: lime;"
title="pronounced 'DCMS bra'" href=/eg/index.php/Redvant>&lt;DCMS</a> and <a style="color: lime;" title="pronounced 'DCMS ket'"
href=https://sameboat.network/DCMS/>DCMS&gt;</a> name front and back end elements relative to this PHP codeset, respectively &sup3;.</center>
<span style="position:relative;top:-10px;">C六 became a fork of D7 as of 7.99 </html><ref><font size=1>selective changes thru 101 have been applied.</font></ref> which contained changes I didn want in core, then d.o after many false starts did in fact decommit in Jan 2025.<ref><font size=1> Since the actual decommit at d.o, all modules in our charge have their sources pointing to our server. However existing d7 modules on d.o can still be installed with an URL in C六. The C六 update mechanism will not convert them and they will show as unsupported as all modules do in a regular d7 site since the decommit.</font></ref> The direction for DCMS is as indicated to the left, the d7 codeset is used as is as a bolus of function to be replaced at a later date and it is best taken as a black box by normal users and most developers.<br>
<span style="position:relative;top:8px;">As far as the C六 D7 line is concerned, [[:en:security by design|<span style="color: lime;">security</span>]] and stack issues are DS system level concerns. The Cliu clean/dirty repos (common/devops, resp.), created with  core and contrib modules diverged as indicated above and the project/update modules are modified to use sameboat commons.  D7 module authors can get forgejo access with social networked, i.e. free entitlement<span><br><br>C六 is a nexus for php in DCMS generally, involving current mediawiki, wordpress, other pkgs/oddments.<br>
</span>
<html></td></tr>
</table>
<img style="float:right;position:relative;left:300px;top:25px;" width=500px src=https://meansofproduction.biz/images/QINBEI.jpg>
<br>
<br>&nbsp;<br><p style="text-align:center;">
<br>
<span style="position:relative;top:-70px;">The <a style="color: lime;" href=https://devops1.sameboat.network/sb-app>common app platform</a> supports C六 and my product lines on Android and iOS.</span>
</p>
<span style="position:relative;top:-50px;left:70px;"><i>Roadmap:</i> C六 relegated to SB network, Redvant headed django-cms becomes the default concrete CMS.</span>
</blockquote>
<blockquote style="width: 80%;">
<span style="font-size:16px;position:relative;left:35px;">A Timeline</span><br>
<span style="font-size:8px;">domains common era after ceremonial</span><br>
<blockquote>
<p>075-12 &mdash; the d9/10 instance db was lost in a migration, a static page could/may replace its content.</p>
<p>075-07 &mdash; Modules rebuilt as projects and redirected to sameboat commons.</p>
<p>075-04 &mdash; django-cms adopted as sister CMS.</p>
<p>075-01 &mdash; D7 disappears from new d.o guided flow  but still available with others going back to D5.</p>
<p>074-12 &mdash; Merge selected final (7.103) changes.</p>
<p>073-12 &mdash; Drupal 7.99 drops, diverge from <a style="color: lime;" href=https://drupal.org>d.o</a>.</p>
<p>c. 4721 &mdash; IANA .live replaced by .network.  </p>
<p>c. 4719 &mdash;  <a style="color: lime;" href=https://devops1.sameboat.network/PGS>PG Concept</a>. Fork live and commons prod, rebuilding the latter&sup2;.</p>
<p>c. 4716 &mdash; Pursuant to SA-CORE-2018-004, C六 drupal was rebuilt from scratch. </p>
<p>c. 4714 &mdash; First selection of sameboat name based on concept of affinity group support.</p>
<p>c. 4705 &mdash; First selection of Drupal as php CMS of choice and the C六  name after C5.</p>
</blockquote><br>
<br><br><div style="position:relative;left:250px;top:-20px;float:right;" >
<audio style="height:14px;" title=" 'Essence' - Donald Byrd 1970. " controls source src="https://meansofproduction.biz/pub/Essence.mp3" type="audio/mpeg"> This page has an audio but your browser does not support the audio element.</audio>
<div style="font-size:8px;color:cyan;"><center>This page has a music track, mouseover for title.</center></div></div><br><br>
</div></blockquote></div></html>
<table width=100%><tr>
<table width=100%><tr>
<td width="20%">[[:en:Concrete 5|<html><span style="background-color: maroon; color: white;">C5 (whence "C-6")</span></html>]]</td>
<td width="33%">[[:en:Concrete 5|<html><span style="background-color: maroon; color: white;">*C5 (whence "C-6")</span></html>]]</td>
<td width="20%">[[Documentation|<b>C六书</b>]]</td>
<td width="34%" align=center>[[Documentation|<b>C六书</b>]]</td>
<td width="20%">[https://drupal.org/u/kyberuserid <html><large><b>d.o</b></large></html>]</td>
<td width="335%" align=right>[https://drupal.org/u/kyberuserid <span style="color: pink;"><b>d.o</b></span>]</td>
<td width="20%">[[drupalapps|<html><span style="background-color: black;">druportfolio</span></html>]]</td>
</tr></table><html><img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=Cliu>
<td width="20%">[[C5|<b>To PHP CMS Page</b>]]</td>
</tr></table>  
<html><div  style="background-color: antiquewhite; color: navy; "></html><br/>
&nbsp;
<font size=6>C六</font>


<html><img style="position: relative; top: -50px;" align=right width=175 src=/img/front_1.jpg>
 
<blockquote>
<font size=1> &nbsp; &sup3;C-六 exceeds drupal tolerances ( <a href=https://www.drupal.org/docs/7/site-building-best-practices/avoid-too-many-modules>best practice</a>),
<div style="width: 80%;"><br><center><b><i>C六 is just my curated set of d7 and d8 modules using a single pg db packaged with the app module
  engineering/curation to make it so and make it work is part of the ops concept. Live now has 101 and commons has 77 packages. &nbsp;
and some <a href=https://drupal.org>d.o</a> drupal distribution helpers. <br>The sameboat products and services are targets of my DDD focused on specific end function/feature sets.</i></b></center><br><p>
<a href=https://drupal.sameboat.network><span style="color: lime;">D10/11</span></a> branch for devops use, other php packages generally track latest release for the operational stack.</font></html>
The drupalfolio link has some other/earlier/jobbing use. I pretty much started with d6 so never used earlier,see discussion page, history for evolution.
<references/>
While I don't anticipate decommitting drupal,<br> I've moved on to the (haskell based) generalization in DCMS, django/python for systems web stuff, and take WordPress as a simpler peer to drupal, and with mediawiki, forming the our cover of the space of PHP CMS. </p>
<p> Originally intended as a locus for various stuff and for a line of biz supporting d7/d8 migration/integration as well as CMS generalization. A golden procrastination situation was found to have arrived by about Spring '18 by which time d8 was finally starting to look solid, although d7 necessarily remains the production choice. So at this point the mark is strictly used for my curation of d7/d8 modules, principally in the sameboat venture and the distribution which I will only be offering here and thru Shopify, not on d.o.</p>
<p>Pursuant to the security issue with drupal 7.59/8.5.3, the <a href=https://sameboat.live>sameboat app</a> (essentially C六 applied to different lines of biz) was rebuilt from scratch and from that point maintains a clean line of descent from that rebuild, with only forward deployments from the clean environment, to avoid such issues in the future. Issues such as SA-CORE-2018-004 are wiped by deployments to the wild, as they arise.
</p>
The sameboat domain (composed of </html>[https://sameboat.live sameboat.live] which is d7 and [https://cliu.sameboat.live cliu.sameboat.live]<html> which is d8) has operational versions of every such service/feature set in its reference public form, usable by authenticated users.<br>&nbsp;<br><br>&nbsp;<br>
</div></blockquote></div>
</html>

Latest revision as of 06:46, 16 December 2025


                       
  C六

A PHP network DCMS façade
C六 was derived from Drupal 7 for use in MCP contexts.
Outside sameboat, the curated modules are mostly unaltered and others will generally work if they did in final D7.


C-Liu (C6*): part of DCMS, reuses final D7
"DCMS" is domain content management in the large outside of DCP not just C六. C六 runs in a php 7 MCP cell, I support only for that context but it is mostly unaltered D7 modules.
To be clear, generally in DCMS, i.e. in mediawiki, WordPress, php is at the supported level, e.g. 8 or whatever the php code requires. DCMS aims to realize CMS generalization via beam and compdata based unification of the relational schema of the constiuent backend CMSes.[1]
<DCMS and DCMS> name front and back end elements relative to this PHP codeset, respectively ³.
C六 became a fork of D7 as of 7.99 [2] which contained changes I didn want in core, then d.o after many false starts did in fact decommit in Jan 2025.[3] The direction for DCMS is as indicated to the left, the d7 codeset is used as is as a bolus of function to be replaced at a later date and it is best taken as a black box by normal users and most developers.

As far as the C六 D7 line is concerned, security and stack issues are DS system level concerns. The Cliu clean/dirty repos (common/devops, resp.), created with core and contrib modules diverged as indicated above and the project/update modules are modified to use sameboat commons. D7 module authors can get forgejo access with social networked, i.e. free entitlement

C六 is a nexus for php in DCMS generally, involving current mediawiki, wordpress, other pkgs/oddments.



 


The common app platform supports C六 and my product lines on Android and iOS.

Roadmap: C六 relegated to SB network, Redvant headed django-cms becomes the default concrete CMS.

A Timeline
domains common era after ceremonial

075-12 — the d9/10 instance db was lost in a migration, a static page could/may replace its content.

075-07 — Modules rebuilt as projects and redirected to sameboat commons.

075-04 — django-cms adopted as sister CMS.

075-01 — D7 disappears from new d.o guided flow but still available with others going back to D5.

074-12 — Merge selected final (7.103) changes.

073-12 — Drupal 7.99 drops, diverge from d.o.

c. 4721 — IANA .live replaced by .network.

c. 4719 — PG Concept. Fork live and commons prod, rebuilding the latter².

c. 4716 — Pursuant to SA-CORE-2018-004, C六 drupal was rebuilt from scratch.

c. 4714 — First selection of sameboat name based on concept of affinity group support.

c. 4705 — First selection of Drupal as php CMS of choice and the C六 name after C5.




This page has a music track, mouseover for title.



*C5 (whence "C-6") C六书 d.o

  ³C-六 exceeds drupal tolerances ( best practice), engineering/curation to make it so and make it work is part of the ops concept. Live now has 101 and commons has 77 packages.   D10/11 branch for devops use, other php packages generally track latest release for the operational stack.

  1. As an antipode to my metadatabase concept c. 1986 (EER on JDCM.pdf).
  2. selective changes thru 101 have been applied.
  3. Since the actual decommit at d.o, all modules in our charge have their sources pointing to our server. However existing d7 modules on d.o can still be installed with an URL in C六. The C六 update mechanism will not convert them and they will show as unsupported as all modules do in a regular d7 site since the decommit.