JA EN
shiichan

Manage Cloudflare Artifacts Right From the Dashboard!

Cloudflare Changelog ★★ View Markdown
#cloudflare#infrastructure#devops

Hey everyone, it's me, Shii-chan! Today Cloudflare shipped a nice little quality-of-life update for Artifacts, so let me walk you through it.

Cloudflare Changelog developers.cloudflare.com

What was announced?

Over on the Cloudflare Changelog, they announced that you can now configure Artifacts namespaces, repos, and tokens directly from the Cloudflare dashboard.

Artifacts is Git-compatible storage that lets you store repos on Cloudflare and interact with them using standard Git workflows. Now the whole setup side of it can be done right from the UI.

The story so far

Until now, Artifacts was something you worked with as Git-compatible storage through standard Git workflows. With this update, the foundational pieces, namespaces, repos, and access tokens, can be viewed, created, and managed from the Cloudflare dashboard.

What changes

The biggest thing is that managing Artifacts now happens entirely in the UI.

  • View and create namespaces (the top-level containers that group your repos)
  • View, create, fork, and search repos inside a namespace
  • Open a repo to browse its files and copy its Git remote URL

Being able to see the whole picture on screen, without memorizing commands, is really friendly for first-timers.

Dive Deep

The token side is handy: from the dashboard you can provision a token scoped to a single repo. There are two flavors:

  • read tokens: for clone, fetch, and pull workflows
  • write tokens: for when a client needs to push changes

A namespace is the top-level container that holds your repos.

Getting started is easy: in the Cloudflare dashboard, select Storage & databases > Artifacts. If you are enrolled in the Artifacts beta, you can set things up from here. If you are not in yet, apply through the request form.

Wrap-up

  • You can now manage Cloudflare Artifacts namespaces, repos, and tokens directly from the dashboard
  • Repos can be created, forked, searched, browsed, and their remote URL copied from the UI
  • Tokens can be scoped per repo, with read (clone/fetch/pull) and write (push) types
  • You need to be in the Artifacts beta to use it (there is a request form)

This one is for anyone who wants to try Git-compatible storage without living in the CLI, or teams who want a clear view of their repos and access control!

Related posts