https://github.com/fourkitchens/sous-drupal-distro
A base Drupal distribution profile with a theme based on Emulsify Design System
https://github.com/fourkitchens/sous-drupal-distro
Last synced: 9 months ago
JSON representation
A base Drupal distribution profile with a theme based on Emulsify Design System
- Host: GitHub
- URL: https://github.com/fourkitchens/sous-drupal-distro
- Owner: fourkitchens
- License: mit
- Archived: true
- Created: 2019-10-04T19:14:57.000Z (over 6 years ago)
- Default Branch: main
- Last Pushed: 2024-04-18T19:26:21.000Z (about 2 years ago)
- Last Synced: 2025-03-15T06:31:38.611Z (over 1 year ago)
- Language: CSS
- Homepage:
- Size: 1.52 MB
- Stars: 6
- Watchers: 15
- Forks: 1
- Open Issues: 15
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Sous Distribution Package
A base Drupal distribution profile with a theme based on Emulsify Design System.
## Install and Use
Follow the documentation found on the [Sous Drupal project](https://github.com/fourkitchens/sous-drupal-project) page.
## Contributing
1. Clone this project, create a new branch make your change and push the branch.
2. In another directory, clone the [sous-drupal-project](https://github.com/fourkitchens/sous-drupal-project) repo.
3. Change the `"fourkitchens/sous-drupal-distro": "dev-4.x",` (located in the `composer.json`) line to match the name of the branch you wish to test or change into the `web/profiles/contrib/sous/` directory and checkout the branch you are looking for if you have already setup the project.
4. `composer install`, if you have already run `composer install` then -> `composer update fourkitchens/sous-drupal-distro`
5. `lando start`
6. Open the url that lando prints
7. Follow the setup instructions
8. Database connection information can be found with `lando info` in the database section.
9. Finish setup and test as appropriate.
## Semantic Versioning
## Setup
1. This repo has the following named/maintenance branches:
```
master
x.x
x.x.x
```
2. These branches are protected on GitHub
3. A personal access token was created for CircleCI.
4. CircleCI was setup to run on this project and tag the releases
5. Commit changes following the [Conventional commit guidelines](https://www.conventionalcommits.org/en/v1.0.0/)
6. Push your change up and verify CircleCI passes and has run on your desired branch.
## Troubleshooting
1. Your branch must be a named stable release branch in order to get a tag.
2. Prereleases are not supported with this package because they contain a dot.