LogoLogo
  • OnePub
  • Guides
    • Installing
      • Install CLI tools
      • Register
      • Invite a member
      • Accept an Invite
      • CLI integration
        • Manually add publish_to
        • Implicit Integration
      • IDE integration
        • Android Studio
        • Visual Studio Code
      • Pre Dart 2.15
      • Pre Dart 2.12
    • Searching
    • Watching packages
    • Publishing Packages
      • The hard way
    • Private dependencies
      • The hard way
    • CLI Tools
      • login
      • logout
      • doctor
      • export
      • import
      • pub add
      • pub private
      • pub global activate
      • pub global deactivate
    • CI/CD
    • SSH
    • Docker
    • Community Choice Awards
  • Fundamentals
    • Members
    • Teams
    • Roles
    • Naming Packages
  • Workflows
    • Distributing to Customers
      • Purchase a Customer Distribution License
      • Security considerations
      • Publish a package
      • Invite a customer
      • Customer installation instructions
      • Conditions Apply
    • For Support
    • Setting up CI/CD
    • Vendoring Dependencies
    • Switching Organisations
    • Creating a Team Leader
  • FAQ
    • Is GST/VAT/Sales Tax applicable?
    • Does OnePub.dev have access to my personal information?
    • What is your SLA?
    • How do I get support?
    • How do I use OnePub from my CI/CD environment?
    • How to invite team members to join OnePub
    • How to publish a private package
    • 401: Unauthorized
  • Solved by OnePub
  • Data Retention Policy
  • Payments
Powered by GitBook
On this page

Was this helpful?

  1. Workflows

Distributing to Customers

PreviousNaming PackagesNextPurchase a Customer Distribution License

Last updated 2 years ago

Was this helpful?

OnePub can be used as a safe and easy method to distribute licensed packages to your customers.

Customers are given limited 'read only' access which allows them to:

  • to add a dependency to your private package(s) published via OnePub

  • participate in the OnePub discussion threads for your package.

  • view your package's; readme, changelog, install instruction, version history and dependency chart

  • Add 'package watches' to receive a notification whenever you publish a new version of a package.

You can control what packages a Customer has access to by creating Teams and allocating packages/customers to the team. A customer will only see packages from the teams that they are members of.

Your customer will have full access to the package's source code!

The package source will be stored in their .pub-cache folder.

The following guides are provide to help you get setup.

  • Set up Customer Teams

  • Customer installation instructions

Purchase a Distribution license
Publish a package
Invite a customers
Conditions Apply