First-Day Checklist

Complete these steps before going live

Once the installer finishes and the first admin can sign in, complete this checklist before inviting learners or processing real payments.

1. Confirm secure access

• enable HTTPS for the final domain
• verify the login page and account pages load over HTTPS only
• remove or restrict installer access if the hosting workflow allows it

2. Configure email

Set up SMTP before any production use. This is required for:

• password reset emails
• user notifications
• admin workflow messages

If SMTP is skipped, account recovery and some operational flows will break.

3. Review branding and public text

Replace placeholder visuals and copy where needed:

• site name
• logos
• banners
• public homepage messaging
• footer and contact details

4. Check global settings

Review the main settings area and confirm:

• platform name and basic business identity
• public URLs
• payment-related settings if Stripe is used
• learner-facing content defaults

5. Validate writable storage after permission hardening

If you tighten permissions after installation, verify these areas still function:

• session creation
• file uploads
• branding asset uploads
• backup generation
• plugin package storage

6. Test the core production flows

Run a short smoke test:

1. Sign in as admin.
2. Create or inspect a course.
3. Load the public course page.
4. Submit a password reset request.
5. Upload a small media asset.

7. Take the first backup baseline

Before editors or learners start using the system, store:

• a database backup
• the deployed file package
• the active storage/config/kubik.config

This creates a clean rollback point for future updates.