Difference between revisions of "C-Liu"

From Cibernética Americana
 
(211 intermediate revisions by the same user not shown)
Line 1: Line 1:
<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="20%">[[Documentation|<b>C六书</b>]]</td>
 
<td width="20%">[https://drupal.org/u/kyberuserid <html><large><b>d.o</b></large></html>]</td>
 
<td width="20%">[[drupalapps|<html><span style="background-color: black;">druportfolio</span></html>]]</td>
 
<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>
+
<html><div  style="background-color: #3e3526; color: antiquewhite; "></html><br/>
<blockquote><p>
+
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp;    &nbsp; &nbsp;  <sup>&#8480;</sup><br>
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.
+
<span style="position: relative; top: -15px;font-size: 34px;>  &nbsp; C六 </span>
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>
+
 
<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
+
<html><script> if (screen.width >= 1024) document.write(
and d.o 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>
+
"<img style='position: relative; top: -30px;left: -50px;' align=right width=175 src=https://meansofproduction.biz/img/front_1.jpg>");</script>
<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>
+
<blockquote>
<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.
+
<div style="text-align: justify;width: 80%;">
</p>
+
<br><center><b><i>Names 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>
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>
+
<br>
</div></blockquote></div>
+
<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/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 is expected to remain d7 based&sup2;.
 +
<br><br>
 +
<a href=https://commons.sameboat.live><span style="color: lime;">Sameboat commons</span></a> is the stable version of my <a href=https://sameboat.live>live development</a> and the first stop before downstream deployments. The <a style="color: lime;" href=https://sameboat.live/sb-app>sameboat commons app</a> supports C六 and my product lines as a base. <br>
 +
</blockquote>
 +
<blockquote style="width: 80%;">
 +
Timeline
 +
<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&sup1;.</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></blockquote>
 +
<font size=1> &nbsp; &sup1;C-六 exceeds <a href=https://www.drupal.org/docs/7/site-building-best-practices/avoid-too-many-modules>best practice</a>,  engineering/curation to do same is part of the ops concept. Live now has 464 and commons 279 non core. &nbsp; &sup2;<a href=https://cliu9.sameboat.live><span style="color: lime;">D9</span></a> branch for devops use, cf. link.</font></div>
 
</html>
 
</html>
 +
<table width=100%><tr>
 +
<td width="33%">[[:en:Concrete 5|<html><span style="background-color: maroon; color: white;">C5 (whence "C-6")</span></html>]]</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>
 +
</tr></table>

Latest revision as of 05:48, 7 September 2021


                       
  C六


Names the php and python codesets at the core of the Domains CMS.
Defining use cases are the sameboat network and the AKSAMBAR 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 is expected to remain d7 based².

Sameboat commons is the stable version of my live development and the first stop before downstream deployments. The sameboat commons app supports C六 and my product lines as a base.

Timeline

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.




  ¹C-六 exceeds best practice, engineering/curation to do same is part of the ops concept. Live now has 464 and commons 279 non core.   ²D9 branch for devops use, cf. link.

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