Menu
Symfony Boilerplate LogoSymfony Boilerplate LogoSymfony BoilerplateDocs
GitHub
Symfony Boilerplate LogoSymfony Boilerplate LogoSymfony Boilerplate
  • Docs
  • GitHub
  • Get Started
    • Overview
    • Installation
  • Development Environment
    • Docker Compose
    • Vagrant
    • Housekeeping
  • API
    • Overview
    • Configuration
    • Composer
    • Housekeeping
  • Web Application
    • Overview
    • Configuration
    • Yarn
    • Housekeeping
  • Database
    • ORM
    • Doctrine Migrations
    • Models
    • DAOs
    • Development Data
  • GraphQL
    • Overview
    • API
    • Web Application
    • Tools
  • i18n
    • Default Locale
    • API
    • Web Application
    • API and Web Application Interactions
    • Disable i18n
  • Security
    • Overview
    • Authentication
    • Access Control
    • CORS
  • Files
    • Assets
    • Temporary Files
    • Uploads
  • Validation
    • Overview
    • Models
    • Use Cases
    • GraphQL
    • Forms
  • Lists
    • Overview
    • Database
    • GraphQL
    • Web Application
  • Emails
    • Overview
    • Configuration
    • Send Emails
    • Templates
  • Static Analysis
    • API
    • Web Application
  • Tests
    • API
    • Web Application
  • Theme
    • Customization
    • Layouts
  • Deployments
    • Overview
    • Docker Images
    • CI/CD
    • Run
    • LogRocket
  • CHANGELOG

Overview

In the Get Started chapter, we saw that many layers composes the Symfony Boilerplate:

  1. Application Layer.
  2. Data Layer.
  3. Additional Services.

In remote environments, it is often not the developers that manage the last two layers. If that's the case, it would be best to externalize those services to the equivalents from your provider.

In this chapter, we focus on how to deliver properly the first layer.

Edit this page
Previous
« Layouts
Next
Docker Images »
Copyright © 2023 TheCodingMachine, Inc. Built with Docusaurus.