Getting started
ScriptBox is a catalog and installation workflow for web applications. Begin with the outcome you need, then compare scripts by their stated features, requirements, version, license, and available installation path.
You can browse public catalog pages without an account. An account is needed when a workflow must save an order, license, installation, domain, hosting service, or support request to your dashboard.
- 1
Describe the job
Write down the must-have workflow, expected traffic, preferred stack, budget, and who will maintain the result.
- 2
Shortlist scripts
Compare the published description, screenshots, version, requirements, license, and support information.
- 3
Prepare a destination
Confirm the server runtime, database, HTTPS, storage, DNS access, and a recoverable backup before installing.
- 4
Install and verify
Follow the selected script’s installation flow, then test its public page, sign-in, email, file upload, and scheduled work as applicable.
Browse and evaluate the catalog
Catalog filters narrow the list; a detail page is the source for a specific script’s current public information. Availability, versions, prices, and installation support can change, so review the detail page again before acting.
Fit
Match features to a real workflow. A longer feature list does not compensate for a missing core requirement.
Requirements
Check runtime and database versions, required extensions, writable paths, background jobs, email, and storage needs.
License
Read the license attached to that script. Catalog access and a script’s right-to-use terms are separate questions.
Maintenance
Check the published version and documentation. Plan how you will back up, update, monitor, and recover the application.
Installation prerequisites
- A domain or temporary HTTPS origin that resolves to the intended server.
- A compatible web runtime and database, based on the selected script’s published requirements.
- Credentials with permission to create the application files and database without exposing unrelated services.
- A backup or snapshot and a tested way to restore the destination.
- Access to DNS, email delivery, cron or background workers when the application requires them.
A careful installation sequence
- 1
Confirm identity
Check the script ID, version, origin, and destination before approving an installer session.
- 2
Review changes
Understand which files, database objects, environment settings, and scheduled tasks the package will create.
- 3
Run prerequisites
Resolve failed runtime, extension, permission, HTTPS, database, or disk checks before continuing.
- 4
Complete setup
Keep the generated administrator credentials private and remove or lock setup surfaces when instructed.
- 5
Test and record
Verify critical flows and record the installed version, origin, license, backup, and rollback procedure.
Account and dashboard
Use the dashboard for resources tied to your account. Protect access with a unique password, keep the account email current, and sign out on shared devices. If you lose access, use the password reset flow rather than creating duplicate records.
Scripts and instances
Review the state of scripts, hosting, domains, databases, billing records, and notifications made available to your account.
Settings
Keep profile and security details accurate. Changes may affect notifications and recovery.
Support
Include the affected service, time, expected result, actual result, and a safe error excerpt. Never send passwords, private keys, or full tokens.
When you need support
Use dashboard support for an account-specific service. Use the public contact form for general, contribution, or partnership questions. A contact submission returns a ticket ID; save it so the conversation can be identified.
- State the affected URL without embedding credentials.
- Include exact steps that reproduce the problem.
- Share timestamps and request IDs when available.
- Redact access tokens, passwords, database exports, and customer data.