This commit introduces new commands to streamline Data Connect
management, including enabling APIs, initializing Firebase, and
deploying schemas. These commands enhance developer experience by
providing easy-to-use shortcuts for common Data Connect tasks.
This commit removes obsolete files and configurations related to the
previous App Engine deployment of the internal-launchpad service.
These artifacts are no longer needed since the service has been
migrated to Cloud Run.
The following changes were made:
- Deleted `fix-appengine-permissions-complete.sh`,
`fix-project-level-permissions.sh`, and
`create-missing-repository.sh` scripts.
- Removed the `app.yaml` file from `firebase/internal-launchpad/`.
- Updated `firebase.json` to remove the `launchpad` hosting target.
- Added `security` label to `labels.yml`
feat(scripts/export_issues.sh): allow filtering issues by state and label
This commit introduces changes to both the Makefile and the
export_issues.sh script to allow users to filter GitHub issues
by state and label when exporting them to a markdown file.
The Makefile's `export-issues` target now accepts an optional
`ARGS` variable, which is passed to the `export_issues.sh`
script. This allows users to specify command-line arguments
such as `--state=all` or `--label=bug` to filter the issues
being exported.
The `export_issues.sh` script has been updated to parse these
command-line arguments and use them to construct the `gh issue
list` command. The script now supports the `--state` and
`--label` options, which allow users to filter issues by their
state (e.g., open, closed, all) and label, respectively.
These changes provide users with more flexibility in exporting
GitHub issues, allowing them to generate markdown files that
contain only the issues that are relevant to their needs.
feat(admin-web): display environment badge in admin console
feat(admin-web): configure Nginx for SPA and copy config
fix(Makefile): fix typo in CR_ADMIN_IMAGE_URI variable assignment
feat(firebase): update launchpad title to "Launchpad"
feat(Makefile): add IAP configuration management for both launchpad and admin
feat(Makefile): refactor IAP user management commands for reusability
feat(Makefile): add Dockerfile for admin-web to containerize the application
feat(Makefile): remove App Engine deployment targets for admin-web
This commit introduces significant changes to the deployment process
for the admin console, migrating it from App Engine to Cloud Run and
integrating Identity-Aware Proxy (IAP) for enhanced security.
The key changes include:
- **Admin Console Deployment to Cloud Run:** The admin console is now
deployed to Cloud Run using a Dockerfile that builds and
containerizes the application. This provides a more scalable and
flexible deployment environment.
- **IAP Integration:** IAP is now enabled for the admin console,
restricting access to authorized users only. This enhances the
security of the application and protects sensitive data.
- **IAP Configuration Management:** New commands have been added to
the Makefile to manage IAP configuration for both the launchpad and
admin console. These commands allow for easy addition and removal
of IAP users.
- **Refactored IAP User Management Commands:** The IAP user management
commands have been refactored to be more reusable and generic. This
allows for easier management of IAP users for both the launchpad and
admin console.
- **Removal of App Engine Deployment Targets:** The App Engine
deployment targets for the admin console have been removed, as the
application is now deployed to Cloud Run.
These changes provide a more secure, scalable, and maintainable
deployment process for the admin console.
This commit removes legacy App Engine deployment artifacts and updates the Makefile to reflect the successful migration of the `internal-launchpad` service to Cloud Run.
The following changes were made:
- Deleted obsolete permission scripts:
- `fix-appengine-permissions-complete.sh`
- `fix-project-level-permissions.sh`
- `create-missing-repository.sh`
- Removed the `firebase/internal-launchpad/app.yaml` file.
- Updated `firebase.json` to remove the `launchpad` hosting configuration.
These changes streamline the repository, reduce developer confusion, and prevent the accidental use of outdated deployment logic.
feat(README.md): update README to reflect monorepo structure and admin console
feat: remove setup_admin_console.sh script
The setup_admin_console.sh script is removed because the admin console setup is now integrated into the Makefile.
The README is updated to reflect the new monorepo structure and the admin console.
The Makefile is updated to include commands for installing, developing, and building the admin console.
feat(admin-web): implement basic layout and navigation
feat(admin-web): implement dashboard page with key metrics
feat(admin-web): implement user management page
feat(admin-web): implement analytics page with user stats
feat(admin-web): implement logs explorer page
style(admin-web): add tailwind css and shadcn/ui components
build(admin-web): configure eslint and prettier for code quality
This commit introduces the admin-web application, a React-based
administration console built with Vite.
- The application provides a central interface for managing
users, monitoring platform health, and troubleshooting issues.
- It includes a basic layout with navigation, a dashboard
displaying key metrics, a user management page, an analytics
page with user statistics, and a logs explorer page.
- Tailwind CSS and shadcn/ui components are used for styling.
- ESLint and Prettier are configured to ensure code quality.
feat: add issue template
feat: add labels.yml with platform:admin label
feat: add setup_admin_console.sh script and update Makefile
This commit introduces several new features and files to the
repository:
- Adds a reference document for Base44 entity schemas to
ensure data integrity during the migration to the new
GCP/Firebase backend.
- Adds an issue template to standardize issue reporting and
ensure all necessary information is included.
- Adds a new label to `labels.yml` for tasks specific to the
Admin Console web app.
- Adds a shell script to automate the setup of the Admin
Console web application, including scaffolding,
dependency installation, and configuration. Also updates
the Makefile to include new targets for managing the Admin
Console application.
- Adds issues to create markdown file.
feat(firebase/internal-launchpad): enhance UI with Tailwind CSS, improving responsiveness and aesthetics
feat(firebase/internal-launchpad): improve diagram loading and error handling
feat(firebase/internal-launchpad): enhance navigation with Tailwind CSS styling
feat(firebase/internal-launchpad): improve home view with Tailwind CSS styling
feat(firebase/internal-launchpad): add pan and zoom functionalities to diagrams
This commit updates the title and favicon in the index.html file
to reflect the new KROW branding. It also updates the links in
the internal launchpad to point to the correct environments.
feat: add script to patch index.html during integration
This commit adds a new script to patch the index.html file during
the integration process. This script updates the title and favicon
to reflect the new KROW branding.
style: update badge style in Dashboard.jsx
This commit updates the badge style in the Dashboard.jsx file to
use a span element with rounded corners instead of the Badge
component. This is to match the design of the new KROW branding.
This commit introduces Firebase configuration files (.firebaserc,
firebase.json) and updates the Makefile to include deployment
commands for different environments (dev, staging).
The .firebaserc file defines Firebase projects for development and
staging, along with hosting targets.
The firebase.json file configures hosting settings, including
rewrites and ignores. It defines hosting targets for the main app
in dev and staging, and a separate target for an internal launchpad.
The Makefile is updated to include:
- GCP project IDs for dev and staging.
- Environment detection (ENV variable).
- Conditional variables based on the environment (GCP_PROJECT_ID,
FIREBASE_ALIAS, HOSTING_TARGET).
- Deployment commands for the launchpad and the main app.
- The build command now passes the environment variable to the
frontend build process.
The internal launchpad is added to firebase/internal-launchpad/index.html
to provide quick access to application URLs and Firebase/GCP
consoles for different environments.
A patch script is added to inject the environment label into the
Dashboard page.
The index.html title is changed to KROW.
These changes enable streamlined deployment and environment
management for the KROW application.
This commit introduces a new internal launchpad for the KROW
project. The launchpad provides a centralized location for
accessing applications, resources, and diagrams related to the
project.
The launchpad includes the following features:
- A sidebar navigation menu for accessing different sections of
the launchpad.
- A home view with links to applications and resources.
- A diagram viewer for displaying static SVG and dynamic Mermaid
diagrams.
- Zoom and pan functionality for diagrams.
- Dynamic loading of Mermaid diagrams from a configuration file.
This launchpad is designed to improve the discoverability of
project resources and provide a more streamlined experience for
developers and stakeholders.
feat(Makefile): patch Layout.jsx queryKey for local development
feat(frontend-web): mock base44 client for local development with role switching
feat(frontend-web): add event assignment modal with conflict detection and bulk assign
feat(frontend-web): add client dashboard with key metrics and quick actions
feat(frontend-web): add layout component with role-based navigation
feat(frontend-web): update various pages to use "@/components" alias
feat(frontend-web): update create event page with ai assistant toggle
feat(frontend-web): update dashboard page with new components
feat(frontend-web): update events page with quick assign popover
feat(frontend-web): update invite vendor page with hover card
feat(frontend-web): update messages page with conversation list and message thread
feat(frontend-web): update operator dashboard page with new components
feat(frontend-web): update partner management page with new components
feat(frontend-web): update permissions page with new components
feat(frontend-web): update procurement dashboard page with new components
feat(frontend-web): update smart vendor onboarding page with new components
feat(frontend-web): update staff directory page with new components
feat(frontend-web): update teams page with new components
feat(frontend-web): update user management page with new components
feat(frontend-web): update vendor compliance page with new components
feat(frontend-web): update main.jsx to include react query provider
feat: add vendor marketplace page
feat: add global import fix to prepare-export script
feat: add patch-layout-query-key script to fix query key
feat: update patch-base44-client script to use a more robust method
This commit introduces a script to patch the base44Client.js file
within the frontend-web directory. This patch is specifically
designed to facilitate local development by mocking user roles and
authentication, allowing developers to test role-based functionality
without needing a full Base44 SDK setup.
The Makefile is updated to include a call to this script during the
`integrate-export` target, ensuring that the patch is applied
automatically when integrating a fresh Base44 export.
This change streamlines the local development process and enhances
the testing capabilities for role-based features.
This commit adds a new card to the launchpad page with links to the
legacy mobile apps on the Google Play Store and Apple App Store. This
will make it easier for users to find and access the legacy mobile apps.
This commit introduces a pre-push Git hook that prevents direct
pushes to the `main` and `dev` branches. This enforces the use of
pull requests for merging changes into these protected branches,
promoting code review and maintaining branch stability.
The changes include:
- Adding a `install-git-hooks` target to the Makefile to symlink
the pre-push script into the `.git/hooks/` directory.
- Creating the `scripts/git-hooks/pre-push` script that checks the
target branch and aborts the push if it matches a protected branch.
- Updating the `CONTRIBUTING.md` file to instruct developers to
install the Git hooks after setting up their development
environment.
This commit introduces several new files and updates to support
SR&ED tracking and project management:
- Adds a template for SR&ED tasks to standardize issue creation.
- Adds a Makefile command to set up GitHub labels from a YAML file.
- Adds a Makefile command to export SR&ED-eligible issues to a
Markdown file.
- Adds a Makefile command to create issues from a file.
- Adds documentation for SR&ED tracking and development
conventions.
- Adds a YAML file to define GitHub labels.
- Adds scripts to set up GitHub labels, export issues, and create
issues from a file.
- Updates the project plan to include SR&ED considerations.
These changes aim to improve project organization, facilitate
SR&ED claims, and streamline development workflows.