This document is the Terms of Service for the runcommand website, products, and any associated services. It is an agreement between runcommand, LLC ("runcommand") and you, a user of runcommand’s offerings. By using any of runcommand’s offerings, you are bound to this agreement.
runcommand reserves the right to change these Terms of Service at any time with no prior notice. If the changes are substantial, runcommand may take the time to communicate the changes to you. For clarification on finer points of this Terms of Service, please email firstname.lastname@example.org.
Ultimately, runcommand’s goal is to make you and your team as productive as possible with WP-CLI. These Terms of Service do their very best to establish expectations for each of runcommand’s offerings, and keep the relationship healthy for both parties.
All runcommand WP-CLI commands are licensed under the MIT license. These open source licenses grant you certain freedoms as an end user:
- The freedom to run the WP-CLI command as you wish, for any purpose.
- The freedom to study how the WP-CLI command works, and change it so it works as you’d like it to.
- The freedom to redistribute copies of the WP-CLI commands so you can help your neighbor.
- The freedom to distribute copies of your modifications to the WP-CLI commands.
Most commands are freely accessible on Github. Some, including wp profile, wp doctor, and others ("premium commands"), are only available for download after purchase. The distinction of availability is how runcommand can be a viable business while maintaining open source software.
Usage and Updates
Purchasing a premium command entitles you to enhancements, bug fixes, and other updates during the period of your subscription. You’re welcome to use the command on as many WordPress sites as you’d like. Run a hosting company? You’re even welcome to include the command as a part of your production deployment for use by customers. However, making your premium command generally available for public download will violate the terms of your updates and support subscription.
runcommand reserves intellectual and exclusive ownership rights over its products, documentation, and all aspects of its offering. They are provided "as is" without warranty of any kind, expressed or implied. runcommand shall not be liable for any damages, including but not limited to, direct, indirect, special, incidental, or consequential damages or losses that occur out of the use or inability to use its offerings.
Code isn’t useful if you don’t know how to use it. runcommand thinks of support (including quality documentation) as a key ingredient of deploying open source software. Support is only offered to current runcommand customers.
Purchasing an individual premium command entitles you to support for that product specific during the period of your subscription. You may write in to email@example.com with any of the following:
- Bug reports: "I think I’ve found a bug. Here’s a description of the issue I’ve run into. I saw a dog bark but expected to hear a cat meow."
- Feature requests: "It would be really neat if this command could also make my coffee for me."
- Usage questions: "Is it possible for this command to park my Tesla?"
While runcommand will make its best effort to answer your question, we offer no guarantee of an immediate solution. If your question requires changes to the codebase, said change may not happen in your current billing period.
WP-CLI operational support
Purchasing a runcommand plan entitles you to aforementioned support for premium and open commands, as well as WP-CLI operational support. WP-CLI operational support opens the playing field to general questions about solving problems with WP-CLI. If your question is easier to answer with code, runcommand will put together a snippet or pull request for it.
As a non-exhaustive sample of the types of questions you could ask:
- "How can we go about proactively caching remote assets when using the WordPress importer repeatedly?"
- "What do you think of these WP-CLI commands I’m adding to my premium plugin?"
- "On a WordPress multisite install, how can I check which plugins are active on which sites?"
Generally, the more specific the question, the better. Think of these as questions that could be answered in 15 minutes if you knew the right person to ask.
runcommand plans are seat-based (aka mapped to real human beans). Support seats count towards the people on your team writing in to runcommand with questions. Github-based developer seats provide direct access to the runcommand issue backlog, with the ability to more easily request new features and see how the existing backlog is prioritized. One Github-based developer seat may be used for an automated deployment account.
runcommand’s policy is to respect the privacy of all information collected while operating our service.
We use modern best practices (SSL, two-factor authentication, etc.) and good ol’ common sense to ensure you trust us enough to share the details you need to share.
Personally identifiable details such as file paths, server names, and customer information are treated as confidential by default, unless explicitly agreed upon otherwise.