How to manage OJS with Git?

Software Support
, , ,
2

Hi @benaltair,

There is a topic related to OJS and git: Running production OJS site with Git for Dummies (like me)

  1. Depends on what the purpose is. According to what you’ve described, I don’t think you’d need any additions there.
  2. I’d fork the repo and track own fork, rather than pkp/ojs repo (for the purposes described). Thus, if any changes to the original code needed, it’s possible to keep them on your fork and reapply every time OJS upgrade needed. E.g., on own fork the branch called stable-3_2_1-modified is created, which origins from pkp/ojs repo stable-3_2_1 branch with custom changes. Crucial update for this branch is available → just update the fork and rebase own stable-3_2_1-modified on top of the stable-3_2_1 from pkp/ojs. But I must confess that don’t upgrade via git production instances of OJS.
1 Like