With the introduction of the Package Activity API and accompanying CLI command, you can now quickly and easily check your entire repository for packages' activity status or even take a detailed approach and view packages individually (per day/per package).
You can save on your storage costs by eliminating inactive packages and retaining only the packages you or your users derive value from storing and distributing via Cloudsmith.
Check out our blog on how to get started with monitoring your package activity.Read More
If you're making use of Cloudsmith's custom domains feature, you can now request that the top-level (i.e. root page) of your domain (e.g. npm.example.com) redirects to a location of your choice.
This provides a little more "discoverability" for your users, by sending them to the right place if they go to the domain directly. Whether you want to redirect them to the UI for your repositories, or to your customer support page, we've got you covered.
If you wish to update your domains with this feature, please contact us and we'll be happy to help.Read More
As a vendor, understanding your bandwidth usage is an invaluable insight into how packages are distributed across your user base and how specific users have grown over a timeframe.
The easiest way to get started exploring these metrics is to check out the metrics command within the Cloudsmith CLI. Alternatively, to get more fine-grained metrics, you can implement a programmatic solution using our API or one of the API binding libraries published in various languages. Check out our blog for an overview of how to get started analysing your Bandwidth usage.Read More
We're very pleased to announce that the Debian package format now supports upstream proxying and caching.
Adding a Debian upstream allows for searching and downloading packages not yet in your Cloudsmith repository using the native apt tooling. Fetches made for packages resolved to an upstream can be cached and synchronised to your Cloudsmith repository - helping to protect your software dependencies from outages, improve visibility, and apply fine-grained access controls for your teams, customers and users.
Debian joins Maven as our second format to support proxying and caching. We are working hard to continue expanding to other supported formats. Watch this space!Read More
Between now and 25th of September, we'll be deprecating user-based repositories and accounts.
If you have a user account, with repositories, we'll be performing the following actions for you:
If you have a user account, but with no repositories:
As part of this process, we'll put the following restrictions in place:
Some of these steps will happen earlier than 25th of September (e.g. preventing the creation of new repositories for users). You're also free to migrate yourself earlier, at any point.
Not at all! This is a user-focused change, and orgs are not affected.
Only if you use your username + password (or API key) to download packages.
We've designed the migration process so that the majority of your client-side tools and integrations will remain the same. The API key you were using will be the same (you'll still authenticate as your user), and any push configuration will use the same account slug/username.
The repository configurations will also remain the same, so you don't need to update/change settings, entitlement tokens, packages, etc.
For example, if your username was cloudsmyths and you were doing the following to upload a Debian package, it will still work the same:
cloudsmith push deb cloudsmyths/production/ubuntu/xenial/ cloudsmyths-1.2.5.deb
Your new username will be something like cloudsmyths-owner. So the only impact/change that might be necessary is if you are downloading packages using your username + password. If so, you'll need to update your username to match.
You'll be able to rename both your user and your organisation after the migration, in the situation you're not happy with our renames.
This is part of our vision for being even more customer-obsessed, by focusing on the team aspects of the Cloudsmith experience. Individual users are, and always be, an integral part of our service; but the best of package management is built on collaboration with others. So by changing the focus of accounts to org-only, we hope to build even greater value for teams around the world. Other than that, this shouldn't impact how you interact with Cloudsmith. You'll just as easily be able to create an organisation with one member. :-)
Ultimately: Don't Panic! No (or little) action is necessary. You'll still be signing in as a user as you've always done.
For any questions or concerns, please contact us; we'll be happy to help, and put your mind at ease!Read More
With Cloudsmith, users have the choice to store their assets where they want, whether it's for compliance purposes or to keep them close to your users for maximum performance. We've rolled out two new US regions to give you even more choice: Ohio and Oregon. Try them out today when creating your new repositories, or transfer an existing repository to one of the new regions. If you've already transferred your repository previously, you'll need to contact us to reset it before you can transfer again (but it'll be quick and painless).Read More
Thanks for subscribing!
Check your inbox to verify your email