laravel-backup
external-dns
Our great sponsors
laravel-backup | external-dns | |
---|---|---|
5 | 78 | |
5,472 | 7,207 | |
0.9% | 2.7% | |
8.5 | 9.6 | |
28 days ago | about 2 hours ago | |
PHP | Go | |
MIT License | 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.
laravel-backup
-
Packages for Laravel
https://github.com/jeremykenedy/laravel-logger#authentication-middleware-usage https://github.com/beyondcode/laravel-dump-server https://github.com/barryvdh/laravel-debugbar https://github.com/laravel-shift/blueprint https://github.com/spatie/laravel-backup https://github.com/spatie/laravel-permission https://github.com/spatie/laravel-activitylog https://github.com/realrashid/sweet-alert https://github.com/rappasoft/laravel-livewire-tables https://github.com/yajra/laravel-datatables https://github.com/Labs64/laravel-boilerplate https://github.com/creativetimofficial/argon-dashboard-laravel https://github.com/the-control-group/voyager https://github.com/beyondcode/laravel-er-diagram-generator
-
10 Laravel packages that might save your day
8. spatie/laravel-backup
-
4 Packages You Need in Any Laravel Project
4. spatie/laravel-backup https://github.com/spatie/laravel-backup
-
Ask HN: Solo-preneurs, how do you DevOps to save time?
In my case I'm dumping + zipping the entire database at the application level. In my case is as simple as adding a library [1], scheduling the job and transferring to AWS S3 (my main application is on DigitalOcean)
-
Development environment suggestions
Database backups via php artisan backup:run
external-dns
-
Kubernetes External DNS provider for Hetzner
One of the reasons why I chose Hetzner was that it WAS supported by the ExternalDNS project. I didn't quite understand why the Hetzner provider was pulled, but I saw that an attempt of re-adding it was refused, on the ground that the upcoming webhook architecture would have allowed to better maintain providers.
-
I am stuck on learning how to provision K8s in AWS. Security groups? ALB? ACM? R53?
So here’s the solution I have taken for our current stack. EKS and its dependencies are created through terraform using the eks module as well as provision a route53 subdomain and a wildcard cert. Once we have that created, I have installed this deployment into the cluster via the helm module: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/. This allows me to use kuberentes resources (load balancers or ingress objects) and it will handle all the provisioning of load balancers and security groups for me, based on my application yaml and annotations. We also use https://github.com/kubernetes-sigs/external-dns to manage all of our specific host names for the applications through annotations. So to generally put, terraform manages out Kubernetes clusters, and Kubernetes manages the deployment of anything needed for the application including volumes, load balancers, hostnames though Kubernetes system deployments
-
Kubernetes as a Platform vs. Kubernetes as an API
Disclaimer: I work for AWS but had nothing to do with this blog post (I'm seeing it for the first time with everyone else here).
I think this is an unfair summary of the post. Of course, using Kubernetes to orchestrate other AWS services is going to be a go-to example on the _AWS_ blog, but there is plenty of vendor-agnostic software doing similar things: DNS Records[1], Databases[2], even using Kubernetes CRDs to deploy Kubernetes[3].
The idea of using Kubernetes as an API to orchestrate external resources doesn't inherently lock you into any single vendor.
-
Does it make sense to use nginx on top of the ingress-nginx
For the average developer an Ingress is substantially simpler to understand. For an expert such as yourself there are additional annotations which may be added, to use nginx specfic features. However the big win using the nginx ingress controller is integration with other Kubernetes features like cert manager and External DNS
-
Kubernetes external-dns add support for pi-hole in the latest release
In the latest version v0.13.2 add support for pi-hole as a dns provider:
-
Help me understand real use cases of k8s, I can’t wrap my head around it
external-dns
- Dont understand how I can watch external resources modification/deletion with my custom operator
-
cloudflare and ingress-nginx
I can then set annotations on the Ingress resource to tell external-dns to flip the proxy switch on the DNS record in Cloudflare:
-
Istio woes on eks 1.22 - external-dns version stuck to v0.7.2
according to users in this issue they claim the external-dns image being a cause of their dns failing on kubernetes 1.22. https://github.com/kubernetes-sigs/external-dns/issues/961
What are some alternatives?
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
cloudflare-ingress-controller - A Kubernetes ingress controller for Cloudflare's Argo Tunnels
ingress-nginx - Ingress-NGINX Controller for Kubernetes
crossplane - The Cloud Native Control Plane
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
k3s - Lightweight Kubernetes
cert-manager - Automatically provision and manage TLS certificates in Kubernetes
charts - ⚠️(OBSOLETE) Curated applications for Kubernetes
kube-vip - Kubernetes Control Plane Virtual IP and Load-Balancer
csi-driver-smb - This driver allows Kubernetes to access SMB Server on both Linux and Windows nodes.
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.