Ploi Releases ‘The Forgejo Update’

Following The SSL & Tenant Update, the Ploi team has just rolled out the so-called ‘Forgejo Update’ to its user-friendly server management tool.

New Features

Ploi has supported GitHub, GitLab and Bitbucket for years. Previously, code on Codeberg or on a Forgejo server that you run yourself had to be added as a custom repository, with the deploy key and webhook set up manually. From today onwards, Forgejo will work in the same way as the other three source control providers.

Take a look at the benefits:

• Install a Forgejo repository on a website, application or WordPress site. Select from a list of your repositories and their branches, including those of organisations you belong to.
• Deploy with zero downtime. Ploi pulls with the token of the linked account.
• Activate quick deployment. Ploi will then add a push webhook to the repository and deploy when you push to the branch.
• See the latest Forgejo commits in the panel.
• Install Forgejo repositories via the API and the MCP server.

In other news, RunCloud has joined Laravel Forge and ServerPilot in offering a server import feature. It works in the same way as the ServerPilot import.

Next: Site Commands

Every site is about to get a new Commands tab. You type a command and Ploi runs it in the site’s directory as the site’s system user. You can then view the output while the command is running. PHP and Composer use the site’s own PHP version, meaning that commands such as ‘php artisan migrate’ or ‘composer install’ run on the version that the site is served with. No SSH session is needed.