Giter Club home page Giter Club logo

Comments (3)

zaantar avatar zaantar commented on September 25, 2024

@baizmandesign, honestly, I would prefer to keep the version number, to prevent any sort of confusion when working with the plugin ZIP files. AFAIK, this is also standard practice. Is there a particular use case where you'd find this helpful?

If you need to install Toolset CLI programmatically, you can still do it via git clone ... && cd toolset-cli && composer install.

from toolset-cli.

baizmandesign avatar baizmandesign commented on September 25, 2024

@zaantar That totally makes to me. The programmatic use case I was imagining looked like this...

$ wp plugin install --activate plugin1 plugin2 https://somesite.com/plugin3.zip https://github.com/OnTheGoSystems/toolset-cli/releases/latest/download/toolset-cli.zip

Basically, I'm seeking the ability to install the toolset-cli plugin via WP CLI (without knowing the current version).

To me this is a GitHub problem. As you said, and as most developers know, including the version number in the asset is standard. Here it has the unfortunate side effect of rendering the nifty magic URLs useless in practice.

Feel free to close this issue. :-) Thanks again, Jan!

from toolset-cli.

zaantar avatar zaantar commented on September 25, 2024

@baizmandesign I see. Well, for your use case, there are workarounds available, some elegant but more complicated, but some also very simple if you can rely on stuff like curl or jq, like this comment.

For Toolset CLI, specifically, you can do just:

wp plugin install --activate `curl -sL https://api.github.com/repos/OnTheGoSystems/toolset-cli/releases/latest | jq -r '.assets[].browser_download_url'`

and it should always give you the asset from the latest release.

Potential weak points:

  • curl and jq is required
  • I have no idea how this would work under Windows (unless you're using WSL, git-bash or some other cygwin-based environment)
  • Unpredicted behavior if Toolset CLI starts producing multiple assets per release, but we have no plans for that whatsoever.

I hope this will make your work easier, but as you pointed out, this is rather a GitHub-related problem, so I'm closing this issue. :)

from toolset-cli.

Related Issues (15)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.