This is a new command based on the standalone authsite tool being made based on the gh-pages-auth project made earlier, but deploys a site with the wanix bundle artifacts under /admin (configurable via flag).
It should be a copypasta of authsite when done (no dependency on authsite) customized to also deploy the bundle artifacts.
This will do a device flow auth with Auth0 and GitHub, setup Auth0, make sure you made a GitHub OAuth App, ensure a GitHub repo by default using the name of the supplied domain name argument, make sure it has GitHub Pages setup, and deploy/push the placeholder site and bundle files to the gh-pages branch.
The end result should be a GitHub Pages static site at the domain with a placeholder homepage showcasing authentication and a link to the "admin" or WANIX deployment at /admin that will require and use authentication to provide a WANIX environment with a /repo filesystem of the GitHub repository for that site.
This is a new command based on the standalone
authsitetool being made based on the gh-pages-auth project made earlier, but deploys a site with the wanix bundle artifacts under/admin(configurable via flag).It should be a copypasta of
authsitewhen done (no dependency on authsite) customized to also deploy the bundle artifacts.This will do a device flow auth with Auth0 and GitHub, setup Auth0, make sure you made a GitHub OAuth App, ensure a GitHub repo by default using the name of the supplied domain name argument, make sure it has GitHub Pages setup, and deploy/push the placeholder site and bundle files to the gh-pages branch.
The end result should be a GitHub Pages static site at the domain with a placeholder homepage showcasing authentication and a link to the "admin" or WANIX deployment at
/adminthat will require and use authentication to provide a WANIX environment with a/repofilesystem of the GitHub repository for that site.