π‘οΈ Safety & Recovery
Protecting your existing work is our primary directive. The static-repo-page-kickstart is designed to be non-destructive, providing multiple layers of defense before any system changes occur.
π‘οΈ Automated Backupsβ
Before the installer modifies a single file, it triggers the Safety-First module.
Location & Namingβ
All backups are stored in your repository's root directory with a unique timestamp:
- Format:
backup_YYYYMMDD_HHMM.tar.gz - Content: A full compressed archive of your current project state
(excluding files already in
.gitignore).
How to Restoreβ
If you need to revert to the state prior to running the kickstarter, use the following command:
tar -xzvf backup_TIMESTAMP.tar.gz
Use code with caution.
π Pre-Flight Collision Detectionβ
To maintain your Modular Architecture without corruption, the script performs a deep scan of your environment:
- Docusaurus Check: If a website/ folder already exists, the script will pause and ask for your permission to Purge (Clean install) or Overwrite.
- CI/CD Verification: We detect existing .gitlab-ci.yml or .github/workflows/
files. You can choose to:
- Preview: View the new logic in your terminal first.
- Sample: Save as .sample files for manual merging.
- Overwrite: Replace with the new Cross-Platform Bridge.
ποΈ Safety by Designβ
- Encapsulation: All documentation logic is isolated within the website/ directory to prevent interference with your core repository code.
- Dry-Run Auditing: You can always audit the full logic of the installer
before execution by running:
curl -sSL https://.../setup.sh | less - Standardized Cleanliness: Our Standardization pillar ensures that any temporary files created during the build are automatically purged upon completion.