Developer Guideline
  • Home
  • 🧠Must you know
    • Algorithm
    • Architecture
      • API
    • Comparison
      • ID Token vs Access Token
      • Lazy Loading vs Eager Loading
      • Morphs vs Foreign Key
      • UUID vs ULID
      • GraphQL vs REST
      • Cache vs CDN
      • Concurrency vs Parallelism
      • Null vs Not Null
    • Diagram
      • CI/CD Pipeline
      • High Performance Culture
  • ☂️Laravel
    • Template
      • Template System Check in Route on Laravel
      • Template Function in FormController on Laravel
      • Template Route call FormController on Laravel
      • Template Route Prefix Name on Laravel
      • Template Basic and Custom Pagination on Laravel
      • Template PHP Artisan Command
      • Template Route for App Environment
    • Feature
      • Data Type
      • Mailables
      • Rules
    • Package
    • Document
  • 🫖Collaboration Agreement
    • Naming Convention
      • Naming Convention for Git Branch
      • Naming Convention for Environment Variable
    • Rule
      • Rule of Commit Message
      • Semantic Versioning
  • 🦣Project Manager
    • Requirements
      • System Requirements
      • Technical Requirements
      • Functional Requirements
Powered by GitBook
On this page
  1. Collaboration Agreement
  2. Naming Convention

Naming Convention for Environment Variable

แนวทางการตั้งชื่อสำหรับ environment variable (.env) ตามข้อตกลงร่วมกัน

File Name
Description

.env

Default environment file for local development.

.env.example

Sample template for environment variables.

.env.testing

Environment file for automated tests.

.env.production

Environment file for production.

.env.staging

Environment file for staging.

.env.local

Additional local environment file to override .env.

.env.development

Environment file for development.

.env.ci

Environment file for continuous integration (CI) builds.

PreviousNaming Convention for Git BranchNextRule

Last updated 5 months ago

🫖