haxcms-nodejs is the source of truth on the template files for "what is a haxsite". We also now have moved
psucdn to its own space on vercel w/ a copy of the build in it
storybook has moved out of webcomponents repo tho it is built there, it is shipped over to the cdn to roll out
haxcms (php) has had it's nodejs backend removed entirely. it is no longer truth for boilerplates but has the files still
api has separated off of webcomponents repo for scale (for jr dev testing) / versioning / build time issue resolution
elmsln still should get updates to hax ecosystem
Scenario: A new build is executed which will update all the things and keep EVERYTHING in sync version wise
new releases of all webcomponents pushed out (lerna publish / npm publish fallback for when it locks up...always...)
api repo tagged to match and pushed out (tho we deploy from master / main / latest)
code built and version / copy taken and cloned over to...
haxcms-nodejs build files
psucdn / hax.cloud
waxam mirror
haxcms (php)
elmsln
desktop
at this time, all the sources above should be tagged as matching version and pushed out
In order to do this from a singular script / location on my side..
[x] polymer.json based build routine should be moved out of haxcms (php) and into webcomponents repo as it is doing all of the other parts of building and management. Also will need the scripts to build wc-registry and what not.
[x] webcomponents build,wc-reg,scripts,etc needs copied into psucdn and haxcms-php and haxcms-nodejs and elmsln
[x] storybook needs built in webcomponents (after prior step) and shipped over to the psucdn repo for distribution / push out to vercel
[x] nodejs version becomes BOILERPLATE and coreConfig truth, copy these into PHP version
[x] haxcms-php needs VERSION.TXT from webcomponents repo, copy there
[x] version control add and commit everything in all repos; don't push yet
[x] command needs added to tag and release everything - ubiquity:release
[x] haxcms-php needs tagged as new version and pushed to github (and push)
[x] haxcms-nodejs needs tagged as new version and released (npm)
[x] CLI needs haxcms-nodejs version updated (then version and released to npm)
[x] desktop app needs it's haxcms-nodejs version updated and latest installed; then packages there would need rebuilt
haxcms-nodejs is the source of truth on the template files for "what is a haxsite". We also now have moved
Scenario: A new build is executed which will update all the things and keep EVERYTHING in sync version wise
In order to do this from a singular script / location on my side..