Hi,
It's either been fixed in the meantime, or it's just you
curl -vvv http://cockpit-project.org/blog/cockpit-starter-kit.html 1>/dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 192.30.252.153... * TCP_NODELAY set * Connected to cockpit-project.org (192.30.252.153) port 80 (#0)
GET /blog/cockpit-starter-kit.html HTTP/1.1 Host: cockpit-project.org User-Agent: curl/7.55.1 Accept: */*
< HTTP/1.1 200 OK < Server: GitHub.com < Date: Mon, 12 Mar 2018 14:06:40 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 16823 < Vary: Accept-Encoding < Last-Modified: Mon, 12 Mar 2018 09:56:55 GMT < Vary: Accept-Encoding < Access-Control-Allow-Origin: * < Expires: Mon, 12 Mar 2018 14:16:40 GMT < Cache-Control: max-age=600 < Accept-Ranges: bytes < X-GitHub-Request-Id: CF8E:1E86:743C7E7:9D426C1:5AA68970 < { [13830 bytes data] 100 16823 100 16823 0 0 16823 0 0:00:01 --:--:-- 0:00:01 26041 * Connection #0 to host cockpit-project.org left intact
Regards.
On Mon, Mar 12, 2018 at 2:02 PM, Dusty Mabe dustymabe@redhat.com wrote:
On 03/12/2018 06:28 AM, Martin Pitt wrote:
Hello Cockpit community,
in the past months we have worked on making Cockpit's test API and CI/CD
system
available to third-party projects. So if you maintain or plan to create
your
own Cockpit page, please have a look at Cockpit's "Starter Kit": It's an example page and project which includes all the gory
webpack/babel/eslint/
release tarballs/rpm build boilerplate, an integration test that uses Cockpit's test VMs and test API, and whose PRs are validated on the
Cockpit CI
infrastructure.
Please have a look at the recent blog post which explains this in much
more
detail:
$ curl http://cockpit-project.org/blog/cockpit-starter-kit.html curl: (6) Could not resolve host: cockpit-project.org
I tried from two different net connections so I don't think it's just me.
Dusty