{"id":23561964,"url":"https://github.com/jfeltkamp/argue-project","last_synced_at":"2026-05-05T13:40:26.570Z","repository":{"id":56998613,"uuid":"103842158","full_name":"jfeltkamp/argue-project","owner":"jfeltkamp","description":"Drupal-composer project template","archived":false,"fork":false,"pushed_at":"2022-07-08T18:35:37.000Z","size":18,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"2.0.x","last_synced_at":"2025-02-17T15:51:55.758Z","etag":null,"topics":["composer","drupal","php"],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/jfeltkamp.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2017-09-17T16:05:15.000Z","updated_at":"2022-07-17T17:39:53.000Z","dependencies_parsed_at":"2022-08-21T14:50:25.099Z","dependency_job_id":null,"html_url":"https://github.com/jfeltkamp/argue-project","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jfeltkamp%2Fargue-project","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jfeltkamp%2Fargue-project/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jfeltkamp%2Fargue-project/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jfeltkamp%2Fargue-project/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/jfeltkamp","download_url":"https://codeload.github.com/jfeltkamp/argue-project/tar.gz/refs/heads/2.0.x","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254455668,"owners_count":22074028,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["composer","drupal","php"],"created_at":"2024-12-26T16:14:33.715Z","updated_at":"2026-05-05T13:40:21.545Z","avatar_url":"https://github.com/jfeltkamp.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Composer template for Drupal Argue projects\n\nThis project template should provide a kickstart for managing your site\ndependencies with [Composer](https://getcomposer.org/).\n\n## Usage\n\nFirst you need to install [Composer](https://getcomposer.org/doc/00-intro.md#installation-linux-unix-osx) and [Git](https://git-scm.com).\n\n\u003e Note: The instructions below refer to the [global composer installation](https://getcomposer.org/doc/00-intro.md#globally).\nYou might need to replace `composer` with `php composer.phar` (or similar) \nfor your setup.\n\nAfter that you can create the project:\n\n```\ncomposer create-project jfeltkamp/argue-project -s dev argue\n```\n\nThe `composer create-project` command passes ownership of all files to the \nproject that is created. You should create a new git repository, and commit \nall files not excluded by the .gitignore file.\n\n## What does the template do?\n\nWhen installing the given `composer.json` some tasks are taken care of:\n\n* Drupal will be installed in the `docroot`-directory.\n* Autoloader is implemented to use the generated composer autoloader in `vendor/autoload.php`,\n  instead of the one provided by Drupal (`docroot/vendor/autoload.php`).\n* Modules (packages of type `drupal-module`) will be placed in `docroot/modules/contrib/`\n* Theme (packages of type `drupal-theme`) will be placed in `docroot/themes/contrib/`\n* Profiles (packages of type `drupal-profile`) will be placed in `docroot/profiles/contrib/`\n* Downloads Drupal scaffold files such as `index.php`, or `.htaccess`\n* Creates `sites/default/files`-directory.\n* Latest version of drush is installed locally for use at `bin/drush`.\n* Latest version of DrupalConsole is installed locally for use at `bin/drupal`.\n\n## Installing Argue\n\nCreate project will install Argue into the docroot direcrory inside of Argue. You can now install Argue as you would with any Drupal 9 site. See: [Drupal installation guide](https://www.drupal.org/node/1839310).\n \n## Updating Argue\n\nTo update Argue, Drupal or any module to the newest version, constrained by the specified version in `composer.json`, execute `composer update`. This command will check every dependency for a new version, downloads it and updates the `composer.lock` accordingly.\nAfter that you can run `drush updb` in the docroot folder to update the database of your site.\n\n### File update\n\nThis project will attempt to keep all of your Argue and drupal core files up-to-date; the \nproject [drupal/core-dev](https://github.com/drupal-composer/drupal-scaffold) \nis used to ensure that your scaffold files are updated every time drupal/core is \nupdated. If you customize any of the \"scaffolding\" files (commonly .htaccess), \nyou may need to merge conflicts if any of your modfied files are updated in a \nnew release of Drupal core.\n\nFollow the steps below to update your Argue files.\n\n1. Run `composer update drupal/argue`\n1. Run `git diff` to determine if any of the scaffolding files have changed. \n   Review the files for any changes and restore any customizations to \n  `.htaccess` or `robots.txt`.\n1. Commit everything all together in a single commit, so `web` will remain in\n   sync with the `core` when checking out branches or running `git bisect`.\n1. In the event that there are non-trivial conflicts in step 2, you may wish \n   to perform these steps on a branch, and use `git merge` to combine the \n   updated core files with your customized files. This facilitates the use \n   of a [three-way merge tool such as kdiff3](http://www.gitshah.com/2010/12/how-to-setup-kdiff-as-diff-tool-for-git.html). This setup is not necessary if your changes are simple; \n   keeping all of your modifications at the beginning or end of the file is a \n   good strategy to keep merges easy.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjfeltkamp%2Fargue-project","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjfeltkamp%2Fargue-project","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjfeltkamp%2Fargue-project/lists"}