Add Setup Script (Frontend, Backend, Syncserver via Tmux)

[its-me-abhishek]

Is your feature request related to a problem? Please describe.
Currently, contributors need to run multiple servers (frontend, backend, syncserver) manually in separate terminals or rely on Docker/Kubernetes, which may not always be convenient for local testing.

Describe the solution you'd like
Create a setup script (e.g., setup.sh) that automatically runs all three components using Tmux. Should be placed in a new Directory named as development. Do include a README with reference to Documentation, and the environment variables required. Tell about all pre requisites to run it locally (npm, tmux, etc.)

For example:

tmux new-session -d -s ccsync "cd backend && flask run"
tmux split-window -h "cd frontend && npm start"
tmux split-window -v "docker-compose up syncserver"
tmux attach -t ccsync

Describe alternatives you've considered

• A Makefile with individual commands for each service
• Using a simple Python script to spawn subprocesses but it might be too complex and adds yet another dependency

Additional context
This will make local development much faster and reduce setup friction for new contributors.

[ShivaGupta-14]

@its-me-abhishek could you please assign this also?

[Hell1213]

Hey @its-me-abhishek , Hi! I’d like to work on this issue.

From what I understand, the goal is to make local development easier by creating a development/ directory that contains a script (likely setup.sh) which starts all three services together using tmux:

Backend (Flask)

Frontend (npm start)

Syncserver (via Docker Compose)

The script will open a tmux session, create panes for each service, run them, and optionally attach to the session.
I’ll also add a small README explaining prerequisites (tmux, npm, python, docker), how to run the script, and mention any required environment variables.

Before I start, I just want to confirm one thing: Should the commands for starting each service be hardcoded inside the script, or should I load them from a .env file / config variable?

If everything looks good, could you please assign this issue to me? I’d be happy to take it forward.

[its-me-abhishek]

Before I start, I just want to confirm one thing: Should the commands for starting each service be hardcoded inside the script, or should I load them from a .env file / config variable?

Hardcoded shall work imo