C-Liu: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
 
(113 intermediate revisions by the same user not shown)
Line 6: Line 6:
<blockquote>
<blockquote>
<div style="text-align: justify;width: 80%;">
<div style="text-align: justify;width: 80%;">
<br><center><b><i><a title="not maintained" href=https://timeline.sameboat.network>Biz case #65</a>, the </html>[[C5|<span style="color: lime;">php</span>]] and python codesets at the core of
the Domains <span class=plainlinks">[[:en:Content management system| <span style="color: lime;">CMS</span>]]</span>. <br>Defining use cases are the 
<span class=plainlinks> [https://cliu9.sameboat.network/verticals  <span style="color: lime;">sameboat network</span>]</span>  and the <html>
<a href=https://sameboat.meansofproduction.biz/products/aksambos><span style="color: lime;">SaaS/PaaS</span></a> products. </i></b></center>
<br>
<br>
<br>&nbsp;<br>
<center style="position:relative;top:-15px;"><span style="font-size:20px;">
C-Liu (C6*) is the PHP part of DCMS based on the Drupal CMS. "DCMS" is used in the widest sense to refer not just to the php/python core (C六) but to content management in domain space generally
<b><i>A maintained Drupal 7 supporting the Domains <span class=plainlinks"></html>[[:en:Content management system| <span style="color: lime;">CMS</span>]]<html></span> and   
outside of the </html>[[MCP|<span style="color: lime;">DCP</span>]] providing manifold services to [[AKPERSON|<span style="color: lime;">AKPERSONS</span>]]<html>. <a style="color: lime;"
  <span class=plainlinks></html> [https://devops1.sameboat.network/geo_node <span style="color: lime;">sameboat network</span>]<html></span> </i></b></span><br>
title="pronounced 'DCMS bra'" href=https://eg.meansofproduction.biz/eg/index.php/Redvant>&lt;DCMS</a> and <a style="color: lime;" title="pronounced 'DCMS ket'"
<span style="font-size:12px;">C六 is basically just D7 with DS specifics in the sameboat module project, a MCP cell can be provisioned for just this.</span>  
href=https://sameboat.network/DCMS/>DCMS&gt;</a> name front and back end elements relative to this PHP codeset, respectively &sup3;.<br><br><p style="text-align:center;">
</center>
.network is the current public/IANA suffix. <a href=https://sameboat.network><span style="color: lime;">Sameboat commons</span></a> is the stable</html> <ref><font size=1>Version of function in live may be different from what makes it to
<br>
commons.</font></ref> branch from my live <html> <a href=https://devops1.sameboat.network>shared devops</a> both upstream of the geonode deployments
<table style="background-color: #372F22; color: #FAF9F6; " width=100%><tr><td valign=absmiddle width=30%>
(<a href=http://bufyyz.sameboat.network>bufyyz</a>, <a href=https://ord.sameboat.network>ord</a>, <a href=https://seayvr.sameboat.network>seayvr</a>) .<br>The
<center style="position:relative;top:-5px;">C-Liu (C6*): part of DCMS, reuses final </html>[[PHPCMS|<span style="color: lime;">D7</span>]]<html></center> "DCMS"  is domain content management in the large
<a style="color: lime;" href=https://devops1.sameboat.network/sb-app>common app platform</a> supports C六 and my product lines as a base.
outsided of  </html>[[MCP|<span style="color: lime;">DCP</span>]] not just C六.  C六 runs in a php 7 [[MCPCELL|MCP cell]], with support only for that context but it is mostly unaltered
</p><br>
D7 core/contrib modules, avail from forgejo here. <br><br>To be clear, php generally in DCMS. e.g. in mediawiki and other php CMS, is at the supported level, currently 8. Ultimately DCMS will be
C六 became a fork of D7 as of 7.99 </html><ref><font size=1>99 and subsequent d.o releases will be applied selectively so the drupal version number will track d.o until D7 EOL.</font></ref> which contains changes I don't want in core, so it's Dec 2023 not Jan 2025 for C六. As far as the C六 line is concerned, security issues are covered by domain space security. The cliu/clean (dirty) repos (common/devops, resp.), created with most core and sites/all modules unaltered, formally diverge as of 7.98 and all drupal projects source from clean.  D7 module authors get free access even if their
implemented as a fulfillment of my metadatabase concept c. 1986 and presumably in Haskell.</td>
module is not under my current curation.<ref><font size=1>S class plus a provided waiver will entitle, message me as Lycurgus in libera or email.</font></ref>
<td width=3%></td><td> <center style="position:relative;top:-19px;"><html><a style="color: lime;"
<html><br><br>
title="pronounced 'DCMS bra'" href=/eg/index.php/Redvant>&lt;DCMS</a> and <a style="color: lime;" title="pronounced 'DCMS ket'"
<a href=https://drupal.org/project/drd>DRD</a> server runs in its last production drupal (currently 10), not modified by me except for the addition of
href=https://sameboat.network/DCMS/>DCMS&gt;</a> name front and back end elements relative to this PHP codeset, respectively &sup3;.</center>C六 became a fork of D7 as of 7.99 </html><ref><font size=1>selective changes thru 101 were applied by November 2025.</font></ref> which contains changes I don't want in core, so it's Dec 2023 not Jan 2025 for C六. At that point a process of migration began with the modules which are already marked unsupported at d.o. These have their .info files altered to point to our servers instead of d.o for revision status. Only those so marked at d.o before it actually terminates support will be redirected as at that point the default will switch to DS servers.
</html> [[MCP-CMS|MCP]] <html> Platform Integration and use of my my module project service.<br><br>
<br><br>As far as the C六 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 most core and sites/all modules unaltered, formally diverged as of 7.98 and all drupal projects source from clean.  D7 module authors get free forgejo access. <ref><font size=1>Registration plus a provided waiver will entitle, message me for it.</font></ref>
<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>
 
</blockquote>
</blockquote>
<blockquote style="width: 80%;">
<blockquote style="width: 80%;">
<span style="font-size:16px;position:relative;left:15px;">A Timeline</span><br>
<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>
<span style="font-size:8px;">domains common era after ceremonial</span><br>
<blockquote>
<blockquote>
<p>073-12-06 &mdash; Drupal 7.99 drops. More <a style="color: lime;" href=https://drupal.org>d.o</a> releases expected before currently committed Jan '25 EOL.</p>  
<p>075-01 &mdash; D7 disappears from new.d.o flow  but still available with others going back to d5.</p>
<p>074-12 &mdash; Project/Update mechanism redirected to forgejo.MoP, hard fork from 7.103.</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. 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. 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>  
Line 46: Line 53:
<td width="34%" align=center>[[Documentation|<b>C六书</b>]]</td>
<td width="34%" align=center>[[Documentation|<b>C六书</b>]]</td>
<td width="335%" align=right>[https://drupal.org/u/kyberuserid <span style="color: pink;"><b>d.o</b></span>]</td>
<td width="335%" align=right>[https://drupal.org/u/kyberuserid <span style="color: pink;"><b>d.o</b></span>]</td>
</tr></table>
</tr></table><html><img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=Cliu>
<html>
 


<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>),
<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>),

Latest revision as of 15:28, 8 January 2025


                       
  C六

A maintained Drupal 7 supporting the Domains CMS and sameboat network
C六 is basically just D7 with DS specifics in the sameboat module project, a MCP cell can be provisioned for just this.

C-Liu (C6*): part of DCMS, reuses final D7
"DCMS" is domain content management in the large outsided of DCP not just C六. C六 runs in a php 7 MCP cell, with support only for that context but it is mostly unaltered D7 core/contrib modules, avail from forgejo here.

To be clear, php generally in DCMS. e.g. in mediawiki and other php CMS, is at the supported level, currently 8. Ultimately DCMS will be

implemented as a fulfillment of my metadatabase concept c. 1986 and presumably in Haskell.
<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 [1] which contains changes I don't want in core, so it's Dec 2023 not Jan 2025 for C六. At that point a process of migration began with the modules which are already marked unsupported at d.o. These have their .info files altered to point to our servers instead of d.o for revision status. Only those so marked at d.o before it actually terminates support will be redirected as at that point the default will switch to DS servers.



As far as the C六 line is concerned, security and stack issues are DS system level concerns. The Cliu clean/dirty repos (common/devops, resp.), created with most core and sites/all modules unaltered, formally diverged as of 7.98 and all drupal projects source from clean. D7 module authors get free forgejo access. [2]



 


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

A Timeline
domains common era after ceremonial

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

074-12 — Project/Update mechanism redirected to forgejo.MoP, hard fork from 7.103.

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. selective changes thru 101 were applied by November 2025.
  2. Registration plus a provided waiver will entitle, message me for it.