action-hosting-deploy
flux2
action-hosting-deploy | flux2 | |
---|---|---|
8 | 84 | |
655 | 5,943 | |
1.2% | 1.5% | |
2.9 | 9.2 | |
20 days ago | 6 days ago | |
TypeScript | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
action-hosting-deploy
-
What are the best practices to hide sensitive information in your open source project
Could they not have their own FB to develop against? Does every dev need to use just yours? If that is the case, then you'd need to use https://support.google.com/firebase/answer/7000272?hl=en also, it looks to be possible to include Firebase in your GitHub for them to pull from https://firebase.google.com/docs/hosting/github-integration
-
Anyone interested in a website that allows pushing to Firebase Hosting in just a couple of clicks?
Github Actions is the way to go for this: https://firebase.google.com/docs/hosting/github-integration
-
Taiga UI: A year in Open Source
Whenever a Pull Request is created we need to be able to quickly checkout the changes. Reading code diff is great, but sometimes you just need to tinker with the new version, test it on mobile, different browsers and OS. Cloud services are perfect for this case, they allow you to deploy the code temporarily and access it with a link from any device. We chose Firebase to host it for us and a Github action posts a link to the deployment as a comment in the Pull Request. It works like a charm and speeds up code reviews a lot. Read this article to set it up on your repository!
- Firebase: Deploy to live and preview channels via GitHub pull requests
-
Ask HN: Solo-preneurs, how do you DevOps to save time?
Lambdas and firebase on the GCP stack for CRUD apps.
One nice thing about firebase -> each PR deploys to its own preview channel[1].
Downside: Very JS heavy. I write lambdas in python though.
[1] https://firebase.google.com/docs/hosting/github-integration
-
Autodeploy subdirectory to Firebase
Google Firebase has a pretty straightforward guide to setting up auto-deploy from Github, which you can take a look at here: https://firebase.google.com/docs/hosting/github-integration
-
[Help] First time setting up Github (actions?) for Firebase Functions
What is the easiest way for setting up CI/CD from GH for Firebase functions? Maybe something like this for hosting, but only for functions?
-
3 steps for handling GitHub Workflow Secrets
Note: you can find more info about the used steps actions here actions/checkout@v2 and here FirebaseExtended/action-hosting-deploy@v0
flux2
-
Self-service infrastructure as code
Given the team had already adopted GitOps and were familiar with deployments powered by Helm Releases and Flux, we wanted to move the provisioning of the infrastructure to be part of the same process of creating the service and its continuous deployment.
-
Weaveworks Is Shuting Down
Your GitHub action can trigger a helm chart, or series thereof, or other infra tools. Declarative specifications, triggered procedurally with the context of the branch’s latest build. We use this pattern quite extensively for preview app workflows.
As of a year ago this is possible in a fully declarative way with Flux 2, but there’s a lot more moving parts and security footguns - and the idea that the maintenance of this project has lost one of its primary sponsors is worrying at best.
https://github.com/fluxcd/flux2/discussions/831
https://blog.kluctl.io/introducing-the-template-controller-a...
-
10 Ways for Kubernetes Declarative Configuration Management
FluxCD - FluxCD is another popular GitOps tool that allows developers to use a Git repository as the sole source of configuration. Flux automatically ensures that the state of the Kubernetes cluster is synchronized with the configuration in the Git repository. It supports automatic updates, meaning Flux can monitor Docker image repositories for new images and push updates to the cluster.
-
SmartCash Project - GitOps with FluxCD
#!/bin/bash aws eks update-kubeconfig --name $CLUSTER_NAME --region $AWS_REGION flux_installed=$(kubectl api-resources | grep flux) if [ -z "$flux_installed" ]; then echo "flux is not installed" curl -s https://fluxcd.io/install.sh | sudo bash flux bootstrap github \ --owner=$GH_USER_NAME \ --repository=$FLUX_REPO_NAME \ --path="clusters/$ENVIRONMENT/$CLUSTER_NAME/bootstrap" \ --branch=main \ --personal else echo "flux is installed" fi
-
Best Kubernetes DevOps Tools: A Comprehensive Guide
Flux CD enables continuous deployment to Kubernetes through GitOps by syncing Git repositories with Kubernetes clusters. Flux CD enables GitOps for Kubernetes through source control integration. It manages Kubernetes manifests as code and syncs git repo changes to clusters. Flux automates checks, deployments, and updates within clusters.
- Flux – a tool for keeping K8s clusters in sync with sources of configuration
-
Git going with GitOps on AKS: A Step-by-Step Guide using FluxCD AKS Extension
FluxCD is a GitOps tool developed by Weaveworks that allows you to implement continuous and progressive delivery of your applications on Kubernetes. It is a CNCF graduated project that offers a set of controllers to monitor Git repositories and reconciles the cluster's actual state with the desired state defined by manifests committed in the repo.
-
Ultimate EKS Baseline Cluster: Part 1 - Provision EKS
From here, we can explore other developments and tutorials on Kubernetes, such as o11y or observability (PLG, ELK, ELF, TICK, Jaeger, Pyroscope), service mesh (Linkerd, Istio, NSM, Consul Connect, Cillium), and progressive delivery (ArgoCD, FluxCD, Spinnaker).
-
Reducing Cloud Costs on Kubernetes Dev Envs
Instead, we will create a single long-lived cluster, and deploy our application in different namespaces. There are a bunch of ways to do that - see ArgoCD, Flux, custom internal tooling, or other solutions (we use our own product). That way, we:
-
What is the proper, kubernetes native way of working with multiple clusters for DR, HA?
One is to make sure configurations in both clusters is same. And for that there are many tools like fluxcd or projectsveltos
What are some alternatives?
firebase-tools - The Firebase Command Line Tools
helmfile - Deploy Kubernetes Helm Charts
flyctl - Command line tools for fly.io services
argo-cd - Declarative Continuous Deployment for Kubernetes
golang-samples - Sample apps and code written for Google Cloud in the Go programming language.
spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
ngx-scully-blog - A simple blog made for developers that is easy to setup, supports SEO, Google Adsense, Google Analytics, Facebook Pixel, and many more
terraform-provider-flux - Terraform and OpenTofu provider for bootstrapping Flux
parsemail - Hanami fork of https://github.com/DusanKasan/parsemail
skaffold - Easy and Repeatable Kubernetes Development
laravel-backup - A package to backup your Laravel app
werf - A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.