Publishing

What publishing does

Until you publish, your app lives at an address only you have. Publishing gives it one meant to be shared.

Your preview keeps working afterwards. Carry on changing it, and publish again when the next version is ready.

Nine checks first

Before anything goes out, we read the whole project against nine checks. The point is one thing: nobody should be able to reach data that is not theirs.

• Passwords and keys left sitting in the code where a visitor could read them.
• Data rules — whether a stranger can read or change rows that belong to someone else.
• Sign-in, and whether pages that should be behind it really are.
• What the app keeps in the browser, and where links are allowed to send people.
• Outside services it talks to, and what ships in the finished files.

Serious findings hold it back

If a check finds something serious, publishing stops. The server decides that, not the screen, so it cannot be clicked past.

Changing an unrelated line does not clear it either. The only way out is to fix the finding and run the check again — and a clean re-check costs nothing.

You can dismiss a finding to get it out of your list, but a dismissed one still counts at the gate. The screen tells you how many are hidden so an empty list never looks like a mystery.

You confirm before it goes

There is a review step. You see what was checked and what is about to go out, then you confirm.

It is a step on purpose. Publishing is the moment strangers can reach your app, and that is worth one deliberate press.

After it is out

You get an address straight away and can hand it to anyone.

If you already own a domain name, you can serve the project on that instead.