Any idea why this has suddenly changed? I've deployed more than a dozen servers before and never had to worry about it.
One of the beauties of Forge was that you didn't need to worry about things like dependencies unless you were really going off the path of best practices.
Just in case anyone else is trying to get a fix for this, I've managed to go 2 steps backwards:
The sudo password that forge mails you is incorrect and doesn't work, so you're not able to manually install composer and other dependencies.
From what I've gathered it seems the DO delay in processing events has caused the server to deploy without the follow up events of installing/updating/setting up being executed. Basically causing forge and DO to be out of sync with the real status of your server.
Thinking it may be time to add another cloud provider onto my forge account.
DigitalOcean is reporting that the mirror issues were fixed, so I just tried to spin up a new server via Forge. Got that update from Laravel's Twitter page.
Still receiving the same error 'composer: command not found' when trying to setup quick deploy from my GitHub repository.
Took me all of 5 minutes to add my AWS credentials to forge.
I'll jump ship to Amazon until DO sorts this out. (Still prefer DO but I really need to get this server running already!)
I understand things fall down sometimes, but that's what a status page is for. P*sses me off that they claim everything is fine when things are clearly not working somewhere.
@maisnamraju keeping my fingers crossed it is able to get resolved this afternoon.
@dylanh thanks for the update about AWS still working with Forge. I also need to get a server up and running ASAP, so probably going to follow in your footsteps in the meantime. Definitely prefer DigitalOcean also, but things happen.