12/8/2023 0 Comments Modmore gitify![]() Just pull in the latest changes, rerun composer in case anything changed with regards to the dependencies, and off you go. Maybe a way to force re-installation of packages, something like Gitify package:reinstall -all.Ĭurrently when this happens, an admin has to manually hit the reinstall button in the MODX packages-grid, possibly on all packages, and then Gitify extract afterwards to have everything back in sync. If you followed the procedure to install Gitify from Git, updating Gitify to a newer version is as simple as pulling in the recent changes.Maybe a new way of upgrading through Gitify, so already locked package-versions get installed and also dumped back to the gitify-config, something like Gitify package:upgrade -all.That way if the admin uses the MODX package-grid to reinstall/update packages, it can automatically be locked back to the config, something like Gitify package:dump -all or Gitify package:save -all. A way of dumping currently installed package-versions back to the gitify-config.The InstallPackageCommand needs to acknowledge this and get the specified version. So the user should be able to provide an exact version in the gitify-config, like colorpicker-1.0.3-pl. That way installing on a new environment gives the user the exact versions used before. Gitify needs to be locked down on package-versions.Possible solutions / ideas / additions to Gitify Expected behaviorĭon't loose stuff in between environment setups, and be confident everything works as expected. Gitify extract and you see the "lost data" or new and not yet gitified data. ![]() Then in the packages grid, reinstall an extra you are sure got updated. It's also possible to install Gitify into your project files (as git submodule - tho we might add it to composer later), so you have a copy of Gitify local to the project, but then you lose the. ![]() After that, run Composer to download the dependencies, and finally make the Gitify file executable to run it. Remember to update all your Gitify installs (local, staging and production) as close to each other as possible to be safe from changes between versions. ![]() And also new stuff gets killed, because it's not gitified yet. To get started with Gitify, it's easiest to set up a local clone of this repository. my gitified old snippets (and other stuff) overwrite the newly ones. there are new updates to packages and new settings/plugins/snippets get installed to the DB.Īlso already gitified snippets, like lets say "ImagePlus", get updates. My "Gitify-process" on initial setup in an environment looks like this: Now when pushing to my production-environment it might install other versions of packages than used before, because let's say FormIt just released an update. I'm using Gitify for handling environments and also new setups (by cloning/copying an old project). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |