C-Liu: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
 
(451 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><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://devops1.sameboat.network/geo_node <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>&nbsp;<br><p style="text-align: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
commons.</font></ref> branch from my live <html> <a href=https://devops1.sameboat.network>shared devops</a> both upstream of the geonode deployments
(<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>
<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 as a base.</span>
</p>
<table style="background-color: #372F22; color: #FAF9F6; " width=100%><tr><td valign=absmiddle width=30%>
<center>C-Liu(C6*): a part of DCMS based on the Drupal CMS.</center><br> "DCMS"  refers not just to C六 but to domain content management in the large
outside of  </html>[[MCP|<span style="color: lime;">DCP</span>]] including mediawiki and other CMS and providing manifold services to [[AKPERSON|<span style="color: lime;">AKPERSONS</span>]]<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;.</td>
<td width=3%></td><td>
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六. 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.
<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 service level concerns. 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
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>
<html></td></tr>
<tr><td colspan=3 align=center><br>
<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
</html> [[MCP-CMS|MCP]] <html> Platform Integration and use of the DS update module.</td></tr></table>
</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>073-12-06 &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: midnightblue; color: antiquewhite; "></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><p>
<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>),
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.
  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;
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>
<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>
<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
<references/>
and d.o drupal distribution helpers. <br>The sameboat products and integrate with my domain space and focus on specific end service/feature sets.</i></b></center><br>
<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>[sameboat.live] which is d7 and [https://cliu.sameboat.live]<html> which is d8 has operational versions of every such service/feature set in its reference public form.<br>&nbsp;<br><br>&nbsp;<br>
</div></blockquote></div>
</html>

Latest revision as of 11:26, 3 April 2024


                       
  C六

Biz case #65, the php and python codesets at the core of the Domains CMS.
Defining use cases are the sameboat network and the SaaS/PaaS products.


 

.network is the current public/IANA suffix. Sameboat commons is the stable [1] branch from my live shared devops both upstream of the geonode deployments (bufyyz, ord, seayvr) .
The common app platform supports C六 and my product lines as a base.

C-Liu(C6*): a part of DCMS based on the Drupal CMS.

"DCMS" refers not just to C六 but to domain content management in the large outside of DCP including mediawiki and other CMS and providing manifold services to AKPERSONS. <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 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 service level concerns. 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 module is not under my current curation.[3]

DRD server runs in its last production drupal (currently 10), not modified by me except for the addition of MCP Platform Integration and use of the DS update module.

A Timeline
domains common era after ceremonial

073-12-06 — 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. Version of function in live may be different from what makes it to commons.
  2. 99 and subsequent d.o releases will be applied selectively so the drupal version number will track d.o until D7 EOL.
  3. S class plus a provided waiver will entitle, message me as Lycurgus in libera or email.