Original working file
START-HERE.txt
Code and working example pages keep their original identifiers and sample text. The lesson and file guidance explain them in your language.
PRACTICAL ROUTE
Download a real backup of supplied practice records, restore it into a separate empty practice target and check the recovered values.
Your role: Operate the supplied source/target controls, inspect the backup and verify the restored data and scope.
1. Use the supplied project and ask your coding assistant to carry out the implementation. You do not need to write HTML, JavaScript or SQL yourself.
2. Follow the current lesson steps, configure only your own permitted accounts and check the result in the actual page/provider.
3. Keep expected results and observed results separate. Record the exact blocked step if you cannot run a live check.
BASIC ROUTE: open practice/index.html from the lesson or extracted workshop. It really exports/imports the supplied local records, without a server or account. This does not back up an existing hosted website. The PostgreSQL/Bash instructions below are an OPTIONAL ADVANCED extension for owners of disposable databases.
--- DETAILED SETUP / OPTIONAL IMPLEMENTATION REFERENCE ---
Create TWO disposable PostgreSQL databases: a source and an EMPTY restore target. Confirm host/project/database identities yourself before proceeding. Install PostgreSQL client tools compatible with the source server; pg_dump cannot dump a newer major server using an older major client.
Run seed.sql ONLY in the source. Run bash export.sh and enter its connection URL privately at the prompt (not in Git or screenshots). Inspect backups/contents.txt. Then run bash restore.sh and enter the DIFFERENT EMPTY target URL. It prints target identity and requires RESTORE-PRACTICE confirmation. It never drops/replaces an existing table.
This archive includes ONLY public.backup_practice_notes. It excludes other tables, auth users, roles, grants, provider settings, uploaded file bytes and secrets. Restore target must stay private; permissions are not recreated by these no-privileges commands. A real service needs a broader reviewed backup/restore plan and access-policy verification.