C-Liu: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
(44 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
<html><div  style="background-color: #372F22; color: #FAF9F6; "></html><br/>
<html><div  style="background-color: #3e3526; color: antiquewhite; "></html><br/>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp;    &nbsp; &nbsp;  <sup>&#8480;</sup><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>
<span style="position: relative; top: -15px;font-size: 34px;>  &nbsp; C六 </span>
<html><script> if (screen.width >= 1024) document.write(
<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>
"<img style='position: relative; top: -30px;left: -50px;' align=right width=175 src=https://meansofproduction.biz/img/front_1.jpg>");</script>
<blockquote>
<blockquote>
<div style="text-align: justify;width: 80%;">
<div style="text-align: justify;width: 80%;">
<br><center><b><i><a href=https://timeline.sameboat.live>Biz case #65</a>, the </html>[[C5|<span style="color: lime;">php</span>]]<html> and python codesets at the core of the Domains CMS.<br>Defining use cases are the </html> <span class=plainlinks> [https://cliu9.sameboat.live/verticals  <span style="color: lime;">sameboat network</span>]</span> <html> and the <a href=https://sameboat.meansofproduction.biz/products/aksambos><span style="color: lime;">AKSAMBAR</span></a> products. </i></b></center>
<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>.<html><br>Defining use cases are the </html> <span class=plainlinks> [https://cliu9.sameboat.network/verticals  <span style="color: lime;">sameboat network</span>]</span> <html> and the <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>
<br>&nbsp;<br>
"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 outside of the </html>[[MCP|<span style="color: lime;">DCP</span>]]<html> providing manifold services to </html>[[AKPERSON|<span style="color: lime;">AKPERSONS</span>]]<html>. <a style="color: lime;" title="pronounced 'DCMS bra'" href=https://eg.meansofproduction.biz/eg/index.php/Redvant>DCMS&lt;</a> and <a style="color: lime;" title="pronounced 'DCMS ket'" href=https://sameboat.live/DCMS/>DCMS&gt;</a> name front and back end elements relative to the Drupal 7 codebase, respectively.  C六 php will remain d7 based&sup3;.
"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 outside of the </html>[[MCP|<span style="color: lime;">DCP</span>]]<html> providing manifold services to </html>[[AKPERSON|<span style="color: lime;">AKPERSONS</span>]]<html>. <a style="color: lime;" title="pronounced 'DCMS bra'" href=https://eg.meansofproduction.biz/eg/index.php/Redvant>DCMS&lt;</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 the Drupal 7 codebase, respectively.  C六 php will remain d7 based &sup3;.
<br><br>
<br><br>
<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><html> branch from my <a href=https://sameboat.live>live sandbox</a> and the first stop before downstream deployments. The <a style="color: lime;" href=https://sameboat.live/sb-app>common app platform</a> supports C六 and my product lines as a base. The sandbox will be privately routed with the same .live suffix after its IANA registration is dropped in November, 2022 requiring use of the domain space nameservers.<br><br>
<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><html> branch from my live <a href=https://devops1.sameboat.network>shared devops</a> and the first stop before downstream public deployments. 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. Live devops will be freely aux routed after .live reaches google/Donuts expiry November, 2022 with    .network equivalents for most .live end user landings in commons. .network will be the sameboat public/IANA suffix until '27 .
Around that time, D7 will reach EOL and drupal.org will cease to support it. Drupal has a vendors program for extended support which is inappropriate for me as C六 isn't drupal. The drupal part of it nearly is though and therefore I will be maintaining a curated d7 core and set of contrib modules as part of the software as a service. The Cliu version of the update function will switch all projects from d.o to sameboat.network beforehand. As far as the C六 line is concerned, security issues are covered by domain space security. At this point, most core and contrib modules are unaltered, but all will formally diverge when their live status contrasts with d.o.  D7 module maintainers  will be able to use the D7 project mechanism here whether or not the module is used in C六. <br><br></blockquote>
<br><br>
D7 is currently provisionally scheduled for EOL in Nov '23 and drupal.org then may cease to support it (keeps getting moved out). Drupal has a vendors program for extended support which is inappropriate for me as C六 isn't drupal. The drupal part of it nearly is though and therefore I will be maintaining a curated d7 core and set of contrib modules as part of the software as a service. The C六 version of the update function operates against our server for our original modules and will switch all other projects from d.o when/if it finally declares non-support. As far as the C六 line is concerned, security issues are covered by domain space security. At this point, most core and contrib modules are unaltered, but all will formally diverge when their update origin ceases to be d.o.  D7 module maintainers  will be able to use the app server project mechanism here whether or not theier module is in the currently curated set.</html><ref><font size=1>Social networked status, i.e. free account will suffice for this.</font></ref><html> <br><br></blockquote>
<blockquote style="width: 80%;">
<blockquote style="width: 80%;">
Key Events
Key Events
<blockquote>
<blockquote>
<p>c. 4719 &mdash;  <a style="color: lime;" href=https://sameboat.live/PGS>Portable Groups</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>Portable Groups</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. 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. 4714 &mdash; First selection of sameboat name based on concept of affinity group support.</p>
Line 24: Line 23:
</blockquote><br>
</blockquote><br>
<br><br>
<br><br>
</div></blockquote>
</div></blockquote></div>
<font size=1>  &nbsp; &sup2;C-六 exceeds drupal tolerances ( <a href=https://www.drupal.org/docs/7/site-building-best-practices/avoid-too-many-modules>best practice</a>),  engineering/curation to make it so and make it work is part of the ops concept. Live now has 464 and commons 279 non core. &nbsp; &sup3;<a href=https://cliu9.sameboat.live><span style="color: lime;">D9/10</span></a> branch for devops use, other php packages generally track latest release for the operational stack.</font></div>
</html>
</html>
<table width=100%><tr>
<table width=100%><tr>
Line 32: Line 30:
<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><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>),  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; <a href=https://cliu9.sameboat.live><span style="color: lime;">D9/10</span></a> branch for devops use, other php packages generally track latest release for the operational stack.</font></html>

Revision as of 14:41, 19 January 2023


                       
  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.


 
"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 outside of the DCP providing manifold services to AKPERSONS. DCMS< and DCMS> name front and back end elements relative to the Drupal 7 codebase, respectively. C六 php will remain d7 based ³.

Sameboat commons is the stable [1] branch from my live shared devops and the first stop before downstream public deployments. The common app platform supports C六 and my product lines as a base. Live devops will be freely aux routed after .live reaches google/Donuts expiry November, 2022 with .network equivalents for most .live end user landings in commons. .network will be the sameboat public/IANA suffix until '27 .

D7 is currently provisionally scheduled for EOL in Nov '23 and drupal.org then may cease to support it (keeps getting moved out). Drupal has a vendors program for extended support which is inappropriate for me as C六 isn't drupal. The drupal part of it nearly is though and therefore I will be maintaining a curated d7 core and set of contrib modules as part of the software as a service. The C六 version of the update function operates against our server for our original modules and will switch all other projects from d.o when/if it finally declares non-support. As far as the C六 line is concerned, security issues are covered by domain space security. At this point, most core and contrib modules are unaltered, but all will formally diverge when their update origin ceases to be d.o. D7 module maintainers will be able to use the app server project mechanism here whether or not theier module is in the currently curated set.[2]

Key Events

c. 4719 — Portable Groups. 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.




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.   D9/10 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. Social networked status, i.e. free account will suffice for this.