AirQo-frontend
This repository contains the frontend applications for the AirQo platform. (by airqo-platform)
AirQo-api
This repo contains API definitions for the AirQo platform (by airqo-platform)
Our great sponsors
| AirQo-frontend | AirQo-api | |
|---|---|---|
| 2 | 1 | |
| 21 | 20 | |
| - | - | |
| 10.0 | 10.0 | |
| 3 days ago | 3 days ago | |
| JavaScript | JavaScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
AirQo-frontend
Posts with mentions or reviews of AirQo-frontend.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-26.
-
HELP!!! How to fix module path errors in React codebase
There doesn't seem to be oñe. This is the repo https://github.com/airqo-platform/AirQo-frontend/tree/staging/netmanager. It's open source
-
My experience with GitOps. So far...
We use a Gitflow worflow in our mono-repository with all the products and the corresponding k8s manifests in the same repo.
AirQo-api
Posts with mentions or reviews of AirQo-api.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-26.
-
My experience with GitOps. So far...
A mono-repository setup can present some challenges and we faced one ourselves with the different products' delivery pipelines to production getting intertwined; deeming it impossible to deploy a specific product at a time. The CI/CD pipelines were all dependent on the git workflow and thus had the same trigger. Perhaps I can discuss how we went about in another article but during my search for an alternative autonomous trigger, is when I landed on ArgoCD. Up until then, I had miniature knowledge of GitOps but I found it interesting as I read about it. Fascinated by how the methodology would address many challenges we faced, I instantly installed ArgoCD on one of our clusters. Due to it's multi-tenant nature, I was able to add setup applications in the different clusters and their respective projects under one roof: and subsequently on boarded the entire team onto it. We now use ArgoCD as our deploy operator but kept GitHub Actions as our CI tool and Config Updater for image tags on Helm(which we defaulted to).