Custom Domain Names for Repositories   βeta

By default, your Gemfury reposistories are available via the [repo] endpoints where the Repo-URL hostname is based on the package type and package manager that you are using. For example, a RubyGems repository is available via:

By enabling a custom domain for a Gemfury account, you will also be able to access this account’s repositories via a domain of your choosing:

Please note that Gemfury works with domains that you already own and manage. We do not provide domain registration/DNS services, nor do we provide continuous monitoring to verify your domain configuration.

Adding a custom domain to your account

During the beta period, custom domains are only available by contacting customer service.

Configuring DNS for your custom domain

After adding your domain to your account, you’ll need to work with your DNS provider to point your domain to Gemfury. This is done by creating a CNAME record for your domain as follows:

Record Name Target
CNAME repo
CNAME other

To set up an apex domain without a subdomain, such as, you must configure a similar ALIAS or ANAME record with your DNS provider. Not all DNS providers support this feature.

Testing your custom domain

To recognize and serve your repository index, your DNS record must point to Gemfury’s custom domains endpoint. To confirm that your CNAME is active, use the dig command:

$ dig +nostats +nocomments +nocmd	3554	IN	CNAME

Using your repository via custom domains

Once you’ve configured your domain, all Gemfury repositories are available as top-level paths of your custom domain. In your configuration, you would replace your repository URLs are follows:

Repo Standard Repo-URL With custom domain
RubyGems h​ttps:// h​ttps://
Javascript npm h​ttps:// h​ttps://
PHP Composer h​ttps:// h​ttps://
Python PyPI h​ttps:// h​ttps://
APT/DEB h​ttps:// h​ttps://
YUM/RPM h​ttps:// h​ttps://
NuGet h​ttps:// h​ttps://

These custom-domain URLs can be directed to either private and public repositories by including or excluding a secret token via Basic Auth (ie. Authorization header). Gemfury does not support using path tokens to authenticate into your custom domain.