Artifactspublic-v0

curl

master
ply4 git calls29 ms290 KiB3 cachedprotocol v2
201 lines7.4 KiBRaw

Infrastructure in the curl project

Overview of infrastructure we maintain, host and run in the project for the project.

git repository

Since 2010, the main curl git repository has been hosted by GitHub, available at https://github.com/curl/curl.

We also use the issue tracker, pull requests and discussions on GitHub.

curl has an "enterprise account" on GitHub and is an "organization" on the site.

We accept sponsorship via GitHub Sponsors.

CI services

For every pull request and git push to the master repository, a number of build and testing jobs are run on a set of different CI services. The exact services vary over time. GitHub Actions and AppVeyor are the primary ones these days.

Test Clutch

A Test Clutch instance generates regular reports on curl CI test results at https://testclutch.curl.se/ as well as writing comments on curl pull requests whose tests have failed. The jobs are hosted on a Virtuozzo Application Platform PaaS instance and is managed by Dan Fandrich. The configuration code is available and managed at https://github.com/dfandrich/testclutch-curl-web

Autobuilds

The curl autobuild system is a set of scripts that build and test curl and send all output logs back to the autobuild server. The results are continuously collected and visualized on the curl website at https://curl.se/dev/builds.html.

The autobuild system and server is maintained by Daniel Stenberg.

OSS-Fuzz

Google runs the OSS-Fuzz project which also runs fuzzing on curl code, non-stop, in their infrastructure and they send us emails in the rare instances they actually find something.

OSS-Fuzz notifies those that are members in the "curl team". Any curl maintainer who wants to is welcome to participate. It requires a Google account.

Coverity

We regularly run our code through the Coverity static code analyzer thanks to them offering this service to us free of charge.

CodeSonar

CodeSonar analyzes the curl source code daily and emails Daniel Stenberg whenever it finds suspected problems in the source code. I hope and expect that we can invite other maintainers to access these reports soon.

Domain names

The project runs services and website using a few different curl related domain names, including curl.se and curl.dev. Daniel Stenberg owns these domain names.

Until a few years ago, the curl website was present at curl.haxx.se. The haxx.se domain is owned by Haxx AB, administered by Daniel Stenberg. The curl.haxx.se name is meant to keep working and be redirecting to curl.se for the foreseeable future.

Websites

The main curl website at curl.se is maintained by curl maintainers and the content is available and managed at https://github.com/curl/curl-www. The site updates from git and runs make every 20 minutes. Any change pushed to git can thus take up to 20 minutes until it takes effect on the origin server.

The content on curl.dev is available and managed at https://github.com/curl/curl.dev/

The content on everything.curl.dev is available and managed at https://github.com/curl/everything-curl/

The machine hosting the website contents for these three sites is owned by Haxx AB and is primarily managed by Daniel Stenberg (co-owner of the Haxx company). The machine is physically located in Sweden.

curl release tarballs are hosted on https://curl.se/download.html. They are uploaded there at release-time by the release manager.

curl-for-win downloads are hosted on https://curl.se/windows/ and are uploaded to the server by Viktor Szakats.

curl-for-QNX downloads are hosted on https://curl.se/qnx/ and are uploaded to the server by Daniel Stenberg.

Daily release tarball-like snapshots are generated automatically and are provided for download at https://curl.se/snapshots/.

CA certificate bundles are extracted from the Firefox source code, hosted by Mozilla and converted to PEM file format and is offered for download. The conversion checks for updates daily. The bundle is provided for download at https://curl.se/docs/caextract.html.

There is an automated "download check bot" that runs twice daily to scan for available curl downloads to populate the curl download page appropriately with the correct updated information. The bot uses URLs and patterns for all download packages and is maintained in a database, maintained by Daniel Stenberg and Dan Fandrich.

The TLS certificate for the origin curl web server is automatically updated from Let's Encrypt.

CDN

Fastly runs the Content Delivery Network (CDN) that fronts all the curl websites. The CDN caches content that it gets from the origin server. Recently, roughly 99.99% of web requests are satisfied by the CDN without having to reach the origin.

The CDN caches different content at different lengths depending on the content-type. The caching thus adds to the time for a change to have an effect on the site from the moment it gets pushed to the git repository.

Using this setup, we provide four IPv4 addresses and eight IPv6 addresses for anycast access to the site. Should be snappy from virtually everywhere across the globe.

The CDN servers support HTTP/1, HTTP/2 and HTTP/3. They set HSTS for a year. The http:// version of the site redirects to https://.

Fastly manages the TLS certificates from Let's Encrypt for the servers they run on the behalf of curl.

Containers

The curl project offer container builds of curl. The source repository for them is located at https://github.com/curl/curl-container.

Container images are hosted at https://quay.io/repository/curl/curl and https://hub.docker.com/r/curlimages/curl

DNS

The primary domain name, curl.se is managed by Kirei and is offered over fault-tolerant anycast servers. High availability and fast access for everyone.

The actual physical DNS files and origin bind instance is managed by Daniel Stenberg.

Mailing lists

The curl related mailing lists are hosted by Haxx AB on lists.haxx.se and are maintained by Daniel Stenberg. This includes the mailman2 and Postfix instances used for this.

Email

We use a few rare additional curl related email aliases in the curl domains. They go through the mail server mail.haxx.se maintained by Daniel Stenberg

Open Collective

We use Open Collective as our "fiscal host". All money sent to and received by the curl project is managed by Open Collective.

Merchandise

We have stickers, coffee mugs and coasters. They are managed by Daniel who sits on the inventory. The best way to get your hands on curl merchandise is to attend events where Daniel is physically.

Chat

Some curl developers, maintainers, users and enthusiasts use IRC for real-time chat about curl and related topics. This done in the #curl channel on the libra.chat IRC network. Daniel Stenberg (bagder) is registered owner of the channel. We do not run any IRC servers or services ourselves.

curlbot is a service in the channel that shows details about GitHub issues and pull requests when publicly mentioned using #[number]. The bot is run by user TheAssassin.

There is a Matrix bridge to the IRC channel called matrix.curl.se. The bridge is setup and run by Sergio Durigan Junior and Daniel Stenberg.

curl online chat documentation

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# Infrastructure in the curl project
9Overview of infrastructure we maintain, host and run in the project for the
10project.
12## git repository
14Since 2010, the main curl git repository has been hosted by GitHub, available
15at https://github.com/curl/curl.
17We also use the issue tracker, pull requests and discussions on GitHub.
19curl has an "enterprise account" on GitHub and is an "organization" on the
20site.
22We accept sponsorship via GitHub Sponsors.
24## CI services
26For every pull request and git push to the master repository, a number of
27build and testing jobs are run on a set of different CI services. The exact
28services vary over time. GitHub Actions and AppVeyor are the primary ones
29these days.
31## Test Clutch
33A [Test Clutch](https://github.com/dfandrich/testclutch) instance generates
34regular reports on curl CI test results at https://testclutch.curl.se/ as well
35as writing comments on curl pull requests whose tests have failed. The jobs
36are hosted on a Virtuozzo Application Platform PaaS instance and is managed by
37Dan Fandrich. The configuration code is available and managed at
38https://github.com/dfandrich/testclutch-curl-web
40## Autobuilds
42The curl autobuild system is a set of scripts that build and test curl and
43send all output logs back to the autobuild server. The results are
44continuously collected and visualized on the curl website at
45<https://curl.se/dev/builds.html>.
47The autobuild system and server is maintained by Daniel Stenberg.
49## OSS-Fuzz
51Google runs the [OSS-Fuzz](https://google.github.io/oss-fuzz/) project which
52also runs fuzzing on curl code, non-stop, in their infrastructure and they
53send us emails in the rare instances they actually find something.
55OSS-Fuzz notifies those that are members in the "curl team". Any curl
56maintainer who wants to is welcome to participate. It requires a Google
57account.
59## Coverity
61We regularly run our code through the [Coverity static code
62analyzer](https://scan.coverity.com/) thanks to them offering this service to
63us free of charge.
65## CodeSonar
67[CodeSonar](https://www.adacore.com/codesonar) analyzes the curl
68source code daily and emails Daniel Stenberg whenever it finds suspected
69problems in the source code. I hope and expect that we can invite other
70maintainers to access these reports soon.
72## Domain names
74The project runs services and website using a few different curl related
75domain names, including `curl.se` and `curl.dev`. Daniel Stenberg owns these
76domain names.
78Until a few years ago, the curl website was present at `curl.haxx.se`. The
79`haxx.se` domain is owned by Haxx AB, administered by Daniel Stenberg. The
80curl.haxx.se name is meant to keep working and be redirecting to curl.se for
81the foreseeable future.
83## Websites
85The main curl website at `curl.se` is maintained by curl maintainers and the
86content is available and managed at https://github.com/curl/curl-www. The site
87updates from git and runs make every 20 minutes. Any change pushed to git can
88thus take up to 20 minutes until it takes effect on the origin server.
90The content on `curl.dev` is available and managed at
91https://github.com/curl/curl.dev/
93The content on `everything.curl.dev` is available and managed at
94https://github.com/curl/everything-curl/
96The machine hosting the website contents for these three sites is owned by
97Haxx AB and is primarily managed by Daniel Stenberg (co-owner of the Haxx
98company). The machine is physically located in Sweden.
100curl release tarballs are hosted on https://curl.se/download.html. They are
101uploaded there at release-time by the release manager.
103curl-for-win downloads are hosted on https://curl.se/windows/ and are uploaded
104to the server by Viktor Szakats.
106curl-for-QNX downloads are hosted on <https://curl.se/qnx/> and are uploaded
107to the server by Daniel Stenberg.
109Daily release tarball-like snapshots are generated automatically and are
110provided for download at <https://curl.se/snapshots/>.
112CA certificate bundles are extracted from the Firefox source code, hosted by
113Mozilla and converted to PEM file format and is offered for download. The
114conversion checks for updates daily. The bundle is provided for download at
115<https://curl.se/docs/caextract.html>.
117There is an automated "download check bot" that runs twice daily to scan for
118available curl downloads to populate the curl download page appropriately with
119the correct updated information. The bot uses URLs and patterns for all
120download packages and is maintained in a database, maintained by Daniel
121Stenberg and Dan Fandrich.
123The TLS certificate for the origin curl web server is automatically updated
124from Let's Encrypt.
126## CDN
128Fastly runs the Content Delivery Network (CDN) that fronts all the curl
129websites. The CDN caches content that it gets from the origin server.
130Recently, roughly 99.99% of web requests are satisfied by the CDN without
131having to reach the origin.
133The CDN caches different content at different lengths depending on the
134content-type. The caching thus adds to the time for a change to have an effect
135on the site from the moment it gets pushed to the git repository.
137Using this setup, we provide four IPv4 addresses and eight IPv6 addresses for
138anycast access to the site. Should be snappy from virtually everywhere across
139the globe.
141The CDN servers support HTTP/1, HTTP/2 and HTTP/3. They set HSTS for a year.
142The `http://` version of the site redirects to `https://`.
144Fastly manages the TLS certificates from Let's Encrypt for the servers they
145run on the behalf of curl.
147## Containers
149The curl project offer container builds of curl. The source repository for
150them is located at <https://github.com/curl/curl-container>.
152Container images are hosted at <https://quay.io/repository/curl/curl> and
153<https://hub.docker.com/r/curlimages/curl>
155## DNS
157The primary domain name, `curl.se` is managed by Kirei and is offered over
158fault-tolerant anycast servers. High availability and fast access for
159everyone.
161The actual physical DNS files and origin bind instance is managed by Daniel
162Stenberg.
164## Mailing lists
166The curl related mailing lists are hosted by Haxx AB on `lists.haxx.se` and
167are maintained by Daniel Stenberg. This includes the mailman2 and Postfix
168instances used for this.
170## Email
172We use a few rare additional curl related email aliases in the curl domains.
173They go through the mail server `mail.haxx.se` maintained by Daniel Stenberg
175## Open Collective
177We use [Open Collective](https://opencollective.com/curl) as our "fiscal
178host". All money sent to and received by the curl project is managed by Open
179Collective.
181## Merchandise
183We have stickers, coffee mugs and coasters. They are managed by Daniel who
184sits on the inventory. The best way to get your hands on curl merchandise is
185to attend events where Daniel is physically.
187## Chat
189Some curl developers, maintainers, users and enthusiasts use IRC for real-time
190chat about curl and related topics. This done in the `#curl` channel on the
191`libra.chat` IRC network. **Daniel Stenberg** (`bagder`) is registered owner
192of the channel. We do not run any IRC servers or services ourselves.
194`curlbot` is a service in the channel that shows details about GitHub issues
195and pull requests when publicly mentioned using #[number]. The bot is run by
196user `TheAssassin`.
198There is a Matrix bridge to the IRC channel called `matrix.curl.se`. The
199bridge is setup and run by **Sergio Durigan Junior** and **Daniel Stenberg**.
201[curl online chat documentation](https://curl.se/docs/irc.html)
Diagnostics4 git calls · 29 ms
CallStatusSizeTime029 ms
discover200152 B2 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit2 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=2
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=23
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=3
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2003.3 KiB · hit24 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=3328
git.response.cache=HIT
git.response.duration_ms=24
git.fetch.wants=ddcd1289d960dae71178dae0b537cb254db80cd1
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=3328
git.pkt.payload.max=3307
git.sideband.band1.bytes=3306
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e1a4633f915e44
Request
b14941e6…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format