News · · Product update
New Services, New Resources, and New Ways to Deploy Your App
Today’s release is about the outside world: the services an app uses, and the host it goes to when it leaves the editor. Both are resources of your account – set up once, and then available for every project – and both have just been improved.
Resources for anything, by name
A resource used to be one of four fixed things: a MySQL database, an SMTP account, a PayPal account, an FTP host. Now you can add lots more resources, with lots of new capabilities, beyond those. The Resources page lists every kind by category with a short explanation of what it is for. But two things changed underneath.
Any service, with fields you name. The new Other kind holds whatever a service needs – an API key, an account id, a region – as fields you name yourself, each one marked protected or not. A protected field is kept encrypted, never listed, and never sent to the device: a PHP< >PHP block reads it on the server with exotool_resource("NAME", "key"). An unprotected one (a public key, an address) is readable on the device too, with exotool.resource("NAME", "key"). A project can use several.
Every resource has a name, and that name follows the app to its host. A deployed app reads every setting of its resources – database, mail, payments, maps, your Other resources – through one function, and whoever runs the server may override any of them with an environment variable, EXOTOOL_RES_<NAME>_<KEY>, give a value encrypted, or have the values read from AWS Secrets Manager or Google Secret Manager. Nothing has to be set: the app runs as compiled. But the production database or mail account can now be set on the server without a rebuild, and a secret need never be in a file at all.
Four new providers
- Google Maps. A Maps resource holds your own browser key; the Map element uses it, and a deployment requires one (previews keep using Exotool’s).
- SendGrid and Mailgun. Mail through their APIs, beside SMTP –
send_mailand the sign-in codes work the same, with attachments. - Stripe. Beside PayPal, and with one difference that matters: the card never reaches your app’s server. The credit card form hands it to Stripe from the device, and the server charges through a payment method id. Stripe also brings holds –
authorize_card,capture_card,release_card– for deposits, reservations and escrow. - Twilio. A new
send_sms(to, body)sends a text message through your Twilio account: a code, a reminder, a notice.
Deploying, explained before it runs
Just click the new Share icon in the editor’s top bar and choose Deploy: the dialog says what will happen before anything does – where the app goes, what goes there and what the host needs, and the settings the host’s operator may change afterwards, with this project’s exact variable names. If your diagram has unsaved changes, the deploy saves and generates them first and tells you so.
Where the app goes grew from one kind of host to five, and a new one can be added right there: an FTP host, an SFTP host over SSH (password or key), a Subversion or GitHub repository that receives the files for your own process to serve, or a zip file to download and put anywhere. An app with a sign-in form asks you to set its administrator’s password at its first deployment to a host, so a deployed app never starts with a default one.
There is a new deployment guide in the Help Center – the kinds of host, what a host needs, the first run, keeping the app running, the operator’s settings, and what to do when something fails – and Claude reads it too, so it can tell you what your host needs before you deploy.