vccs
Vue 3용 차트 컴포넌트 모음, Recharts에서 포팅
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Web app for the SPACESCANS EHR ↔ environmental-exposure linkage pipeline: upload a patient cohort CSV, pick exposure variables, run the pipeline, and explore the results.
The same setup runs on macOS, Windows, and Linux — everything runs inside Docker containers, so there is nothing OS-specific to configure.
The only thing you install yourself is Docker — Docker Desktop on macOS/Windows, Docker Engine on Linux.
Docker Desktop users (macOS/Windows): give the Docker VM enough memory — Settings → Resources → Memory ≥ 12 GB. The pipeline works on multi-GB geodata inside the VM; at the ~8 GB default a large run can get OOM-killed. Linux needs no setting — containers see all host RAM.
git clone https://github.com/IU-Ultraman/spacescans-web.git
cd spacescans-web
cp .env.docker.example .env # then set SECRET_KEY — see step 1
docker compose up --build # first build takes a few minutes
Then open http://localhost:3000 and sign up to create an account.
The app runs without any exposure data. To add a dataset, run one command
from this directory — it downloads from the deployer's shared folder,
verifies the checksum and extracts it into pipeline-data/:
scripts/fetch_distribution.sh --list # what's available
scripts/fetch_distribution.sh tract_boundaries_v1.tar.gz # one dataset
scripts/fetch_distribution.sh --small # everything except Bluespace
# (7 variables, 8.5 GB on disk)
The script wraps python -m spacescans data fetch (resumable downloads,
SHA-256 checks from the package's data manifest), so it needs a Python with
the spacescans package installed; set SPACESCANS_PYTHON to point at one
(scripts/fetch_distribution.sh --help has the install line). Without one,
run the same command in the backend container, which has the package and the
data root at /project:
docker compose exec backend /opt/conda/bin/python -m spacescans data fetch --data-dir /project --dataset tract_boundaries.
Add only what the variables you plan to run need — the in-app Data Setup page shows the command for each variable, and takes archive uploads if you would rather not use a terminal. Datasets whose licenses forbid redistribution (VNL, TEMIS) are listed there with their original download sites. See pipeline-data/README.md for the full layout.
cp .env.docker.example .env
Then set SECRET_KEY in .env to a random value. Generate one with:
openssl rand -hex 32
Open .env and replace the placeholder with the generated value:
SECRET_KEY=<paste the generated value here>
Skipping this is fine for local testing — defaults apply — but set a real secret for anything else.
docker compose up --build
http://localhost:3000http://localhost:8000The first build downloads ~1.5 GB of dependencies and takes a few minutes; later runs are cached and fast. Open the frontend and sign up to create an account.
docker compose down # stop
docker compose down -v # stop + also delete accounts/tasks/cache
docker compose logs -f backend # follow backend logs
spacescans-web is released under the MIT License (LICENSE), like the spacescans package it runs. The license covers the software only: each catalog source keeps its provider's terms (the Data Setup page lists them), and a dataset a user registers keeps the terms of its source, which its owner is responsible for before sharing it with the deployment.