Launchpad

SQL + Frontend intake workflow

ارفع قاعدة البيانات وملفات الواجهة من مكان واحد، ثم حوّلها إلى مساحة عمل جاهزة.

This first MVP slice gives you one guided admin page to register the database connection, upload the SQL dump, queue the import, and keep HTML/CSS/JavaScript assets organized for the next build step.

Progress

0/4

Complete the four steps below to build your first connected intake flow.

Database profilePending
SQL dumpPending
Import queuePending
Frontend filesPending

Connections

0

Saved database profiles for MySQL, PostgreSQL, MariaDB, SQLite, or MSSQL.

SQL uploads

0

Registered SQL dumps waiting for mapping or review.

Import jobs

0

Queued import runs that connect dumps to a destination database.

Frontend assets

0

Uploaded HTML, CSS, JS, ZIP, and supporting files kept in one library.

Step 1

Create a database connection profile

Save the destination database credentials as a draft first. This keeps the workflow safe while you prepare the actual import.

No create permission

Ask an administrator for CREATE_DATABASE_CONNECTIONS to use this step.

Step 2

Upload your SQL dump

Attach the .sql dump or a plain SQL script, give it a clear label, and keep it discoverable for the next import action.

No create permission

Ask an administrator for CREATE_SQL_UPLOADS to use this step.

Step 3

Queue the import job

Pair the uploaded SQL dump with a saved connection. This creates a clear handoff for review, testing, and the actual execution later.

No create permission

Ask an administrator for CREATE_IMPORT_JOBS to use this step.

Step 4

Upload frontend files

Store your HTML, CSS, JavaScript, ZIP package, or supporting media in one library so the frontend handoff stays tidy.

No create permission

Ask an administrator for CREATE_ASSETS to use this step.

Recent data setup

Connections + SQL uploads

Full list

Loading recent activity...

Recent delivery assets

Import jobs + frontend files

Full list

Loading recent activity...

Next step

This is your first iteration.

After you validate the intake flow, the logical follow-up is a true execution step: table preview, schema mapping, and a controlled “run import” action for the queued jobs.