Composer keeps reverting to v1 on Digital Ocean droplet

I have an application running on Digital Ocean and managed by Laravel Forge, and it seems like every time I go to deploy my application I need to SSH into the box and manually invoke composer self-update --2, to update composer to v2.

I would have expected to need to only run this once ever, but it seems like the state of the droplet is being reverted after a period of time.

Has anyone experienced this or have any suggestions for why it could be happening?

Thanks

rodrigo.pedra

5 years ago

Best Answer

Level 56

On forge, navigate to your server (not the site/app, but the server) and click the "Scheduler" option on the sidebar.

URL is something like this:

https://forge.laravel.com/servers/XXXXXX#/scheduler

Where XXXXXX is your forge's server ID

You'll see a scheduled cron task to self-update composer. This task is added by default by forge to every server.

Probably yours is set like this:

/usr/local/bin/composer self-update --1

Create a new scheduled task to update to version , and delete this one.

19 likes

viglucci

5 years ago

Level 1

That was it.

Thanks!!

1 like

rodrigo.pedra

5 years ago

Level 56

You’re welcome! Have a nice day

Please or to participate in this conversation.