# Incorrect warnings in Ploi after automated site provisioning via API calls

**Project:** API | **Board:** Planned | **Votes:** 1
**URL:** https://roadmap.ploi.io/projects/6-api-level-requests/items/1306-incorrect-warnings-in-ploi-after-automated-site-provisioning-via-api-calls

---

# Summary

After provisioning a new Laravel site through API calls, the Ploi dashboard shows incorrect warnings:

* “Debug mode on” in the websites overview
* “You have composer install in your deploy script, without the --no-dev”
It also shows the “Deploy script suggestions” popup even though those suggestions have already been applied.

## Steps to reproduce

1. Create a new customer (for example, ploi) and provision a new site on a selected server via API calls.
2. Let the API handle the automated setup: create the deploy script, connect the repository, write the .env, create the database, and perform the initial deploy.
3. Open Ploi:
*  Go to Websites overview.
*  Click through to the newly created site.

## Actual result

* Websites overview: A badge “Debug mode on” is displayed.
* Site detail: A Deploy script suggestions modal appears even though the suggestions are already implemented.
* After dismissing the modal, two notices remain:
1. “You currently have debug mode on in your application.”
(Note: Opening and saving the .env in Ploi clears this message.)
2. “You have composer install in your deploy script, without the --no-dev.”
(This is incorrect — the deploy script does include composer install --no-dev.)

## Expected result
* No “Debug mode on” warning when APP_DEBUG=false in .env.
* No composer warning when --no-dev is present in the deploy script.
* No “Deploy script suggestions” modal when the suggested changes are already applied.

## Notes
* The .env file generated via the API sets APP_ENV=production and APP_DEBUG=false.
* The deploy script generated by the API includes composer install --no-dev --prefer-dist --no-interaction.