PHPackages                             wri/wri-starter-kit - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. wri/wri-starter-kit

ActiveProject[Utility & Helpers](/categories/utility)

wri/wri-starter-kit
===================

Install profile based on drops-8 with Composer on Pantheon.

10.5.0(5mo ago)02.8k↓33.3%2[1 issues](https://github.com/wri/wri-starter-kit/issues)MITPHPPHP ^8.3

Since Mar 17Pushed 5mo agoCompare

[ Source](https://github.com/wri/wri-starter-kit)[ Packagist](https://packagist.org/packages/wri/wri-starter-kit)[ RSS](/packages/wri-wri-starter-kit/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (6)Dependencies (24)Versions (23)Used By (0)

wri-starter-kit
===============

[](#wri-starter-kit)

Starter code for wri sites

Based off of  with some updates to make this install with the wri/wri\_sites [https://github.com/wri/wri\_sites](https://github.com/wri/wri_sites) profile.

To build a new site
-------------------

[](#to-build-a-new-site)

1. Make sure you have all the prerequisites to use the Pantheon build tools, as discussed at

Note that includes each of the following:

- Composer version 2+
- terminus version 3+
- An SSH key on Pantheon's Dashboard (so you can run terminus commands without having to provide a password)
- The terminus build tools plugin

You should also have:

- The ability to create a new repository on Github under the WRI org:
- The ability to create a new Site on Pantheon under the WRI org (on your Pantheon dashboard, use the top-left icon to go to the WRI org and then look for the "Create New Site" button)

2. Make sure you're running composer version 2: `composer self-update --2`, then run this command:

    ```
    COMPOSER_MEMORY_LIMIT=-1 terminus build:project:create --team='8d0668c5-17bd-17c8-6fd2-1e81cddff66f' --org='wri' --visibility='private' --stability='dev'  wri/wri-starter-kit [new-project-name]

    ```

    More info about the build tools and what each section means is available at

    If you run into a memory exhausted error jump down to the "What to do if the build:project command fails - Manual create" section.
3. Enable solr on your new site:

    ```
    terminus solr:enable [new-project-name]

    ```
4. You can now visit your github repo at [https://github.com/wri/\[new-project-name\]](https://github.com/wri/%5Bnew-project-name%5D). That repository will have information on the Pantheon multidev and Circleci configuration in its README.md
5. Rename the master branch to "main" using [https://github.com/wri/\[new-project-name\]/settings](https://github.com/wri/%5Bnew-project-name%5D/settings).
6. There is likely a new branch waiting to be merged that contains the config changes that show up after installing your site. Create a PR for that branch to the `main` branch of your repo.
7. In the PR, if settings.php is contains lines adding connection to a database, remove those changes and push them: `git checkout main web/sites/default/settings.php`
8. Also update the permissions of one of the build files and push that up to the PR: `chmod 755 ./.ci/build/multidev-save`
9. Merge the PR to the "main" branch.

Post-install recommended configuration changes:
-----------------------------------------------

[](#post-install-recommended-configuration-changes)

After initial install, we recommend doing the following:

1. Pull your site from dev -> test -> live so you can start making configuration changes without fear of losing them with new deploys.
2. On live, enable the `wri_package` and `wri_package2` modules.
3. On live, change the user 1 username to something other than "admin" and give it a stronger password.
4. On live, create a homepage `/node/add/homepage`
5. On live, create the Site title, etc at `/admin/config/system/site-information` including linking to the homepage you just created.
6. On live, set up any Languages you'll want to use on the site. The documentation:
7. Export the live configuration back to the codebase using the `config_partial_export` module at `/admin/config/development/configuration/single/config-partial-export`

### What to do if the build:project command fails:

[](#what-to-do-if-the-buildproject-command-fails)

1. Start by trying to delete the site:
2. If that fails, delete the github repo and the pantheon environment manually.
3. Fix the problems that caused the site to fail to build
4. Re-run the `terminus build:project:create`

#### Manual Create:

[](#manual-create)

If the automated tooling hits a memory exhausted error during the profile install we will need to install / wrap up wiring up the build tools by hand.

(These steps assume you already ran `COMPOSER_MEMORY_LIMIT=-1 terminus build:project:create --team='World Resources Institute' --org='wri' --visibility='private' --stability='dev' wri/wri-starter-kit [new-project-name]` and haven't run / changed anything yet.)

##### Building the codebase

[](#building-the-codebase)

1. On your local run `COMPOSER_MEMORY_LIMIT=-1 composer create-project wri/wri-starter-kit [new-project-name]`
    1. This will build out the project on your local (Minus profile install)
2. Run `cd [new-project-name]`
3. Skip this step if not using docksal
    1. Copy the `.docksal/` directory from  and paste it in the project.
    2. Run `fin init`
4. Now run (add `fin if using docksal`): `drush site-install wri_sites --account-mail='' --account-name= --account-pass="