Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to run a MODX upgrade #7

Closed
Mark-H opened this issue Sep 11, 2014 · 6 comments
Closed

Ability to run a MODX upgrade #7

Mark-H opened this issue Sep 11, 2014 · 6 comments

Comments

@Mark-H
Copy link
Member

Mark-H commented Sep 11, 2014

The .gitify could contain a modx_version (or just version) key that contains the MODX version that it is expected to run. Then with a Gitify build or Gitify update-modx [version] it could grab that specific version and run the command line upgrade.

@bequadrat
Copy link

👍

@isaacniebeling
Copy link
Contributor

Maybe version could take a few forms:

  • nightly -- the newest nightly
  • stable -- the newest stable version
  • previous -- one version back (this could be useful for companies that have a "one version prior" IT policy. Not that I agree with it, just that it'd be fairly straightforward to code for.)
  • 2.3.1 -- a specific version
  • 2.3.x (or 2.3) -- the latest minor version -- if someone wanted the last 2.2 version, for example. Not a huge deal at this point, but probably useful for a little while when 2.4 comes out.

@alroniks
Copy link
Collaborator

alroniks commented Oct 1, 2014

@isaacniebeling +1. Good suggestion

@adamwintle
Copy link

👍 for this too, installing an older version would be very useful

@alroniks
Copy link
Collaborator

alroniks commented Nov 4, 2015

I think it can be closed, because described functions already works.

@Mark-H
Copy link
Member Author

Mark-H commented Nov 4, 2015

Yep, was added in #116 :)

@Mark-H Mark-H closed this as completed Nov 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants