{"id":2943,"date":"2026-04-25T10:07:52","date_gmt":"2026-04-25T10:07:52","guid":{"rendered":"https:\/\/aiopsschool.com\/blog\/?p=2943"},"modified":"2026-04-25T11:04:13","modified_gmt":"2026-04-25T11:04:13","slug":"coding-best-practices-using-codex-for-laravel-developers","status":"publish","type":"post","link":"https:\/\/aiopsschool.com\/blog\/coding-best-practices-using-codex-for-laravel-developers\/","title":{"rendered":"Coding Best Practices using Codex for Laravel Developers"},"content":{"rendered":"\n

Option 1 <\/h2>\n\n\n\n

Do not<\/strong> start Codex from the parent folder unless you need all projects.<\/p>\n\n\n\n

For each Laravel project, add ignore files:<\/p>\n\n\n\n

cat > .codexignore <<'EOF'\nvendor\/\nnode_modules\/\nstorage\/\nbootstrap\/cache\/\npublic\/build\/\npublic\/hot\n.git\/\n.env\n*.log\n*.zip\n*.sql\n*.dump\n*.bak\nEOF<\/code><\/pre>\n\n\n\n
Option 2<\/h2>\n\n\n\n
Also add\/update AGENTS.md<\/code> inside each project:<\/p>\n\n\n\n
# Professnow Laravel project\n\nOnly inspect files relevant to the requested task.\n\nDo not scan:\n- vendor\/\n- node_modules\/\n- storage\/logs\/\n- bootstrap\/cache\/\n- public\/build\/\n- .env\n\nBefore editing, identify the exact files needed.\nPrefer small, targeted changes.\nDo not refactor unrelated code.<\/code><\/pre>\n\n\n\n
Option 3 <\/h2>\n\n\n\n
Use targeted prompts like:<\/p>\n\n\n\n
Fix the booking status issue. Look only in routes\/web.php, app\/Http\/Controllers, app\/Models, and resources\/views\/bookings.<\/code><\/pre>\n\n\n\n
Avoid prompts like:<\/p>\n\n\n\n
Analyze this whole project<\/code><\/pre>\n\n\n\n
Example, If you have multiple microservices<\/h3>\n\n\n\n
root@ip-172-31-1-90:\/opt\/lampp\/htdocs\/professnow# ls -1\nadmin-new\nbookings-new\ncategory-new\ncustomer-managers-new\ngallery\nnotification-new\nprofessional-new\nprofessnow-new<\/code><\/pre>\n\n\n\n
Use this structure:<\/p>\n\n\n\n
\/opt\/lampp\/htdocs\/professnow\/\n\u251c\u2500\u2500 AGENTS.md          # global rules\n\u251c\u2500\u2500 .codexignore      # global ignore\n\u251c\u2500\u2500 admin-new\/\n\u251c\u2500\u2500 bookings-new\/\n...\n<\/code><\/pre>\n\n\n\n
Create global .codexignore<\/code>:<\/p>\n\n\n\n
cd \/opt\/lampp\/htdocs\/professnow\n\ncat > .codexignore <<'EOF'\n**\/vendor\/\n**\/node_modules\/\n**\/storage\/\n**\/bootstrap\/cache\/\n**\/public\/build\/\n**\/public\/hot\n**\/.git\/\n**\/.env\n**\/error_log\n**\/nohup.out\n**\/*.log\n**\/*.zip\n**\/*.sql\n**\/*.dump\n**\/*.bak\nEOF\n<\/code><\/pre>\n\n\n\n
Create global AGENTS.md<\/code>:<\/p>\n\n\n\n
cat > AGENTS.md <<'EOF'\n# Professnow workspace rules\n\nThis workspace contains multiple separate projects.\n\nProjects:\n- admin-new: admin panel\n- bookings-new: bookings service\/app\n- category-new: category service\/app\n- customer-managers-new: customer manager app\n- gallery: standalone PHP\/gallery assets\n- notification-new: notification service\/app\n- professional-new: professional app\n- professnow-new: main Professnow app\n\nRules:\n- Do not scan all projects unless explicitly asked.\n- First identify which project is relevant.\n- Work inside only one project at a time.\n- Ignore vendor, node_modules, storage, logs, cache, build files, backups, and env files.\n- Before editing, list the exact files you plan to inspect.\n- Make small targeted changes only.\n- Do not refactor unrelated code.\nEOF\n<\/code><\/pre>\n\n\n\n
Then add per-project ignore files:<\/p>\n\n\n\n
for d in admin-new bookings-new category-new customer-managers-new notification-new professional-new professnow-new; do\ncat > \"$d\/.codexignore\" <<'EOF'\nvendor\/\nnode_modules\/\nstorage\/\nbootstrap\/cache\/\npublic\/build\/\npublic\/hot\n.git\/\n.env\nerror_log\nnohup.out\n*.log\n*.zip\n*.sql\n*.dump\n*.bak\nEOF\ndone\n<\/code><\/pre>\n\n\n\n
For gallery<\/code>:<\/p>\n\n\n\n
cat > gallery\/.codexignore <<'EOF'\nimages\/\ngalleries\/\ngallery\/\nsingle\/\n*.zip\n*.bak\n*.log\nEOF\n<\/code><\/pre>\n\n\n\n
Best daily usage:<\/p>\n\n\n\n
cd \/opt\/lampp\/htdocs\/professnow\/bookings-new\ncodex\n<\/code><\/pre>\n\n\n\n
Not:<\/p>\n\n\n\n
cd \/opt\/lampp\/htdocs\/professnow\ncodex\n<\/code><\/pre>\n\n\n\n
Prompt style:<\/p>\n\n\n\n
Work only in bookings-new. Inspect routes, controllers, models, and related views only. Do not scan other projects.\n<\/code><\/pre>\n\n\n\n
This will save the most credit.<\/p>\n\n\n\n
Option 4<\/h2>\n\n\n\n
Short Tutorial: Codex Memories<\/h1>\n\n\n\n
~\/.codex\/memories\/<\/code> is where Codex stores local memories so it can remember useful context from previous sessions. Memories are off by default<\/strong>, so you need to enable them first. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
1. Enable memories<\/h2>\n\n\n\n
Open Codex config:<\/p>\n\n\n\n
mkdir -p ~\/.codex\nnano ~\/.codex\/config.toml\n<\/code><\/pre>\n\n\n\n
Add:<\/p>\n\n\n\n
[features]\nmemories = true\n<\/code><\/pre>\n\n\n\n
Your user-level Codex config lives at:<\/p>\n\n\n\n
~\/.codex\/config.toml\n<\/code><\/pre>\n\n\n\n
(OpenAI Developers<\/a>)<\/p>\n\n\n\n
2. Check memory folder<\/h2>\n\n\n\n
ls -la ~\/.codex\/memories\n<\/code><\/pre>\n\n\n\n
If it is empty or missing at first, that is normal. Codex may create memory later after sessions become eligible.<\/p>\n\n\n\n
3. Use \/memories<\/code> inside Codex<\/h2>\n\n\n\n
Inside Codex, type:<\/p>\n\n\n\n
\/memories\n<\/code><\/pre>\n\n\n\n
Use this to control whether the current thread can:<\/p>\n\n\n\n
use existing memories\ngenerate future memories\n<\/code><\/pre>\n\n\n\n
Thread choices do not change your global config. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
4. What to save<\/h2>\n\n\n\n
Good memory:<\/p>\n\n\n\n
Remember that I prefer small, targeted changes.\nRemember that I usually want tests run before final answers.\nRemember that this project uses Laravel and MySQL.\nRemember not to scan vendor, node_modules, storage, or build folders unless needed.\n<\/code><\/pre>\n\n\n\n
Bad memory:<\/p>\n\n\n\n
Remember my database password.\nRemember my API key.\nRemember production customer data.\nRemember my SSH private key.\n<\/code><\/pre>\n\n\n\n
5. Recommended config<\/h2>\n\n\n\n
[features]\nmemories = true<\/code><\/pre>\n\n\n
[memories]<\/p>\n\n\n\n
use_memories = true generate_memories = true disable_on_external_context = true min_rollout_idle_hours = 6 max_rollout_age_days = 30 max_unused_days = 30<\/p>\n\n\n\n
These memory settings are documented in Codex\u2019s configuration reference. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
6. Memory vs AGENTS.md<\/h2>\n\n\n\n
Use memory for things Codex can recall:<\/p>\n\n\n\n
I prefer short explanations.\nI usually work in Laravel.\nI like small commits.\n<\/code><\/pre>\n\n\n\n
Use AGENTS.md<\/code> for rules Codex must follow:<\/p>\n\n\n\n
Do not edit generated files.\nDo not expose secrets.\nRun tests before finishing.\nDo not refactor unrelated code.\n<\/code><\/pre>\n\n\n\n
Codex supports AGENTS.md<\/code> as reusable project guidance. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
7. Delete memories<\/h2>\n\n\n\n
rm -rf ~\/.codex\/memories\n<\/code><\/pre>\n\n\n\n
This removes saved memories, but if memory is still enabled, Codex may create new ones later.<\/p>\n\n\n\n
8. Disable memories<\/h2>\n\n\n\n
[features]\nmemories = false<\/code><\/pre>\n\n\n
[memories]<\/p>\n\n\n\n
use_memories = false generate_memories = false<\/p>\n\n\n\n
Simple rule<\/h2>\n\n\n\n
Use:<\/p>\n\n\n\n
Memory = helpful recall\nAGENTS.md = strict rules\nPrompt = current task\n<\/code><\/pre>\n\n\n\n
That is the best practical setup.<\/p>\n\n\n\n
Option 4 – Codex Memories<\/h2>\n\n\n\n
~\/.codex\/memories\/<\/code> is where Codex stores local memories so it can remember useful context from previous sessions.<\/p>\n\n\n\n
Memories are useful for saving recurring preferences, project context, coding style, and workflow habits.<\/p>\n\n\n\n
\n\n\n\n
1. Enable Memories<\/h3>\n\n\n\n
Open your Codex config file:<\/p>\n\n\n\n
mkdir -p ~\/.codex\nnano ~\/.codex\/config.toml\n<\/code><\/pre>\n\n\n\n
Add this:<\/p>\n\n\n\n
[features]\nmemories = true\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
2. Check the Memory Folder<\/h3>\n\n\n\n
Run:<\/p>\n\n\n\n
ls -la ~\/.codex\/memories\n<\/code><\/pre>\n\n\n\n
If the folder is missing or empty at first, that can be normal. Codex may create memory files later after enough useful sessions.<\/p>\n\n\n\n
\n\n\n\n
3. Use \/memories<\/code> Inside Codex<\/h3>\n\n\n\n
Inside Codex, type:<\/p>\n\n\n\n
\/memories\n<\/code><\/pre>\n\n\n\n
Use this to control whether the current Codex session can:<\/p>\n\n\n\n
Use existing memories\nGenerate future memories\n<\/code><\/pre>\n\n\n\n
This is useful when working on sensitive or temporary tasks.<\/p>\n\n\n\n
\n\n\n\n
4. What to Save in Memory<\/h3>\n\n\n\n
Good examples:<\/p>\n\n\n\n
Remember that I prefer small, targeted changes.\nRemember that I like short explanations after code changes.\nRemember that this project uses Laravel and MySQL.\nRemember not to scan vendor, node_modules, storage, logs, or build folders unless needed.\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
5. What Not to Save<\/h3>\n\n\n\n
Avoid saving secrets or private production data:<\/p>\n\n\n\n
Database passwords\nAPI keys\nSSH private keys\n.env values\nCustomer data\nProduction tokens\n<\/code><\/pre>\n\n\n\n
Memory is for reusable working context, not secrets.<\/p>\n\n\n\n
\n\n\n\n
6. Recommended Config<\/h3>\n\n\n\n
[features]\nmemories = true<\/code><\/pre>\n\n\n
[memories]<\/p>\n\n\n\n
use_memories = true generate_memories = true disable_on_external_context = true min_rollout_idle_hours = 6 max_rollout_age_days = 30 max_unused_days = 30<\/p>\n\n\n\n
This enables memory while keeping it reasonably controlled.<\/p>\n\n\n\n
\n\n\n\n
7. Memory vs AGENTS.md<\/h3>\n\n\n\n
Use memory for helpful recall:<\/p>\n\n\n\n
I prefer small commits.\nI usually work with Laravel.\nI like concise summaries.\n<\/code><\/pre>\n\n\n\n
Use AGENTS.md<\/code> for strict rules:<\/p>\n\n\n\n
Do not expose secrets.\nDo not edit generated files.\nRun tests before finishing.\nDo not refactor unrelated code.\n<\/code><\/pre>\n\n\n\n
Simple rule:<\/p>\n\n\n\n
Memory = helpful recall\nAGENTS.md = strict rules\nPrompt = current task\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
8. Delete Memories<\/h3>\n\n\n\n
To remove all saved memories:<\/p>\n\n\n\n
rm -rf ~\/.codex\/memories\n<\/code><\/pre>\n\n\n\n
If memories are still enabled, Codex may create new ones later.<\/p>\n\n\n\n
\n\n\n\n
9. Disable Memories<\/h3>\n\n\n\n
Edit:<\/p>\n\n\n\n
nano ~\/.codex\/config.toml\n<\/code><\/pre>\n\n\n\n
Set:<\/p>\n\n\n\n
[features]\nmemories = false<\/code><\/pre>\n\n\n
[memories]<\/p>\n\n\n\n
use_memories = false generate_memories = false<\/p>\n\n\n\n
\n\n\n\n
10. Best Practice<\/h3>\n\n\n\n
Use Codex memories to reduce repeated explanations, but do not rely on memory alone.<\/p>\n\n\n\n
Best setup:<\/p>\n\n\n\n
~\/.codex\/memories\/   = learned context\n~\/.codex\/AGENTS.md   = personal rules\nproject\/AGENTS.md    = project rules\ncurrent prompt        = current task\n<\/code><\/pre>\n\n\n\n
Option 7 – graphify Graphify turns your project into a knowledge graph<\/strong> so Codex can understand the code structure<\/h2>\n\n\n\n
Short Tutorial: Graphify with Codex<\/h3>\n\n\n\n
Graphify turns your project into a knowledge graph<\/strong> so Codex can understand the code structure before searching files randomly. It creates files like graphify-out\/GRAPH_REPORT.md<\/code>, graphify-out\/graph.json<\/code>, and graphify-out\/graph.html<\/code>. The latest GitHub release shown is v0.5.0<\/strong>, released April 23, 2026. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
1. Install Graphify<\/h3>\n\n\n\n
The official package name is graphifyy<\/code>, but the command is graphify<\/code>.<\/p>\n\n\n\n
pipx install graphifyy\n<\/code><\/pre>\n\n\n\n
Or:<\/p>\n\n\n\n
pip install graphifyy\n<\/code><\/pre>\n\n\n\n
Check:<\/p>\n\n\n\n
graphify --help\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
2. Enable Codex Multi-Agent<\/h3>\n\n\n\n
Edit Codex config:<\/p>\n\n\n\n
mkdir -p ~\/.codex\nnano ~\/.codex\/config.toml\n<\/code><\/pre>\n\n\n\n
Add:<\/p>\n\n\n\n
[features]\nmulti_agent = true\n<\/code><\/pre>\n\n\n\n
Codex needs multi_agent = true<\/code> for Graphify parallel extraction. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
3. Install Graphify for Codex<\/h3>\n\n\n\n
Go to your project:<\/p>\n\n\n\n
cd \/path\/to\/your\/project\n<\/code><\/pre>\n\n\n\n
Install Codex integration:<\/p>\n\n\n\n
graphify codex install\n<\/code><\/pre>\n\n\n\n
Or:<\/p>\n\n\n\n
graphify install --platform codex\n<\/code><\/pre>\n\n\n\n
This writes Graphify guidance into AGENTS.md<\/code> and installs a Codex hook in .codex\/hooks.json<\/code>, so Codex is reminded to use the graph before broad file searching. (GitHub<\/a>)<\/p>\n\n\n\n
\n\n\n\n
4. Create the Graph<\/h3>\n\n\n\n
From terminal:<\/p>\n\n\n\n
graphify .\n<\/code><\/pre>\n\n\n\n
Inside Codex, use:<\/p>\n\n\n\n
$graphify .\n<\/code><\/pre>\n\n\n\n
Important: for Codex, use $graphify<\/code>, not \/graphify<\/code>. (PyPI<\/a>)<\/p>\n\n\n\n
\n\n\n\n
5. Use Graphify in Codex<\/h3>\n\n\n\n
After graph is created, ask Codex like this:<\/p>\n\n\n\n
Use Graphify first. Read graphify-out\/GRAPH_REPORT.md before searching files. Identify the relevant modules, then inspect only the needed files.\n<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
Use Graphify first and find where login is handled. Do not grep the whole project until you read GRAPH_REPORT.md.\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
6. Useful Graphify Commands<\/h3>\n\n\n\n
Build graph:<\/p>\n\n\n\n
graphify .\n<\/code><\/pre>\n\n\n\n
Update graph after code changes:<\/p>\n\n\n\n
graphify . --update\n<\/code><\/pre>\n\n\n\n
Ask graph a question:<\/p>\n\n\n\n
graphify query \"how does authentication work?\"\n<\/code><\/pre>\n\n\n\n
Explain one node\/file\/class:<\/p>\n\n\n\n
graphify explain \"UserController\"\n<\/code><\/pre>\n\n\n\n
Find path between two concepts:<\/p>\n\n\n\n
graphify path \"User\" \"Payment\"\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
7. Best Workflow with Codex<\/h3>\n\n\n\n
cd \/path\/to\/project\ngraphify codex install\ngraphify .\ncodex\n<\/code><\/pre>\n\n\n\n
Inside Codex:<\/p>\n\n\n\n
$graphify .\n<\/code><\/pre>\n\n\n\n
Then prompt:<\/p>\n\n\n\n
Use Graphify before search. Read GRAPH_REPORT.md first, then make a small targeted change.\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Simple Rule<\/h3>\n\n\n\n
Graphify = project map\nGRAPH_REPORT.md = summary Codex should read first\n$graphify . = run Graphify inside Codex\ngraphify . --update = refresh graph after changes\n<\/code><\/pre>\n\n\n\n
Option 6 – .graphifyignore<\/code> tells Graphify which files and folders to skip when building a project knowledge graph.<\/h2>\n\n\n\n
Short Tutorial: .graphifyignore<\/code><\/h3>\n\n\n\n
.graphifyignore<\/code> tells Graphify which files and folders to skip when building a project knowledge graph.<\/p>\n\n\n\n
It works like .gitignore<\/code>.<\/p>\n\n\n\n
Use it to avoid scanning:<\/p>\n\n\n\n
vendor\/\nnode_modules\/\nlogs\/\ncache\/\n.env files\nlarge media files\ndatabase dumps\nbuild output\n<\/code><\/pre>\n\n\n\n
This makes Graphify faster, cleaner, and safer.<\/p>\n\n\n\n
\n\n\n\n
Why Use .graphifyignore<\/code>?<\/h3>\n\n\n\n
Without .graphifyignore<\/code>, Graphify may scan unnecessary files like:<\/p>\n\n\n\n
vendor\/\nnode_modules\/\nstorage\/logs\/\npublic\/build\/\n.env\n*.sql\n*.zip\n<\/code><\/pre>\n\n\n\n
That can make the graph noisy and may waste time or tokens.<\/p>\n\n\n\n
With .graphifyignore<\/code>, Graphify focuses only on useful project files.<\/p>\n\n\n\n
\n\n\n\n
Create .graphifyignore<\/code><\/h3>\n\n\n\n
Go to your project folder:<\/p>\n\n\n\n
cd \/path\/to\/your\/project\n<\/code><\/pre>\n\n\n\n
Create the file:<\/p>\n\n\n\n
nano .graphifyignore\n<\/code><\/pre>\n\n\n\n
Or use:<\/p>\n\n\n\n
cat > .graphifyignore <<'EOF'\nvendor\/\nnode_modules\/\nstorage\/\nbootstrap\/cache\/\npublic\/build\/\n.env\n*.log\n*.sql\n*.zip\nEOF\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Basic Example<\/h3>\n\n\n\n
vendor\/\nnode_modules\/\n.env\n*.log\n*.zip\n<\/code><\/pre>\n\n\n\n
This tells Graphify to ignore:<\/p>\n\n\n\n
vendor\/          dependency files\nnode_modules\/    npm packages\n.env             secrets\/config file\n*.log            log files\n*.zip            archive files\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Laravel Example<\/h3>\n\n\n\n
vendor\/\nnode_modules\/\nstorage\/\nbootstrap\/cache\/\npublic\/build\/\npublic\/hot\n.env\n.env.*\n*.log\n*.sql\n*.dump\n*.zip\n*.bak\n<\/code><\/pre>\n\n\n\n
Good for Laravel projects because it skips dependencies, cache, logs, environment files, and database dumps.<\/p>\n\n\n\n
\n\n\n\n
Node \/ React Example<\/h3>\n\n\n\n
node_modules\/\ndist\/\nbuild\/\ncoverage\/\n.next\/\n.nuxt\/\n.env\n.env.*\n*.log\n<\/code><\/pre>\n\n\n\n
Good for frontend projects because it skips dependencies, build output, test coverage, and environment files.<\/p>\n\n\n\n
\n\n\n\n
Python Example<\/h3>\n\n\n\n
.venv\/\nvenv\/\n__pycache__\/\n.pytest_cache\/\n.mypy_cache\/\ndist\/\nbuild\/\n.env\n*.log\n*.db\n*.sqlite\n<\/code><\/pre>\n\n\n\n
Good for Python projects because it skips virtual environments, caches, build files, logs, and local databases.<\/p>\n\n\n\n
\n\n\n\n
Large Workspace Example<\/h3>\n\n\n\n
For a folder with multiple apps:<\/p>\n\n\n\n
**\/vendor\/\n**\/node_modules\/\n**\/storage\/\n**\/bootstrap\/cache\/\n**\/public\/build\/\n**\/.env\n**\/*.log\n**\/*.sql\n**\/*.zip\n<\/code><\/pre>\n\n\n\n
The **\/<\/code> pattern means \u201cmatch this folder or file anywhere inside the workspace.\u201d<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
**\/vendor\/\n<\/code><\/pre>\n\n\n\n
matches:<\/p>\n\n\n\n
app1\/vendor\/\napp2\/vendor\/\nbackend\/vendor\/\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Run Graphify After Creating It<\/h3>\n\n\n\n
graphify .\n<\/code><\/pre>\n\n\n\n
Graphify will now skip everything listed in .graphifyignore<\/code>.<\/p>\n\n\n\n
\n\n\n\n
Best Practice<\/h3>\n\n\n\n
Keep .graphifyignore<\/code> strict.<\/p>\n\n\n\n
A good rule:<\/p>\n\n\n\n
Ignore anything that is generated, secret, huge, cached, or not written by your team.\n<\/code><\/pre>\n\n\n\n
Useful files to keep:<\/p>\n\n\n\n
app\/\nsrc\/\nroutes\/\nconfig\/\ndatabase\/migrations\/\nresources\/views\/\nREADME.md\nAGENTS.md\ncomposer.json\npackage.json\n<\/code><\/pre>\n\n\n\n
Files to ignore:<\/p>\n\n\n\n
vendor\/\nnode_modules\/\nstorage\/\nlogs\/\n.env\nbuild\/\ndist\/\n*.sql\n*.zip\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Final Example<\/h3>\n\n\n\n
# Dependencies\nvendor\/\nnode_modules\/\n\n# Secrets\n.env\n.env.*\n\n# Logs and cache\nstorage\/\nbootstrap\/cache\/\n*.log\n\n# Build output\npublic\/build\/\ndist\/\nbuild\/\n\n# Backups and dumps\n*.sql\n*.dump\n*.zip\n*.bak\n<\/code><\/pre>\n\n\n\n
This is enough for most projects.<\/p>\n","protected":false},"excerpt":{"rendered":"
Option 1 Do not start Codex from the parent folder unless you need all projects. For each Laravel project, add […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2943","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/2943","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=2943"}],"version-history":[{"count":7,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/2943\/revisions"}],"predecessor-version":[{"id":2964,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/2943\/revisions\/2964"}],"wp:attachment":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=2943"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=2943"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=2943"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}