cividesk/civicrm

There is no license information available for the latest version (6.5.x-dev) of this package.

CiviCRM platform for Cividesk.

Maintainers

Package info

gitlab.com/cividesk/platform/civicrm

Issues

pkg:composer/cividesk/civicrm

Transparency log

Statistics

Installs: 3 257

Dependents: 0

Suggesters: 0

Stars: 0

Security

Advisories: 0

Aikido package health analysis

6.5.x-dev 2026-07-23 11:40 UTC

Requires

Unknown License 95c5feb349cc3252e4ec6ac681247e16e15000e9

Published on Packagist.org on 2026-07-23 11:40 UTC

This package is auto-updated.

Last update: 2026-07-28 02:36:26 UTC

README

Getting started

Drupal 9: with composer

composer require cividesk/civicrm:6.0.x-dev

You can even then remove the `civicrm/civicrm-core`, `civicrm/civicrm-drupal-8andcivicrm/civicrm-packageslines from yourcomposer.jsonfile as these dependencies are already included incividesk/civicrm-patches`.

Wordpress: with composer

composer require cividesk/platform:6.0.x-dev
composer require wpackagist-plugin/civicrm

Add new patches to the build

If the patch is available in a gitlab repository:

  • [ ] download the patch in the patches folder (use the same name as the commit id)
    • the easiest way to download a patch file is to add `.patch` to the end of the URL for the corresponding PR.
    • use the same name as the commit id for the patch file

If you need to create patch an existing filei (ie. CRM/Report/Form.php):

cd {civicrm_root}
cp {file}.php {file}.php.ori
vi {file}.php
diff -Naur {file}.php.ori {file}.php > {patches_dir}/my-new-patch.patch

Then:

  • [ ] edit the `patches/README.md` file to add a comment and instructions about your patch
  • [ ] run `make` and check that all patches apply correctly
  • [ ] run `make release && git status`
  • [ ] check that all looks good (the composer.json should have changed)
  • [ ] commit and push all your changes

Build in Docker Desktop

docker build  --platform linux/amd64 --build-arg BUILD_REGISTRY=registry.gitlab.com/cividesk/registry/ .