LocalGov Drupal Docs
Overview
  • Developers
  • Content designers
  • Designers
  • Contributing
  • Credits System
  • Accessibility
  • Governance
Microsites
Main site
GitHub
Overview
  • Developers
  • Content designers
  • Designers
  • Contributing
  • Credits System
  • Accessibility
  • Governance
Microsites
Main site
GitHub
  • For Developers
  • Getting started
    • Drupal requirements
    • Working with Lando
    • Working with DDEV
    • Debugging with Xdebug
    • Working with Gitpod
  • General configuration
    • Content types
    • Custom modules
    • Image styles
    • Media types
    • Paragraph types
    • Taxonomies
    • User roles
  • Features
    • Services: Technical
    • Alert banners: Technical
    • News: Technical
    • Directories: Technical
    • Location Geo: Technical
    • Subsites: Technical
    • Workflows: Technical
  • Theme
    • LocalGov Base
    • Regions
    • LocalGov Theme (Deprecated)
    • Skeleton theme (Deprecated)
    • Admin theme (Deprecated)
  • Testing
  • Development workflows
    • Installing and deploying a LocalGov Drupal site
  • Hosting
    • Hosting a LocalGov Drupal site
      • Development site
      • Staging site
      • Production site
      • Hosting providors and options
    • Hosting LocalGov Drupal on Azure
  • Release statuses
    • Release statuses
  • Security
    • Best practice guidance
    • Single Sign-On
  • Quality standards
    • Quality standards: Accessibility
    • Quality standard: Documentation
    • Quality standard: Testing
  • How-tos
    • How to use Gitpod to test modules in the browser

Hosting a LocalGov Drupal site

There are many options for hosting a Drupal wesite and a LocalGov Drupal site is generally no different.

For most council sites, it is considered best practice to have a three tiered approach for your website.

  • Development site
  • Staging / testing site
  • Production site

Most developers prefer to work on their local computers in a development environment that closely matches the production site environment, with the same versions of webserver, PHP, MySQL etc. Often Lando or DDEV will be used on the developer's local machine to work in Docker containers, before deploying changes to dev / staging / production sites.

Development site

This is where developers can deploy changes to code and configuration to review the functionality and styling of the site and resolve any bugs before deploying to the staging site for acceptance testing.

Staging site

Once work is reaady to be deployed the developers and wider team use the staging site to test the deployment against a copy of the production database and files. Ideally the staging site should be identical to the produciton site with any additional performance and security configurations to support full testing.

Production site

This is the live public facing site where content designers manage live content and the public can access and interact with the content and funcionality.

Hosting providors and options

Councils hosting with LocalGov Drupal use a range of providors and hosting technologies and we are not in a position to recommend one over another. We'd recommend talking to other councils about their experience hosting LocalGov Drupal.

Croydon Council

Croydon Council manage their hosting on the Microsoft Azure platform. There is some usful discussion of that on this Github issue: https://github.com/localgovdrupal/localgov/issues/497

Brighton and Hove City Council

Brighton and Hove City Council use the Acquia Cloud platform to host their main public facing site.

How does your council host LocalGov Drupal?

Please feel free to edit this page and add details of the hosting setup at your council, it is useful for new councils to see the range of approaches.

Help us improve this page!
Last Updated: 9/3/2024, 9:03:17 AM
Prev
Development workflows
Next
Release statuses