dagger
cloudflared
Our great sponsors
dagger | cloudflared | |
---|---|---|
92 | 100 | |
9,986 | 7,710 | |
4.1% | 5.0% | |
9.9 | 8.8 | |
about 5 hours ago | 7 days ago | |
Go | 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.
dagger
-
Nix is a better Docker image builder than Docker's image builder
Since there are a plethora of dagger projects, lazyweb: https://github.com/dagger/dagger#readme
They also recently released their "github actions" replacement <https://news.ycombinator.com/item?id=39550431> but holy hell their documentation is just aggressively bad
The fact that I couldn't point to one page on the docs that shows the tl;dr or the what problem is this solving
https://docs.dagger.io/quickstart/562821/hello just emits "Hello, world!" which is fantastic if you're writing a programming language but less helpful if you're trying to replace a CI/CD pipeline. Then, https://docs.dagger.io/quickstart/292472/arguments doubles down on that fallacy by going whole hog into "if you need printf in your pipline, dagger's got your back". The subsequent pages have a lot of english with little concrete examples of what's being shown.
I summarized my complaint in the linked thread as "less cowsay in the examples" but to be honest there are upteen bazillion GitHub Actions out in the world, not the very least of which your GHA pipelines use some https://github.com/dagger/dagger/blob/v0.10.2/.github/workfl... https://github.com/dagger/dagger/blob/v0.10.2/.github/workfl... so demonstrate to a potential user how they'd run any such pipeline in dagger, locally, or in Jenkins, or whatever by leveraging reusable CI functions that setup go or run trivy
Related to that, I was going to say "try incorporating some of the dagger that builds dagger" but while digging up an example, it seems that dagger doesn't make use of the functions yet <https://github.com/dagger/dagger/tree/v0.10.2/ci#readme> which is made worse by the perpetual reference to them as their internal codename of Zenith. So, even if it's not invoked by CI yet, pointing to a WIP PR or branch or something to give folks who have CI/CD problems in their head something concrete to map into how GHA or GitLabCI or Jenkins or something would go a long way
-
Testcontainers
> GHA has "service containers", but unfortunately the feature is too basic to address real-world use cases: it assumes a container image can just … boot! … and only talk to the code via the network. Real world use cases often require serialized steps between the test & the dependencies, e.g., to create or init database dirs, set up certs, etc.)
My biased recommendation is to write a custom Dagger function, and run it in your GHA workflow. https://dagger.io
If you find me on the Dagger discord, I will gladly write a code snippet summarizing what I have in mind, based on what you explained of your CI stack. We use GHA ourselves and use this pattern to great effect.
Disclaimer: I work there :)
-
BuildKit in depth: Docker's build engine explained
Dagger (https://dagger.io) is a great way to use BuildKit through language SDKs. It's such a better paradigm, I cannot imagine going back.
Dagger is by the same folks that brought us Docker. This is their fresh take on solving the problem of container building and much more. BuildKit can more than build images and Dagger unlocks it for you.
-
Cloud, why so difficult? 🤷♀️
And suddenly, it's almost painfully obvious where all the pain came from. Cloud applications today are simply a patchwork of disconnected pieces. I have a compiler for my infrastructure, another for my functions, another for my containers, another for my CI/CD pipelines. Each one takes its job super seriously, and keeps me safe and happy inside each of these machines, but my application is not running on a single machine anymore, my application is running on the cloud.
-
Share your DevOps setups
That said I've been moving my CI/CD to https://dagger.io/ which has been FANTASTIC. It's code based so you can define all your pipelines in Go, Python, or Javascript and they all run on containers so I can run actions locally without any special setup. Highly recommended.
-
What’s with DevOps engineers using `make` of all things?
You are right make is arcane. But it gets the job done. There are new exciting things happening in this area. Check out https://dagger.io.
-
Shellcheck finds bugs in your shell scripts
> but I'm not convinced it's ready to replace Gitlab CI.
The purpose of Dagger it's not to replace your entire CI (Gitlab in your case). As you can see from our website (https://dagger.io/engine), it works and integrates with all the current CI providers. Where Dagger really shines is to help you and your teams move all the artisanal scripts encoded in YAML into actual code and run them in containers through a fluent SDK which can be written in your language of choice. This unlocks a lot of benefits which are detailed in our docs (https://docs.dagger.io/).
> Dagger has one very big downside IMO: It does not have native integration with Gitlab, so you end up having to use Docker-in-Docker and just running dagger as a job in your pipeline.
This is not correct. Dagger doesn't depend on Docker. We're just conveniently using Docker (and other container runtimes) as it's generally available pretty much everywhere by default as a way to bootstrap the Dagger Engine. You can read more about the Dagger architecture here: https://github.com/dagger/dagger/blob/main/core/docs/d7yxc-o...
As you can see from our docs (https://docs.dagger.io/759201/gitlab-google-cloud/#step-5-cr...), we're leveraging the *default* Gitlab CI `docker` service to bootstrap the engine. There's no `docker-in-docker` happening there.
> It clumps all your previously separated steps into a single step in the Gitlab pipeline.
This is also not the case, we should definitely improve our docs to reflect that. You can organize your dagger pipelines in multiple functions and call them in separate Gitlab jobs as you're currently doing. For example, you can do the following:
```.gitlab-ci.yml
-
Cicada – A FOSS, Cross-Platform Version of GitHub Actions and Gitlab CI
Check out https://dagger.io/. Write declarative pipelines in code, reproducibly run anywhere.
-
Show HN: Togomak – declarative pipeline orchestrator based on HCL and Terraform
Is this similar to Dagger[1] ?
cloudflared
-
Colab error on second call with stable diffusion xl refiner
# Install apt dependencies !apt install dotnet-sdk-7.0 git # Install Clouldflared (not on apt) !wget https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb !dpkg -i cloudflared-linux-amd64.deb # Download StableSwarmUI !git clone https://github.com/Stability-AI/StableSwarmUI # Download ComfyUI backend %cd /content/StableSwarmUI !mkdir /content/StableSwarmUI/dlbackend %cd /content/StableSwarmUI/dlbackend !git clone https://github.com/comfyanonymous/ComfyUI %cd /content/StableSwarmUI/dlbackend/ComfyUI # Setup ComfyUI !pip install -r requirements.txt
-
Servarr : One docker compose file to rule them all (Jellyfin, radarr, sonarr, firefox, duplicati...)
Something like cloudflared would be awesome. https://github.com/cloudflare/cloudflared
-
KoboldAI?
if you're on windows, you can install it with the exe: https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-amd64.exe (or https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-386.exe if your using 32bit windows.)
-
Problem related to UI interface
%cd /content/naifu !pip install virtualenv && bash ./setup.sh !curl -Ls https://github.com/ekzhang/bore/releases/download/v0.4.0/bore-v0.4.0-x86_64-unknown-linux-musl.tar.gz | tar zx -C /usr/bin !curl -Lo /usr/bin/cloudflared https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64 && chmod +x /usr/bin/cloudflared !/content/naifu/venv/bin/python -m pip install -qq pytorch_lightning==1.7.7
-
How a reverse proxy like Cloudflare works in front of kub clusters?
As an alternative to traditional ingress, you can use cloudflared to expose web apps on Cloudflare via encrypted tunnels: https://github.com/cloudflare/cloudflared
- Cloudflare tunnels appear to be going down repeatedly today
-
How much can you get out of a $4 VPS?
It's not an issue anymore. Your main concerns are power and internet stability. Plus, upload speed. The rest can be worked out.
https://www.cloudflare.com/products/tunnel/
https://github.com/cloudflare/cloudflared
https://developers.cloudflare.com/cloudflare-one/connections...
-
How to set a static IP?
I would suggest a reverse proxy tunnel. There is a great and mostly free one I personally use by Cloudflare. You will need a domain, cloudflare account and install the cloudflared client on your machine. For security you can lock down this tunnel in many ways as cloudflare gives you many many options. Zero trust is a good one to look at if you are wanting to secure what ever you want to expose with a login through google or GitHub.
-
Nextcloud ! Why is it so F*ing difficult to setup!
I shared the same feeling until I gave up on "fixing" nextcloud for external access. Slapped cloudflared tunnel on it. You may have to disable Rocket Loader to get the homepage to work properly but after that it just works.
mariadb: # https://github.com/linuxserver/docker-mariadb/releases image: lscr.io/linuxserver/mariadb:${MARIADB_VERSION:-latest} container_name: nextcloud_mariadb environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - MYSQL_ROOT_PASSWORD=${NEXTCLOUD_MARIADB_ROOT_PASSWORD} - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud - MYSQL_PASSWORD=${NEXTCLOUD_MARIADB_PASSWORD} volumes: - ${NEXTCLOUD_PATH}/mariadb:/config security_opt: - no-new-privileges:true restart: unless-stopped labels: - "com.centurylinklabs.watchtower.enable=true" redis: # https://hub.docker.com/\_/redis?tab=tags image: redis:${REDIS_VERSION:-latest} container_name: nextcloud_redis security_opt: - no-new-privileges:true restart: unless-stopped labels: - "com.centurylinklabs.watchtower.enable=true" cloudflared: # https://github.com/cloudflare/cloudflared/releases image: cloudflare/cloudflared:${CLOUDFLARED_VERSION:-latest} container_name: nextcloud_cloudflared_tunnel command: tunnel run environment: - TUNNEL_TOKEN=${CLOUDFLARED_TUNNEL_TOKEN} restart: unless-stopped labels: - "com.centurylinklabs.watchtower.enable=true" watchtower: ## https://containrrr.dev/watchtower/ image: containrrr/watchtower:${WATCHTOWER_VERSION:-latest} container_name: nextcloud_watchtower environment: - WATCHTOWER_CLEANUP=${WATCHTOWER_CLEANUP:-false} - WATCHTOWER_LABEL_ENABLE=${WATCHTOWER_LABEL_ENABLE:-false} - WATCHTOWER_SCHEDULE=${WATCHTOWER_SCHEDULE:-0 0 0 * * *} ## https://pkg.go.dev/github.com/robfig/[email protected]#hdr-CRON\_Expression\_Format volumes: - /var/run/docker.sock:/var/run/docker.sock - /etc/localtime:/etc/localtime:ro restart: unless-stopped
What are some alternatives?
awesome-tunneling - List of ngrok/Cloudflare Tunnel alternatives and other tunneling software and services. Focus on self-hosting.
ZeroTier - A Smart Ethernet Switch for Earth
dnscrypt-proxy - dnscrypt-proxy 2 - A flexible DNS proxy, with support for encrypted DNS protocols.
earthly - Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
tailscale - The easiest, most secure way to use WireGuard and 2FA.
Bypass_CGNAT - Wireguard setup to bypass CGNAT with a VPS
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
ngrok-c - ngrok client for c language,Due to the use of GO ngrok language development, porting to embedded devices some inconvenience, such as openwrt, so use C language rewrite a client. Very mini, the need to support polarssl library.
wireguard-kmod - WireGuard for UDM series routers
unifios-utilities - A collection of enhancements for UnifiOS based devices
frp - A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.
headscale - An open source, self-hosted implementation of the Tailscale control server