Package, dependency and environment management for any language - Python, R, Ruby, Lua, Scala, Java, JavaScript, C/ C++, FORTRAN, and more. Cloudsmith is fully compatible as a conda repository/channel.

The following instructions are for Conda or compatible packages only.

Adding a new channel can be accomplished by using the conda CLI:

conda config --add channels https://conda.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/

channels:
  - https://conda.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/
  - defaults

name: env-name
channels:
  - https://conda.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/
  - defaults
dependencies:
  - python=3.7
  - codecov

Once configured, you can install packages from your channel using the conda CLI:

conda install your-package=1.2.3

Note: You'll need to replace your-package and 1.2.3 with your own awesome Conda packages and versions.

If necessary, you can explicitly declare the channel from which to install:

conda install your-package=1.2.3 -c https://conda.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/

Note: You'll need to replace your-package and 1.2.3 with your own awesome Conda packages and versions.

If you couldn't find what you needed in our documentation, then you can always chat to a member of our team instead. It's our mission to be your dedicated off-site team for package management, and we mean it. Come and chat with us, anytime.

Npm is the package manager of choice for the Javascript/Node ecosystem. Cloudsmith is fully compatible as an npmjs-like registry.

The following instructions are for npm or compatible packages only.

There are two ways to tell npm to use a Cloudsmith-based npm registry:

1. Set the registry as the default globally, per-user or per-project.
2. Provide the registry URL when executing npm commands.

To use/set the registry as the default for your user, execute the following:

npm config set registry https://npm.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/

You can set it globally (with permissions) by using the -g argument.

Alternatively, you can add it directly to your user or project .npmrc file:

registry=https://npm.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/

Note: Setting the registry globally will impact all npm commands, unless they explicitly override the registry.

You can specify the registry each time you execute npm commands, such as:

npm install lodash --registry=https://npm.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/

For a public registry, you do not provide authentication for read-only contexts, such as installing packages:

npm install awesome-package

You can namespace your registry and packages using npm scopes.

Using a registry scope tells npm to route installs for packages in that scope to Cloudsmith.

You can set it via the command-line using:

npm config set '@cloudsmith:registry' https://npm.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/

You can also set it directly in your user or project .npmrc file:

@cloudsmith:registry=https://npm.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/

Note: You should replace @cloudsmith in the above with your own scope name.

Using a package scope provides a different namespace to other similarly named packages to differentiate them.

Installing packages with a scope requires putting the scope before the name:

npm install @cloudsmith/awesome-package

You can find out more about scoped packages (on npmjs.com).

Note: You should replace @cloudsmith in the above with your own scope name.

Distribution tags allow npm packages to be tagged with a mnemonic that is associated with a specific package version.

These can be used as an alternative to the package version when installing packages, such as:

npm install awesome-package@beta --registry=https://npm.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/

Cloudsmith has full support for distribution tags and (mostly) follows the same rules for them as on npmjs.com:

1. A specific tag can point at one version of a package only.
2. A package version may have multiple unique tags.
3. Unless specified otherwise, the default tag for the last package published is latest.
4. When a package that is latest is deleted, the tag is moved to the next applicable version by semver.

Note: If the repository is configured so that upstream npm tags take precedence, tags from configured upstreams will override matching local tags. When both upstream and local repositories have the same tag name (e.g., latest), the upstream tag will be used instead of the local one, even if the local repository has a semantically higher version.

You can inspect a package to see what tags it has:

npm dist-tags ls awesome-package --registry=https://npm.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/
(out)latest: 1.0.0
(out)beta: 2.0.0

You can find out more about distribution tags (on npmjs.com).

Cloudsmith supports transparent proxying of install requests to/from npmjs.com.

When enabled, requests for packages that don't exist in the registry will be automatically proxied:

npm install lodash@4.17.11 --registry='https://npm.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/'
(out)+ lodash@4.17.11
(out)updated 1 package in 2.743s

In this case, lodash didn't exist in the registry and was proxied. This also applies automatically when npm is installing dependencies for your package. It will load them from the registry automatically and transparently proxy them.

Warning: If transparent upstream proxying is disabled for the registry then you will need to fetch all dependencies of your packages manually. These can then be published into the registry, or you can bundle them with bundleDependencies.

Cloudsmith supports proxying of npm audit requests to detect vulnerabilities in dependencies:

npm audit
(out)                       === npm audit security report ===
(out)found 0 vulnerabilities
(out) in 1 scanned package

You can find out more about security auditing (on npmjs.com).

Assuming that you have always-auth enabled, Yarn is immediately compatible with Cloudsmith registries:

yarn add lodash@4.17.11 --registry=https://npm.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/
(out)[1/5] Validating package.json...
(out)[2/5] Resolving packages...
(out)[3/5] Fetching packages...
(out)[4/5] Linking dependencies...
(out)[5/5] Building fresh packages...
(out)success Saved lockfile.
(out)success Saved 1 new dependency.
(out)info Direct dependencies
(out)└ lodash@4.17.11
(out)info All dependencies
(out)└ lodash@4.17.11

To enable always-auth, add it to your user or project .npmrc file:

always-auth

If you couldn't find what you needed in our documentation, then you can always chat to a member of our team instead. It's our mission to be your dedicated off-site team for package management, and we mean it. Come and chat with us, anytime.

NuGet is the package manager of choice within the .NET development platform.

The following instructions are for NuGet or compatible packages only.

As explained by nuget.org: "NuGet is the package manager for .NET. The NuGet client tools provide the ability to produce and consume packages. The NuGet Gallery is the central package repository used by all package authors and consumers."

To consume packages in NuGet from this Feed, you'll need to configure it as a source.

• Chocolatey
• NuGet CLI
• .NET Core CLI
• Paket CLI
• PowerShell
• VS Package Manager (PM)

choco source add -n seowebchecker-seowebchecker-seoaudit-sdk -s https://nuget.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/v2/

nuget sources add -Name seowebchecker-seowebchecker-seoaudit-sdk -Source https://nuget.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/v3/index.json

dotnet nuget add source --name seowebchecker-seowebchecker-seoaudit-sdk https://nuget.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/v3/index.json

source https://nuget.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/v3/index.json

Register-PackageSource -Name 'seowebchecker-seowebchecker-seoaudit-sdk' -Location 'https://nuget.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/v2/' -Trusted
Register-PSRepository -Name 'seowebchecker-seowebchecker-seoaudit-sdk' -SourceLocation 'https://nuget.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/v2/' -InstallationPolicy 'trusted'

https://nuget.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/v3/index.json

You can install NuGet packages using the following commands:

• Chocolatey
• NuGet CLI
• .NET Core CLI
• Paket CLI
• PowerShell
• VS Package Manager (PM)

choco install Your.Package -s seowebchecker-seowebchecker-seoaudit-sdk --version 1.2.3

nuget install Your.Package -Version 1.2.3 -Source seowebchecker-seowebchecker-seoaudit-sdk

dotnet add package Your.Package -v 1.2.3 -s https://nuget.cloudsmith.io/seowebchecker/seowebchecker-seoaudit-sdk/v3/index.json

paket add nuget Your.Package -v 1.2.3

Install-Package -Name 'Your.Package' -RequiredVersion '1.2.3' -Source 'seowebchecker-seowebchecker-seoaudit-sdk'

Install-Module -Name 'Your.Package' -RequiredVersion '1.2.3' -Repository 'seowebchecker-seowebchecker-seoaudit-sdk'

Install-Script -Name 'Your.Package.ps1' -RequiredVersion '1.2.3' -Repository 'seowebchecker-seowebchecker-seoaudit-sdk'

Install-Package Your.Package -Version 1.2.3 -Source seowebchecker-seowebchecker-seoaudit-sdk

Note: You should replace Your.Package and 1.2.3 with your own package name and version.

If you couldn't find what you needed in our documentation, then you can always chat to a member of our team instead. It's our mission to be your dedicated off-site team for package management, and we mean it. Come and chat with us, anytime.

Pip/Pipenv/Poetry are package managers of choice for the Python ecosystem. Cloudsmith is fully compatible as a PyPi-like repository.

The following instructions are for Python or compatible packages only.

You can install packages directly by using the --index-url or --extra-index-url Pip configuration arguments when executing a pip command.

Note: We recommend using --index-url. As per pip's documentation: Using the --extra-index-url option to search for packages that are not in this repository (such as private packages) is unsafe, per a security vulnerability called dependency confusion: an attacker can claim the package on the public repository in a way that will ensure it gets chosen over the private package. For more detail, see our expanded documentation on the usage and dangers of extra index URL.

pip install my-awesome-package==1.0.0 --index-url https://dl.cloudsmith.io/public/seowebchecker/seowebchecker-seoaudit-sdk/python/simple/

Note: You'll need to replace my-awesome-package and 1.0.0 with your own awesome python packages and versions.

Similar to setup via command-line, pip needs to be passed the --index-url configuration option. To do this add --index-url to the top of your requirements.txt (or similar) file.

--index-url https://dl.cloudsmith.io/public/seowebchecker/seowebchecker-seoaudit-sdk/python/simple/
my-awesome-package==1.0.0

Note: You'll need to replace my-awesome-package and 1.0.0 with your own awesome python packages and versions.

Remove the following line from your $HOME/.pip/pip.conf file:

--index-url=https://dl.cloudsmith.io/public/seowebchecker/seowebchecker-seoaudit-sdk/python/simple/

If you couldn't find what you needed in our documentation, then you can always chat to a member of our team instead. It's our mission to be your dedicated off-site team for package management, and we mean it. Come and chat with us, anytime.

Rubygems/bundler are the package managers of choice for the Ruby ecosystem. Cloudsmith is fully compatible as a Rubygems-like repository.

The following instructions are for Ruby or compatible packages only.

As stated by Bundler, "Bundler provides a consistent environment for Ruby projects by tracking and installing the exact gems and versions that are needed."

Bundler from version 1.7 supports scoped sources, so you can install a gem from Cloudsmith using the following declaration in your Gemfile:

source 'https://dl.cloudsmith.io/public/seowebchecker/seowebchecker-seoaudit-sdk/ruby/' do
  gem 'awesome-gem', '~> 42.0'
end

Note: You'll need to replace awesome-gem and ~> 42.0 with your own gem name and version.

You can also add Cloudsmith as a source for the Ruby CLI instead:

gem sources --add 'https://dl.cloudsmith.io/public/seowebchecker/seowebchecker-seoaudit-sdk/ruby/'

gem sources -r 'https://dl.cloudsmith.io/public/seowebchecker/seowebchecker-seoaudit-sdk/ruby/'

If you couldn't find what you needed in our documentation, then you can always chat to a member of our team instead. It's our mission to be your dedicated off-site team for package management, and we mean it. Come and chat with us, anytime.