scriptoriumadmin/smriti
1
0
Fork 0
mirror of https://github.com/himanshudongre/smriti.git synced 2026-08-28 05:14:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Apply the same two-terminal split to the landing page install block

Browse source 
The previous commit (Codex's README activation-path fix) split the
README's step-1 code block to make it clear that `make dev-local` is a
long-running foreground process that must stay in one terminal while
`source backend/.venv/bin/activate` runs in another.

The landing page at `website/index.html` had the same paste-and-get-stuck
shape in its "Try it in 5 minutes" install block. Apply the parallel
split with the exact same wording so the website and README give the
same first-run guidance — install in one block, then "Start the backend
in one terminal and keep it running", then "In a second terminal,
activate the CLI before running smriti commands".

Verified locally: page renders the split cleanly at 1280x800, no console
errors.
This commit is contained in:
Himanshu Dongre 2026-05-21 01:43:52 +05:30
parent 73914a9e1a
commit 6ddfc2eedf
1 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
website/index.html
View file

@ -177,8 +177,11 @@ smriti metrics # project coordination KPIs</code></pre>
<h3>1. Install</h3>
<pre><code>git clone https://github.com/himanshudongre/smriti
cd smriti
make setup-local # backend venv + CLI + frontend, no Docker
make dev-local # backend on http://localhost:8000
make setup-local # backend venv + CLI + frontend, no Docker</code></pre>
<p>Start the backend in one terminal and keep it running:</p>
<pre><code>make dev-local # backend on http://localhost:8000</code></pre>
<p>In a second terminal, activate the CLI before running <code>smriti</code> commands:</p>
<pre><code>cd smriti
source backend/.venv/bin/activate</code></pre>
</li>
<li>