eugenevdm
2 months ago
137
0
Forge

Forge API refusing to deploy with 'forge' user and vague validation error

Posted 2 months ago by eugenevdm

I would like to deploy Forge sites using the built-in 'forge' user. This is the default Unix user that is chosen if you deploy a site and you don't make it isolated. I'm happy with this scenario because it allows me to quickly SSH to the box and do any granular SSH work that might be required. I can also jump between directories without having to go up and down too much.

The Forge API script payload looks like this:

{
            "domain": "$fullyQualifiedDomainName",
            "project_type": "php",            
            "directory": "/public",           
            "isolated": true,
            "username": "$domain",
            "database": "$database"
}

That works. Now simply changing from isolated to false and using the built-in user forge, I get a generic validation error.

{
            "domain": "$fullyQualifiedDomainName",
            "project_type": "php",            
            "directory": "/public",           
            "isolated": false,
            "username": "forge",
            "database": "$database"
}

Is there a way to determine what is wrong with the validation? Perhaps it's not possible to use the built-in forge user and simulate what's already possible using the UI?

Please sign in or create an account to participate in this conversation.