Operating System CentOS

Laravel GitScrum on AlmaLinux 9: Project Status and Maintained Alternatives

The open-source Laravel GitScrum code has been unsupported since 2017. Here is what it requires, why it does not fit the RHEL 9 family, and what to use instead.

If you are looking for a way to install Laravel GitScrum on a current server, the honest answer is that you should not deploy it for real work. The open-source Laravel GitScrum code is abandoned, it was written for PHP 7.1 and Laravel 5.5, and neither is available in a supported form on AlmaLinux 9, Rocky Linux 9 or CentOS Stream 9. This page explains the project's status, what the code really requires, how to look at it in a throwaway environment if you must, and which maintained self-hosted tools cover the same ground.

Older tutorials on this topic targeted CentOS 7. That release reached end of life on 30 June 2024; the RHEL 9 family named above is what replaces it.

Project status

The repository still exists and now lives under the gitscrum-core organisation on GitHub (the old GitScrum-Community address redirects there). It is not formally archived, but its own README is clear about what it is: "the first code of the GitScrum application developed in 2016 and supported until 2017". The README sends anyone who wants the current GitScrum to the company's website, where GitScrum is offered as a hosted commercial product rather than as this code base.

Other signs point the same way:

  • The newest tag in the repository is 1.1.0, and the newest version published on Packagist dates from January 2017.
  • Commits in recent years only touch the README and repository metadata, not the application.
  • There is no release that supports PHP 8.

What the code actually requires

These values come from the project's README and composer.json:

ComponentRequirement
PHP7.1 or newer (written and tested in the PHP 7 era)
FrameworkLaravel 5.5
DatabaseMySQL or MariaDB
Web serverNginx or Apache
LoginAn OAuth application on GitHub, GitLab or Bitbucket; the keys go into .env

Laravel 5.5 was a long-term support release that received security fixes for three years after its 2017 release, so the framework underneath the application has been unpatched for years. The pinned dependencies are equally old.

Why it does not fit AlmaLinux 9 or Rocky Linux 9

The RHEL 9 family ships PHP 8.0 by default and offers 8.1, 8.2 and 8.3 as module streams. There is no PHP 7 in the distribution, and PHP 7 itself is end of life upstream. Running this application would mean adding an unsupported PHP 7 build from a third-party repository, installing an unpatched framework, and exposing a login page to the internet on top of both. Its sign-in also depends on OAuth integrations written in 2017 against provider APIs that have changed since.

For those reasons this page does not give a production installation procedure. Anything presented as one would be guesswork.

If you only need to look at the old code

To evaluate the application or recover data from an old instance, use a disposable virtual machine or container that is not reachable from the internet, with PHP 7.x, Composer and MariaDB inside it. The README documents this procedure, reproduced here in the order it gives:

git clone https://github.com/gitscrum-core/laravel-gitscrum.git
cd laravel-gitscrum
composer update
composer run-script post-root-package-install

Create an empty database, then edit .env and fill in APP_URL, the DB_HOST, DB_DATABASE, DB_USERNAME and DB_PASSWORD values, and the OAuth keys for the provider you use (GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET, or the GitLab or Bitbucket equivalents). Then create the tables and default settings:

php artisan migrate
php artisan db:seed --class=SettingSeeder

Expect dependency resolution problems: composer update has to find 2017-era packages that still install on your PHP 7 build, and some may no longer resolve. The README also links a separate Docker setup by the original author built on PHP 7 and MySQL 5.7 images, which is just as old.

Maintained self-hosted alternatives

All of the following are open-source projects with releases in the last few months of 2026. Pick by how much process you need:

ToolGood fit whenHow it is deployed
OpenProjectYou want full Scrum support: backlogs, sprints, task boards, plus classic project planningDocker is the recommended method; RPM packages exist for RHEL 9 and CentOS Stream 9 but are being phased out for newer distributions
PlaneYou want a modern issue tracker with sprint-style cyclesDocker containers
LeantimeYou want a PHP and MySQL application, close to the stack older tutorials builtStandard PHP web application or Docker
KanboardYou only need a simple Kanban boardSmall PHP application

OpenProject's packaged installation documents a minimum of a quad-core CPU, 4 GB of memory and 20 GB of disk for up to 200 users, which is far more than the 1 GB the old GitScrum guide suggested. Kanboard and Leantime are comfortable on a small VPS. Read each project's own installation guide before you choose; start with the OpenProject installation documentation if Scrum is the priority.

If your team already works in GitHub or GitLab, also check whether their built-in boards, milestones and iterations are enough. The original appeal of GitScrum was tying Scrum artefacts to Git hosting, and both platforms now do that natively.

Moving off an existing GitScrum instance

There is no export tool. What you can do:

  • Dump the database with mysqldump (or mariadb-dump) and keep it with the .env file and the storage directory as an archive.
  • Recreate open user stories and issues in the new tool. Check whether the tool you chose imports CSV files; if it does, a SQL query that exports the issues table to CSV is usually the quickest route.
  • Take the old instance off the public internet as soon as the data is copied.

Frequently asked questions

Is GitScrum itself dead?

No. GitScrum continues as a hosted commercial service. What is discontinued is the open-source Laravel code base from 2016 and 2017 that older tutorials installed.

Can I make the old code run on PHP 8?

Not without porting it. You would have to upgrade Laravel across many major versions and replace abandoned dependencies, which is more work than adopting a maintained tool.

Is there a maintained fork?

None is referenced by the project, and the upstream repository lists no successor for the open-source edition. Treat any fork you find with the same caution and check its commit history and PHP requirements first.

Share story:

Continue reading other guides on How VPS.