HAXcms NodeJS steps - Githubissues

[x] Get routes to resolve for sites/whatever/system/api...
[x] CLI making a site needs to include symlinks for what haxcms typically supplies
[x] // @todo siteFields.json needs to be incorporated here so we have a standard set of site fields
[x] addNode needs to support correct path rewriting getUniqueSlugName (glitch in PHP version solved ~ 8 months ago)
[x] archiveSite
[x] cloneSite
[x] createSite
[x] add symlink in build routine so that @lrnwebcomponents is pointed to @haxtheweb
[x] new site adding things into the items area may need to just blow away a site and rebuild
[x] need to start putting in a minimum save delay of 100ms (this is too damn fast in local!)
[x] cli prototype to map directly to a single site and run a method!!!!!!
[x] filter_var needs cleaned up and replaced but requirement still exists
[x] fileSave / upload
[x] description, author fields, regions saving but not recalling correctly, null or empty not always keeping especially on boolean
[x] manifestSave
[x] "woah..-that's cool" was accepted as a title to make a slug; look at how we sanitize slug on createNode
[x] duplicate needs to clone content as well
[x] download
[x] file search
[x] openapi (json and yaml response)
[x] token validation on dashboard needs to kick you out / re-test while it attempts to process commands
[x] outlineDesigner issues stemming from some internal data management issue, probably async hell
[x] rename
[x] duplicate
[x] new items
[x] indent / move around
[x] Make a package for HAXcms / haxsite nodejs based backend that is stand alone / own monorepo of stuff; or possibly just move it into create..
[x] writing to a config directory that is below the PHP one needs to happen
[x] Map out how to peal this off from the core package; right now VERY dependent on substructure of PHP system
[x] npx haxcms-nodejs needs to see where it is and if needed, automatically create the system directory as well as the public directory
[x] Work on app.js configuration for a single site to operate by itself (required so we can get into the full system administration stuff for the CLI)
[x] listen on any open port picked by express
[x] JWT needs a way of automatic calculation and setting based on if operating in single site administration mode. This also needs a security context that you are running in security disabled mode
[x] Get live reloading working without opening a new tab
[x] HAXCMS_ROOT + this.sitesDirectory needs to be correctly resolved if working within a single or multi-site context. All calls to this combination / sitesDirectory attempts to discover root should be operating off of a method that calculates this at run time. The system also needs to operate off a mode variable that tells if we are in multi-site, single-site, etc as far as loadContext. Some variable like that
[x] Wire into the create cli so that we can leverage overlapping boilerplates instead of now how we have these replicated in two places
[ ] #2024
[ ] #2025
[ ] #2026

auto generation of public directory is a bit odd... might want to look at creating symlinks back to project root (if possible...) so that everything the command does is writing directly to the folder you are in. This would make the most sense for running in multi-site mode as well as archiving things.

Now. it also could just NOT symlink and operate off the top level for these paths as far as where it's "public" directory is.

Single site calls should be fine if we have a UI element for login because the routes just have to interpret the same way. Package.json will just have a call that invokes haxsite to run from a different file instead of app.js

haxtheweb / issues

HAXcms NodeJS steps #2008