A micro-frontend(mife...like "wife":) bootstrap that authenticates mife users against Firebase and provides access to a configured mife realm. This project is similar to micro-private, but differs by its use of several web components that were deployed from micro-client-library.
With the use of micro-cms, dynamic content to any GraphQL datasource is supported.
NOTE: The unit tests for this project are temporarily unplugged awaiting resolution of a 'zen-observable' issue, a dependency of @apollo/client as configured here. So far, the issue is isolated to testing, Apollo seems to do a fine job with its primary function, pulling content.Here 's the issue along with a manual hack-around, if you are excited for the tests to run.
To encourage rapid iteration/deployment, this project is configured for, and this quickstart assumes, use with bin-zsh.
$ pu.sh --local
$ REMOTE_ALIAS=stage pu.sh --remote=<REMOTE_ALIAS>
We value your perspective and invite you to participate in discovering new mife techniques and methods, regardless of your skill-level. Because of the shared common purpose, we try to quickly respond to your hackathon team... your success is ours!
Caution: All Micro-cosm projects are heavily-opinionated with bias towards Nodejs(Typescript)/GoLang/Angular(CLI)/Google(GCP)/Kubernetes.
A few goals of the overarching project:
- Use latest lts node implementation
- Use latest of angular cli
- Use
ng new <PROJECT NAME>to create each new mife - Use @angular/schematics wherever available to install libraries
- Use @angular/cli best practice and default libraries where conflicts with mife best practices are not present
- Use the latest library version of the most active project that serves the need
- Target 90% code coverage as constribution acceptance criteria
- Focus exclusively on GCP deployability and infrastructure support.
This project was initially generated with Angular CLI version 11.2.7.
- Replace CMS component with Angular Element
- Replace Angular code environment files with static remote environment stored in environment-specific GCP bucket or GCP Secret Manager, as appropriate.