Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/city-of-helsinki/drupal-employment-services
Online service for employment services
https://github.com/city-of-helsinki/drupal-employment-services
Last synced: about 1 month ago
JSON representation
Online service for employment services
- Host: GitHub
- URL: https://github.com/city-of-helsinki/drupal-employment-services
- Owner: City-of-Helsinki
- Created: 2020-11-09T13:03:26.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2024-06-12T04:49:47.000Z (6 months ago)
- Last Synced: 2024-06-12T15:18:15.641Z (6 months ago)
- Language: PHP
- Size: 3.41 MB
- Stars: 1
- Watchers: 7
- Forks: 3
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Työllisyyspalvelut Helsinki Drupal 9 site
Drupal 9 website for the Työllisyyspalvelut Helsinki project.
## Related repositories
- [Employment services content sync](https://github.com/City-of-Helsinki/employment-services-content-sync)
- [React UI](https://github.com/City-of-Helsinki/employment-services-ui)
## Environments
Env | Branch | Drush alias | URL | Notes
--- | ------ | ----------- | --- | -----
development | develop | - | https://drupal-tyollisyyspalvelut-helfi.docker.so | Local development environment
production | main | - | https://edit.tyollisyyspalvelut.hel.fi | Production site
## Requirements
You need to have these applications installed to operate on all environments:
- [Docker](https://github.com/druidfi/guidelines/blob/master/docs/docker.md)
- [Stonehenge](https://github.com/druidfi/stonehenge)
- For the new person: Your SSH public key needs to be added to servers
## Create and start the environment
For the first time (new project):
``
$ make new
``
Stop project:
``
$ make stop
``
Start project after stopping it:
``
$ make up
``
Stop project and remove containers:
``
$ make down
``
Start project, rebuild and update configuration:
``
$ make up; make build; make post-install
``
Install fresh Drupal site from existing configuration:
``
$ make build; make drush-si; make post-install
``
Start project, update all packages and sync db from local sql dump:
``
$ make fresh
``
## Update Drupal and composer modules
Install all modules and composer packages:
``
$ make build
``
Update all modules and composer packages:
``
$ make composer-update
``
Update only Drupal core:
``
$ make drupal-update
``
**Note:** After updates, clear caches, run database updates and export possibly changed configuration:
``
$ make drush-cr; make drush-updb; make drush-cex
``
Update Composer.lock if outdated (after merges, etc):
```
# Login into app container first:
$ make shell
# Update lock file:
$ composer update --lock
```
## Configuration management
Export settings:
``
$ make drush-cex
``
Import settings:
``
$ make drush-cim
``
## Other useful commands
```
# Login to app container:
$ make shell
# Login with Drush
$ make drush-uli
# Create sql dump from local site
$ make drush-create-dump
# Run database updates, config import, clear caches.
$ make drush-deploy
# Check Drupal coding style
$ make lint-drupal
# Automatically fix Drupal coding style errors
$ make fix-drupal
```
### Coding standards
Follow Drupal's coding standards: https://www.drupal.org/docs/develop/standards
City of Helsinki's coding standars and best practices: https://dev.hel.fi/
Check for coding style violantions by running `$ make lint-drupal`
### Gitflow workflow
The Gitflow workflow is followed, with the following conventions:
**Main branch**: `develop`. All feature branches are created from `develop` and merged back with pull requests. All new code must be added with pull requests, not committed directly.
**Production branch:** `main`. Code running in production. Code is merged to `main` with release and hotfix branches.
**Feature branches**: For example, `TH-add-content-type`, Always created from and merged back to `develop` with pull requests after code review and testing.
**Release branches**: Code for future and currently developed releases. Should include the version number, for example: `1.1.0`
**Hotfix branches**: Branches for small fixes to production code. Should include the word hotfix, for example: `TH-hotfix-drupal-updates`. Remember to also merge these back to `develop`.