Edit any app's files, like a site

Your app's code is yours to change in the browser, whether it came from a ZIP or from GitHub.

What's new

• Every app's code opens in Files: one folder tree, with kept folders like Laravel's storage inside it, marked kept. Edit, upload a file or a ZIP, add, rename, move or delete, as on a site.

• Each change goes live by itself: saving says "Saved. Going live in about a minute…" and follows the version until it's live. Several quick saves go live together, and every save stays in the app's versions, so Go back to version 12 still works.

• Small changes in seconds: a PHP view, a template, a picture or a static page is laid on the version before, live in about 15 to 30 seconds. The deploy page says Quick change with the number of files. A change to composer.json or package.json makes a full version.

• Even when the last version failed: fix the file in Files and save, and it tries again.

• Apps from GitHub too: saving changes your app at once and opens a pull request in your repository, so your next push keeps the change. A push that would replace an unmerged change says so on its deploy page.

• Owners and developers can change files; viewers look only. A ready-made app's code stays as its makers publish it.

• Fewer words about builds: the dashboard says Versions, Version 12, Save and go live, Go back to version 12, Send version 12 to production and Try again.

• One way to add your code: the project's Add a service card has App or website. A classic PHP ZIP without Composer runs as a website by itself, anything else as an app, and you can switch before you deploy.

Read The file manager and Deploying.