Summary: How to install the 2027 developer environment for GakuNin (Japan's academic identity federation) RDM using the installer script, including prerequisites, step-by-step commands, everyday operations, security notes, and troubleshooting. All services run on
127.0.0.1with no host network changes. æŠèŠ: GakuNinïŒæ¥æ¬ã®åŠè¡èªèšŒé£æºïŒRDM ã® 2027 éçºç°å¢ãã€ã³ã¹ããŒã©ãŒã§å°å ¥ããæé ãåææ¡ä»¶ãã¹ãããããšã®ã³ãã³ããæ¥åžžæäœãã»ãã¥ãªãã£æ³šæç¹ããã©ãã«ã·ã¥ãŒãã£ã³ã°ãå«ãããã¹ãŠã®ãµãŒãã¹ã¯127.0.0.1ã§åäœãããã¹ãã®ãããã¯ãŒã¯èšå®ã¯å€ããŸããã
- Version / ç: 1.11 â 2026-11-13. Learned: a sentence that names the current milestone is live state, not history, so it changes in the same PR as
manifest/milestone.json: the owner closed M2 on 2026-11-13, the file now says M3, and from now onscanfails with exit 50 if the allow-list grows past 58 entries. ïŒ çŸåšã®ç¯ç®ãåæãæã¯å±¥æŽã§ã¯ãªãçŸåšã®ç¶æ ãªã®ã§ãmanifest/milestone.jsonãšåã PR ã§å€ãããææè 㯠2026-11-13 ã« M2 ãéãããã¡ã€ã«ã¯ M3 ã«ãªã£ããããããã¯èš±å®¹ãªã¹ãã 58 é ç®ãè¶ ãããšscanã¯çµäº 50 ã§å€±æããã 1.10 â 2026-11-13. Learned: a scan line that readsokhas to say what it did not scan: with mandatory sign-in ZAP cannot enterweb, and the report now lists that target as skipped (skipped_targets), not as scanned (PR #56 review r1 R1-01). ïŒokãšèªããæ€æ»ã®è¡ã¯ãæ€æ»ããªãã£ããã®ãèšããªããã°ãªããªããå¿ é ãµã€ã³ã€ã³ã§ã¯ ZAP ã¯webã«å ¥ãããå ±åã¯ãã®å¯Ÿè±¡ãæ€æ»æžã¿ã§ãªã察象å€ïŒskipped_targetsïŒãšããŠèŒããïŒPR #56 ã¬ãã¥ãŒ r1 R1-01ïŒã 1.9 â 2026-11-12. Learned: an upgrade guide has to be an order of commands, because each step needs the one before: the new secrets must exist beforecompose render,compose renderbeforebuild(tags) and again after it, and the search index rebuild only afterup;secrets rotateis not that first step, since it needs a healthy old stack and rolled back here when the former ember image took more than 300 seconds to start. ïŒ ã¢ããã°ã¬ãŒãã®æåŒãã¯ã³ãã³ãã®é åºã§ãªããã°ãªããªããã©ã®æ®µãåã®æ®µãèŠããããã§ãããæ°ããç§å¯ã¯compose renderã®åã«ãcompose renderã¯buildïŒã¿ã°ïŒã®åãšåŸã«ãæ€çŽ¢ã®çŽ¢åŒã®åæ§ç¯ã¯upã®åŸã«èŠããsecrets rotateã¯ãã®æåã®æ®µã§ã¯ãªããå¥åº·ãªæ§ã¹ã¿ãã¯ãèŠããããã§ã¯ä»¥åã® ember ã®ã€ã¡ãŒãžã®èµ·åã 300 ç§ãè¶ ããŠå·»ãæ»ã£ãã 1.8 â 2026-11-11. Learned: a troubleshooting entry that names a workaround goes stale the day the workaround ends: ember-osf-web is built from source again as a static image, so the DEMO-20 cases now say that the prebuilt image was the past state and whatbuilddoes now (RDM-ember-osf-web-dev2027 PR #2 review r1 R1-03). ïŒ åé¿çãåæãããé害察å¿ã®é ã¯ããã®åé¿çãçµãã£ãæ¥ã«å€ããªããember-osf-web ã¯åã³ãœãŒã¹ããéçãªã€ã¡ãŒãžãšããŠçµãŸããã®ã§ãDEMO-20 ã®äºäŸã¯äºåãã«ãæžã¿ã®ã€ã¡ãŒãžãéå»ã®ç¶æ ã ã£ãããšãšãããŸã®buildã®åããæžãããã«ããïŒRDM-ember-osf-web-dev2027 PR #2 ã¬ãã¥ãŒ r1 R1-03ïŒã 1.7 â 2026-11-12. Learned: the guide must not promise what an option cannot do:--timeoutlengthens only the wait ofup, never the build (PR #50 review r1 R2). ïŒ æåŒãã¯ããªãã·ã§ã³ã«ã§ããªãããšãçŽæããŠã¯ãªããªãã--timeoutãå»¶ã°ãã®ã¯upã®åŸ ã¡ã ãã§ããã«ãã§ã¯ãªãïŒPR #50 ã¬ãã¥ãŒ r1 R2ïŒã 1.6 â 2026-11-12. Learned: an amd64 test machine on Apple Silicon is a fully emulated computer, so it needs two more host tools and a long first start, and it compiled osf.io's scientific Python about ten times slower than Rosetta did (a full build there was not finished after 5 h 12 min); the guide now says so and says how to giveupa longer wait through the one command, which does not shorten the build (DEMO-22). ïŒ Apple Silicon äžã® amd64 ã®è©Šéšæ©ã¯å šäœããšãã¥ã¬ãŒã·ã§ã³ããèšç®æ©ãªã®ã§ããã¹ãã®éå ·ãäºã€å€ãèŠããæåã®èµ·åãé·ããosf.io ã®ç§åŠèšç®ã® Python ã®ã³ã³ãã€ã«ã¯ Rosetta ã®çŽ 10 åé ãã£ãïŒããã§ã®ãã«ãå šäœã 5 æé 12 ååŸãæªå®ïŒãæåŒãã¯ãããæžããäžã€ã®ã³ãã³ãã§upã®åŸ ã¡ãå»¶ã°ãæ¹æ³ã瀺ãïŒãã«ãã¯çããªããªãïŒïŒDEMO-22ïŒã 1.5 â 2026-11-10. Learned: a safety check should say what it does not cover: the shared-folder check looks for four names directly under each shared mount point, decoded as the kernel escapes them, not for every credential anywhere (PR #44 review r1 R1). ïŒ å®å šã®ããã®æ€æ»ã¯ãäœãèŠãªãããèšãã¹ãã§ãããå ±æãã©ã«ãã®æ€æ»ã¯ãã«ãŒãã«ã®ãšã¹ã±ãŒãã埩å·ããåå ±æ mount å ã®çŽäžã«ããåã€ã®ååã ããæ¢ããã©ãã«ããè³æ Œæ å ±ã§ãèŠã€ããããã§ã¯ãªãïŒPR #44 ã¬ãã¥ãŒ r1 R1ïŒã 1.4 â 2026-11-10. Learned: a test VM is only isolated if nothing of the host is shared by default: Lima's Ubuntu template mounted the host home and showed~/.config/ghinside the VM, so the Lima steps below share only read-only mirrors andinstall-ubuntu.shstops when credentials are visible (DEMO-21). ïŒ ãã¹ãçšã® VM ã¯ãæ¢å®ã§ãã¹ãã®äœãå ±æããªããšãã ãéé¢ãããŠãããLima ã® Ubuntu ãã³ãã¬ãŒãã¯ããŒã ã mount ã~/.config/ghã VM ããèŠããã®ã§ãäžã® Lima ã®æé ã¯èªã¿åãå°çšã®ãã©ãŒã ããå ±æããinstall-ubuntu.shã¯è³æ Œæ å ±ãèŠãããšæ¢ãŸãïŒDEMO-21ïŒã 1.3 â 2026-11-10. Learned: on a Linux server image the acceptance browser needs two more steps than on a Mac, a library for Playwright's driver and Chromium's system libraries, so §3.9 lists them (DEMO-21). ïŒ Linux ã®ãµãŒããŒã€ã¡ãŒãžã§ã¯åå ¥è©Šéšã®ãã©ãŠã¶ã« Mac ããäºã€å€ãæé ãPlaywright ã®ãã©ã€ããŒçšã®ã©ã€ãã©ãªãš Chromium ã®ã·ã¹ãã ã©ã€ãã©ãªãèŠãã®ã§ã§3.9 ã«èŒããïŒDEMO-21ïŒã - Version / ç: 1.2 â 2026-11-10. Learned: telling a reader that the installer checks each prerequisite is not the same as helping them get one, so the guide now starts from a script for each OS (ADR-08). ïŒ ãã€ã³ã¹ããŒã©ãŒãåææ¡ä»¶ã確èªããããšäŒããããšã¯ããããæããæå©ãã«ã¯ãªããªããããã§æåŒã㯠OS ããšã®ã¹ã¯ãªããããå§ããïŒADR-08ïŒã
- Version / ç: 1.1 â 2026-11-06. Learned: the Project Metadata edit page needs a waffle flag that no setup step turned on, so the legacy startup steps now set
ember_edit_draft_registration_pageonce after the first migration (PR #17); the 2027 installer has no equivalent step yet. ïŒ Project Metadata ã®ç·šéç»é¢ã«ã¯ãã©ã®æé ãæå¹ã«ããŠããªãã£ã waffle ãã©ã°ãå¿ èŠãªãããæ§ã¬ã€ãã®èµ·åæé ã«ååãã€ã°ã¬ãŒã·ã§ã³åŸã®ember_edit_draft_registration_pageèšå®ã远å ããïŒPR #17ïŒã2027 ã€ã³ã¹ããŒã©ãŒã«ã¯çžåœããæé ããŸã ç¡ããšåãã£ãã - Version / ç: 1.0 â 2026-11-06. Learned: full startup is not yet verified by a recorded run: the ember-osf-web (the browser interface) base image is end-of-life and current Docker (the tool that runs containers: boxes that each hold one program and everything it needs) refuses to pull it, so the manifest (the list of components and the exact source revisions they are built from) already configures a digest-pinned prebuilt image for ember-osf-web as a fallback until M4 modernizes its Dockerfile (DEMO-20,
manifest/upstreams.json). ïŒ å®å šãªèµ·åã¯ãŸã å®è¡èšé²ã§æ€èšŒã§ããŠããªããember-osf-webïŒãã©ãŠã¶ç»é¢ïŒã®ããŒã¹ã€ã¡ãŒãžããµããŒãçµäºã§çŸè¡ DockerïŒã³ã³ããïŒäžã€ã®ããã°ã©ã ãšå¿ èŠãªãã®ãå ¥ããç®±ãåããéå ·ïŒãååŸãæããããM4 ã§ Dockerfile ãè¿ä»£åãããŸã§ã®ä»£æ¿ãšããŠãmanifestïŒéšåãšããããçµãæ£ç¢ºãªãœãŒã¹çã®äžèЧïŒã«ã¯ãã€ãžã§ã¹ãåºå®ã®é åžæžã¿ã€ã¡ãŒãžããã§ã«èšå®ãããŠããïŒDEMO-20ãmanifest/upstreams.jsonïŒã - Version / ç: 0.1 â 2026-11-05. Initial bilingual skeleton pointing to the legacy guide. ïŒ æ§ã¬ã€ããæãæåã®äºèšèªã®éªšçµã¿ã
- Normative for:
docs/guides/environment/ - Parent index / 芪玢åŒ: Guides
- Related: SPEC-02 Installer CLI · ADR-02 Network Model · ADR-03 Staged Security Gate · SPEC-03 Security Gate · SPEC-04 Acceptance Tests · SPEC-06 Documentation Conventions · DEMO-20 Core Install on Mac Studio · REF-01 Glossary
- Used by: Guides index · DEMO-20 Core Install on Mac Studio
Install the 2027 developer environment for GakuNin RDM with these three commands:
git clone https://github.com/RCOSDP/RDM-developer-guide.git
cd RDM-developer-guide
./installer/install.sh --yesWhen the installer completes, grdm-dev up opens your browser at the web URL it reports. The default is http://127.0.0.1:5000, but if port (a numbered door a program listens on) 5000 was busy the installer chose another port and recorded it in runtime/.env as GRDM_PORT_WEB; always use the URL or port printed in the report rather than assuming 5000.
Caveat (2026-11-06): a complete startup of the
coreprofile (a named subset of services to run) has not yet been verified by a recorded run. The ember-osf-web Dockerfile cannot be built with current Docker, so the manifest already runs a digest-pinned prebuilt image for that component (see §3.5 and §6). Expect the next recorded run in DEMO-20.
- macOS 14 or newer, Apple Silicon (arm64): Docker Desktop installed
- Ubuntu 24.04, amd64 (the Intel/AMD type of CPU; Apple Silicon is arm64) or arm64: Docker Engine installed
- Windows 11 with WSL2 (Windows Subsystem for Linux 2, a way to run Ubuntu inside Windows; see REF-01) and Ubuntu 24.04: Docker Desktop installed
Note: The installer checks each prerequisite. It exits with code 10 if your host is unsupported and 11 if Docker is missing, not running, or lacks the Compose or buildx (multi-platform image builder) plugin. See SPEC-02 §8 for the full host list.
If your computer does not have the prerequisites yet, run the script for your OS instead of install.sh. Each one shows what it will change, asks before any administrator action, and ends by running install.sh. Add --yes to consent to everything in advance, or --dry-run to only see the plan. Run them from the repository folder.
| OS | Command |
|---|---|
| Ubuntu 24.04 | ./installer/install-ubuntu.sh |
| macOS (Apple Silicon) | ./installer/install-macos.sh |
| Windows 11 (in PowerShell) | powershell -ExecutionPolicy Bypass -File .\installer\install-windows.ps1 |
Expected result: the plan is printed, and after your answer the installer's report ends with the web URL.
On Windows you only need this one script file from the repository. It enables WSL2, installs Ubuntu 24.04, checks Docker Desktop and its WSL integration, and clones the repository inside WSL, never under /mnt/c, because the Windows disk is slow from WSL and changes line endings. Read the script before you run it. -ExecutionPolicy Bypass applies to this one run only.
Note: The integration repositories are private. Before the build, give git your own access where the install runs (inside WSL on Windows), for example
gh auth loginand thengh auth setup-git. The scripts never ask for, read or store a token.
Lima (a tool that runs Linux virtual machines on macOS) is a quick way to test the Ubuntu path on a Mac (DEMO-21).
Warning: Lima's Ubuntu template mounts your home directory into the VM (read-only), even when your configuration lists its own
mounts:, because the template's list is merged in. Your~/.config/gh/hosts.yml, which holds your GitHub token, is then readable inside the VM.install-ubuntu.shstops with exit 10 when one of.config/gh/hosts.yml,.git-credentials,.netrcor.docker/config.jsonexists directly under the mount point of a shared folder. It does not search deeper, so the steps below still matter.
Write the VM configuration, create the VM, then remove the home mount before you start it. Run on the Mac:
limactl create --name grdm-ubuntu2404 --tty=false my-vm.yaml # base: template:ubuntu-24.04, your own mounts
# open ~/.lima/grdm-ubuntu2404/lima.yaml and delete the line - location: "~"
limactl start grdm-ubuntu2404
limactl shell grdm-ubuntu2404 -- mount | grep -E 'virtiofs|9p|sshfs'Expected result: only the folders you chose are listed; no line ends in your home directory.
To test Ubuntu amd64 on an Apple Silicon Mac, set vmType: qemu and arch: x86_64 in my-vm.yaml and run brew install qemu lima-additional-guestagents first (Lima needs QEMU and the amd64 guest agent for this). The whole virtual machine is then emulated, so expect everything to be many times slower than on real hardware, and give the first start a long --timeout. To make the user a non-root user whose uid is not 1000, add user: {name: grdm, uid: 2002, home: /home/grdm} (DEMO-22).
To give the VM the private repositories without a token, share read-only bare mirrors (git clone --mirror on the Mac) and point git at them inside the VM with git config --global url."file:///<mirror>.git".insteadOf https://github.com/RCOSDP/<repo>.git.
Note: Docker Desktop is never installed by these scripts, because its licence depends on your organisation. Homebrew is not installed either;
install-macos.shtells you where to get its signed package. See ADR-08 for the reasons.
The installer creates a self-contained environment under runtime/ with no changes to your host network. It uses two Docker Compose (the tool that starts several containers together from one file) networks:
- Internal network
grdmâ services talk to each other using Compose service names (e.g.,web,api,postgres). No ports are published and there is no route to the Internet. - Publishing network
grdm-edgeâ the seven browser-facing services (web,api,admin,wb,mfr,fakecas,ember_osf_web) also attach here so their ports can be published on127.0.0.1. Because it is an ordinary bridge network, these seven services already have outbound (egress) access; no other service does unless you grant it (§4).
flowchart TD
subgraph HOST["Host computer (macOS / Ubuntu / WSL2)"]
BROWSER["Browser â http://127.0.0.1:GRDM_PORT_WEB"]
subgraph DOCKER["Docker Compose"]
INTERNAL[internal network grdm]
PUBLISHING[public bridge network grdm-edge]
end
end
subgraph SERVICES["Running services"]
web[web (default port 5000)]
api[api (default port 8000)]
postgres[postgres]
rabbitmq[rabbitmq]
end
BROWSER -->|"127.0.0.1:<web port>"| web
web -->|"http://api:8000"| api
api -->|"postgres:5432"| postgres
web -->|"rabbitmq:5672"| rabbitmq
BROWSER --- PUBLISHING
web --- PUBLISHING
api --- PUBLISHING
web --- INTERNAL
api --- INTERNAL
postgres --- INTERNAL
rabbitmq --- INTERNAL
./installer/install.sh --yes creates a Python virtual environment at .venv/ (a venv is a private folder of Python and its libraries, separate from the system), installs grdm-dev into it, and then runs grdm-dev install. That command executes the following steps in this exact order and stops at the first non-zero exit (SPEC-02 §2.1, installer/grdm_dev/install.py):
doctorplansecrets initâ only whenruntime/.envdoes not exist yetcompose renderbuilduphealth --networkscanreport
The acceptance tests (accept, §3.9) are not part of this sequence; run them manually afterwards. The subsections below describe each step so you can also run it on its own after the bootstrap has created .venv/.
Check that your host meets all requirements (run on its own after the bootstrap created .venv/):
.venv/bin/grdm-dev doctorSuccess: You see a TOON report (TOON is a compact text form of JSON data that people and AI read easily; see REF-01) showing your OS, CPU, memory, free disk, and Docker version.
Failure exit codes: 10 â unsupported host (OS, CPU, memory, or Python < 3.11); 11 â Docker missing, not running, or Compose / buildx plugin absent.
See which images will be built and which services will start:
.venv/bin/grdm-dev plan --profile coreA manifest is the list of components and the exact source revisions they are built from (manifest/upstreams.json; see REF-01). A profile is a named subset of services to run: minimum, core (default), or full (SPEC-02 §4). The choice is saved in runtime/.env as GRDM_PROFILE and reused later.
Success: You see a TOON report with the services and their published ports.
Failure exit code: 20 â manifest invalid or TOON excerpt disagrees with JSON.
Generate random secrets and write them to runtime/.env with mode 0600 (owner read/write only):
.venv/bin/grdm-dev secrets initSuccess: A new runtime/.env file appears with random database passwords, Django secret key, and CAS (the sign-in service protocol GRDM uses) keys.
Failure exit code: 2 â usage error (e.g., missing --force if runtime/.env exists).
Security note: The installer never writes default or example passwords. Every secret is generated from your OS's random source.
Generate the Docker Compose file from the manifest and profile:
.venv/bin/grdm-dev compose render --profile coreSuccess (exit 0): runtime/docker-compose.yml appears with all services configured for your host, and any port that had to move away from its default is reported.
Failure exit codes: 20 â manifest invalid; 2 â usage error, for example runtime/.env is missing (run secrets init first) or --egress names an unknown service; 12 â a required port is in use and no free alternative was found within +100 (§6).
Build or pull all images:
.venv/bin/grdm-dev buildSuccess: All images are built or pulled, and a TOON report shows their status (built, prebuilt, ...).
Failure exit code: 30 â image build or prebuilt pull failed (e.g., an EOL base cannot be built for arm64 without emulation). EOL means end of life: the vendor no longer fixes bugs or security holes (REF-01). Emulation means running an linux/amd64 image on an arm64 CPU through Docker's built-in CPU translation; it is slower but works for most images.
Real cases from DEMO-20:
- modular-file-renderer (the file preview service): Built with emulation (
build_platform: linux/amd64) becausepandas==0.25.1has no arm64 wheel (a prebuilt Python package file; without one, pip must compile from source, which fails on this EOL base).- ember-osf-web: At the time, the source build failed on every CPU because the base image used Docker manifest v2 schema 1, which current Docker refuses, so the manifest carried a digest-pinned
prebuilt_imagethatbuildpulled instead (DEMO-20). The Dockerfile has since been modernized (RDM-ember-osf-web-dev2027 PR #2):buildbuilds ember-osf-web from its pinned commit on your own CPU, without emulation, into a static nginx image, and the row saysbuilt.
Start all services and wait for health:
.venv/bin/grdm-dev up --profile coreSuccess: All services report healthy, and the browser opens at the web URL up reports (http://127.0.0.1:<GRDM_PORT_WEB>, default port 5000). Add --no-open to skip the browser.
Failure exit code: 40 â one or more services did not become healthy within the timeout.
Manually check service health:
.venv/bin/grdm-dev health # service responses only
.venv/bin/grdm-dev health --network # also verify that every published port listens on 127.0.0.1 onlySuccess: All services report healthy; with --network, the report also shows loopback_only: true.
Failure exit code: 40 â one or more services are unhealthy; with --network, also when any container port is bound to an address other than 127.0.0.1. Plain health does not check host exposure, so only health --network proves loopback-only publishing. The automatic install sequence runs health --network.
Run the whole security gate of SPEC-03:
.venv/bin/grdm-dev scanWithout flags, scan runs every part: baseline controls, the Trivy (a scanner that lists known weaknesses in images) image scanner's SBOM (software bill of materials: the list of every part inside an image) and CVE list (a CVE is a public identifier for one known security weakness), the gitleaks secret scan, Semgrep (static analysis that reads source code for dangerous patterns), and the OWASP ZAP (a scanner that probes the running website the way an attacker would) dynamic baseline. The flags --baseline, --secrets, and --dynamic each run one part only and are not the whole gate:
.venv/bin/grdm-dev scan --baseline # subset: baseline controls of runtime/docker-compose.yml and runtime/.env only
.venv/bin/grdm-dev scan --secrets # subset: gitleaks over the repository only
.venv/bin/grdm-dev scan --dynamic # subset: OWASP ZAP baseline only (needs healthy services)Gate rule by milestone (manifest/milestone.json, currently M3 since the owner closed M2 on 2026-11-13, so the allow-list may hold at most the M2 count of 58 entries, see the status board; ADR-03, SPEC-03 §5): the gate data â manifest/milestone.json, the allow-list manifest/allowlist.json (the written list of known findings accepted for a limited time) and its baseline manifest/allowlist.baseline.json â must be readable and well-formed at every milestone, M1 included: an unreadable file or an allow-list entry missing one of its six fields exits 50 (SPEC-03 §5.1 rule 1). Baseline-control violations (default secrets, publishing outside loopback, privileged: true, a missing grdm internal network) also exit 50 at every milestone. Only with valid gate data and passing baseline controls are M1âM3 report-only for vulnerability findings: the run exits 0 and records them. From M2 the allow-list may not grow: scan compares the entry count with manifest/allowlist.baseline.json and a larger count exits 50 (at M1 the count is only reported). At M4 any HIGH or CRITICAL finding not in the allow-list exits 50; in addition, passing M4 requires that the first real AI red-team run (authorized attack testing of the isolated environment, SPEC-03 §6) has been completed and every intrusion path it found has been fixed or allow-listed â the red-team preflight (grdm-dev redteam preflight, a readiness check that proves isolation before a run) is not that run. At M5 every CRITICAL or HIGH finding exits 50, allow-listed or not; the allow-list may contain no CRITICAL or HIGH entry (scan exits 50 if it does); and the AI red team must report zero unresolved intrusion paths. scan itself enforces the data validity, baseline, count, and severity rules; the M4 red-team completion and the M5 zero-paths result are milestone acceptance requirements that the owner records with the red-team evidence (SPEC-03 §6â7), not checks scan performs.
Success: Exit 0; the report under runtime/reports/scan_<date>.json (plus TOON) shows the baseline controls passed and the findings for the current milestone.
Failure exit codes: 50 â gate failed for the current milestone (see rule above); 51 â a scanner could not run (Trivy, gitleaks, or Semgrep missing, or its vulnerability database could not be downloaded); 52 â --dynamic was requested while services are unhealthy.
Limit of the dynamic part: with mandatory sign-in (ENABLE_PUBLIC_ACCESS=false, the default) web answers an anonymous request only with a redirect to the sign-in page, which ZAP cannot open. When the scan itself confirms that redirect and that it goes to the configured sign-in address, web is listed under skipped_targets with a note "ZAP NOT RUN on web" and the run can still exit 0; the pages behind sign-in were then not scanned by ZAP. Any other failure to reach a target, such as a redirect elsewhere, stays exit 51.
The acceptance tests (SPEC-04) are not run by install. They need the optional Python extra and a Chromium build in the existing .venv/, installed once:
.venv/bin/pip install -e "installer[accept]"
PLAYWRIGHT_BROWSERS_PATH=.venv/.playwright .venv/bin/playwright install chromiumOn Linux (Ubuntu 24.04) two more commands are needed, both with sudo (DEMO-21). Run this one before the two commands above, because Playwright's driver does not start without it:
sudo apt-get install -y libatomic1and this one after them, to add Chromium's system libraries (it asks for sudo itself):
PLAYWRIGHT_BROWSERS_PATH=.venv/.playwright .venv/bin/playwright install-deps chromiumThen run the tests with --seed, which creates disposable test users, runs the browser scenarios, and removes those users again within the same run (there is no persistent seed step):
.venv/bin/grdm-dev accept --seedSuccess: All tests pass, and a report is written under docs/demo/runs/<run-id>/.
Failure exit codes: 2 â the extra or Chromium is not installed (the message repeats the two commands above); 40 â the integration precheck failed, so the browser tests did not start (fix health first); 60 â one or more tests failed.
Tip:
--only <scenario>runs one scenario;--headedshows the browser window.
.venv/bin/grdm-dev up # start services and wait for health
.venv/bin/grdm-dev down # stop containers, keep volumes
.venv/bin/grdm-dev reset # stop and delete runtime/volumes/Tip: Add
--yesto skip confirmation prompts.
docker compose -f runtime/docker-compose.yml logs -f web apiNote: The generated
runtime/docker-compose.ymluses the service names from the manifest.
.venv/bin/grdm-dev compose render --profile full --yes
.venv/bin/grdm-dev up --yesThe seven publishing services on grdm-edge (web, api, admin, wb, mfr, fakecas, ember_osf_web) already have outbound access to the Internet. Every other service has none by default (ADR-02 §4). --egress adds that access for the services you name, by attaching them to grdm-edge too:
# Requires the full profile (rdmcp and aipf_mcp_data_grdm are not in core); select it first or in the same command.
.venv/bin/grdm-dev compose render --profile full --egress rdmcp,aipf_mcp_data_grdm
.venv/bin/grdm-dev compose render --egress none # clear the saved grantThe choice is saved in runtime/.env as GRDM_EGRESS_SERVICES, kept on later renders, shown by scan --baseline, and cleared with --egress none. Naming a service that is not in the selected profile is a usage error (exit 2).
| Service | Host port | Profile |
|---|---|---|
| web | 5000 | minimum |
| api | 8000 | minimum |
| admin | 8001 | core |
| wb (WaterButler) | 7777 | core |
| mfr (Modular File Renderer) | 7778 | core |
| fakecas | 8080 | minimum |
| ember_osf_web | 4200 | core |
Note: If a port is in use (e.g., macOS AirPlay on 5000),
compose renderfinds the next free port and records it inruntime/.envasGRDM_PORT_<SERVICE>; see §6.
The installer implements these controls from milestone M1 (SPEC-03 §3):
- Secrets: All passwords and keys are generated at install time with random values, written to
runtime/.env(mode0600), and never committed to Git. - Network: Services talk on an internal Compose network (
internal: true). Browser-facing ports are published only on127.0.0.1;health --networkverifies it. - Container hardening: Non-root (the program does not run as the all-powerful administrator user) user, read-only root filesystem, and
cap_drop: [ALL]are the defaults for every service, together with resource limits (memory, CPU, process count).privileged: trueis forbidden everywhere. A service that cannot tolerate one of the defaults (for example the PostgreSQL, RabbitMQ, or Elasticsearch images, which must write inside the image at start-up) gets a documented per-service exception inmanifest/hardening.json, naming the relaxed control, the reason, the review date, and the milestone at which it is to be removed. Read-only roots therefore apply where the service tolerates them, not to every service. - Supply chain: Images are pulled by digest (exact fingerprint), never a floating tag such as
latest. - Sign-in: Since RDM-osf.io-dev2027 PR #8 every data page and API route needs a signed-in user (
ENABLE_PUBLIC_ACCESS=false, the default);grdm-dev compose render --public-access trueturns anonymous viewing of public projects back on. The admin app asks a one-time code after the password (PR #10): an administrator without one is sent to an enrolment page on the first sign-in, and every administrator signs in again after an upgrade. - Search: Elasticsearch 8 is reached over TLS with its own certificate authority and a user limited to the search indices; no port is published (ADR-14).
These are the requirements the installer enforces; whether a given running environment satisfies them is shown by
health --networkandscan, not by this guide.
What the installer does not protect:
- Attacks on your operating system itself (e.g., kernel vulnerabilities)
- Phishing of the developer
- The production GRDM service (this guide is for development only)
compose render starts from the port you requested or the one saved in runtime/.env (GRDM_PORT_<SERVICE>; the SPEC-02 §4 default if neither exists) and searches up to 100 ports above it for a free one. Ports already held by this project's own running containers are kept. If another program holds the port, the service moves to the first free candidate, the choice is recorded as GRDM_PORT_<SERVICE>, and the render reports it. Exit code 12 happens only when no free alternative exists in that range.
Fix: Stop the other program if you want the original port back, or simply use the port compose render / plan reports.
# macOS: AirPlay shares port 5000
sudo lsof -i :5000
# Kill the process if you do not need AirPlaydoctor fails if Docker is not installed, not running, or lacks the Compose plugin.
Fix: Install Docker Desktop (macOS, Windows) or Docker Engine (Ubuntu). Version ⥠27 with Compose v2 plugin is required. On Ubuntu, ./installer/install-ubuntu.sh installs Docker Engine for you.
This happens when an image cannot be built for your CPU architecture or a prebuilt image cannot be pulled.
Real cases from DEMO-20:
- modular-file-renderer on arm64: Built successfully with
build_platform: linux/amd64(emulation) because the base Python 3.5 image has no arm64 wheel forpandas==0.25.1. - ember-osf-web on any platform: The source build failed because the base image used Docker manifest v2 schema 1, which current Docker refuses to pull.
Current state: ember-osf-web no longer uses a prebuilt_image: its modernized Dockerfile (RDM-ember-osf-web-dev2027 PR #2) runs the ember-cli build in a Node stage on your own CPU and produces a static nginx image, so build builds it like the other components (manifest/upstreams.json). That Node stage needs several GiB of Docker engine memory while it runs; if the ember-osf-web build fails with exit 30, check the engine's memory first.
health fails if a service does not respond. health --network additionally fails if any published port listens on an address other than 127.0.0.1; the plain command does not perform that check.
Fix: Check logs with docker compose -f runtime/docker-compose.yml logs <service>, then restart the service. For a non-loopback listener, inspect runtime/docker-compose.yml (every ports: entry must start with 127.0.0.1:) and re-run compose render.
The rows below compare what README.legacy.md actually describes with the 2027 installer.
| Old way (README.legacy.md) | New way (2027 installer) | Why |
|---|---|---|
Configure a loopback alias 192.168.168.167 on the host (needs sudo) so services can reach each other |
Internal network grdm with Compose service names + publishing network grdm-edge on 127.0.0.1 |
No sudo, no host network change, no LAN exposure, same setup on macOS/Ubuntu/WSL2 (ADR-02) |
Copy local-dist.py to local.py for web and api by hand; one URL serves both the browser and the services |
Generated settings separate internal URLs (service names) from external browser URLs (http://127.0.0.1:<port>/) |
Redirects and absolute URLs work from the browser without the alias (ADR-02 §4) |
Hand-written docker-compose.override.yml that swaps images to niicloudoperation/*:latest and carries commented platform: lines per CPU |
grdm-dev compose render generates runtime/docker-compose.yml from the manifest and profile; platform: comes from the manifest's build_platform |
No manual edits, no host-specific file to commit by mistake, same output for everyone |
Start from distribution images (niicloudoperation/*:latest, quay.io/centerforopenscience/*) and install Python/Node modules into volumes with the *_requirements services |
Build from manifest-pinned source revisions; prebuilt images only as documented, digest-pinned exceptions | Exact reproducibility, no floating tags, no stale module volumes |
Uncomment Elasticsearch limits and single-node settings in docker-compose.yml by hand on Apple Silicon |
compose render writes resource limits scaled from doctor and per-service exceptions from manifest/hardening.json |
One generated file instead of per-host edits |
Default credentials shipped by the upstream Compose files (e.g., postgres/postgres; SPEC-03 §3.1) |
Random secrets in runtime/.env (mode 0600), generated by secrets init; scan --baseline fails if a default remains |
No default credentials left behind |
Note: The old instructions are kept verbatim in
README.legacy.mdfor historical reference. The legacy guide itself never documented default passwords; they come from the upstream Compose files it relied on.
- 2026-11-12 â Elasticsearch 8, y-websocket only, mandatory sign-in, admin two-step sign-in (ADR-13 §6, ADR-14). An existing installation upgrades in this order:
git pull;grdm-dev secrets init --missing(addsELASTIC8_PASSWORDandELASTIC8_OSF_PASSWORD, keeps every other value, dropsSHAREJS_SECRET);grdm-dev compose render;grdm-dev build;grdm-dev compose renderagain;grdm-dev up; then oncedocker compose exec web invoke migrate_searchto rebuild the search index from PostgreSQL (the Elasticsearch 2 data is not moved;runtime/volumes/elasticsearch_data,mongo_dataandmongo_tlsare no longer used and can be removed by hand).sharejsandmongoare gone, so port 7007 is no longer published. The first administrator sign-in after the upgrade asks to enrol a one-time code; keep the recovery codes it shows once. - 2026-11-06 â Waffle flag for the Metadata addon (PR #17). The legacy startup steps in
README.legacy.mdnow rundocker compose run --rm web python3 manage.py waffle_flag ember_edit_draft_registration_page --everyoneonce, right after the first database migration, in each of the three startup variants. A waffle flag (a named on/off switch stored in the database that turns a feature on for chosen users) is required to open the Project Metadata edit page of the Metadata addon. The 2027 installer (grdm-dev) does not run this step yet; if you need the Metadata addon, run the samemanage.py waffle_flagcommand against thewebservice by hand. Incorporated from PR #17 by yacchin1205 (2026-11-06).
GakuNin RDM ã® 2027 éçºç°å¢ã以äžã®äžã€ã®ã³ãã³ãã§å°å ¥ããŸãïŒ
git clone https://github.com/RCOSDP/RDM-developer-guide.git
cd RDM-developer-guide
./installer/install.sh --yesã€ã³ã¹ããŒã©ãŒãå®äºãããšãgrdm-dev up ãå ±åãã web ã® URL ããã©ãŠã¶ã§éããŸããæ¢å®ã¯ http://127.0.0.1:5000 ã§ãããããŒãïŒããã°ã©ã ãåŸ
ã¡åããçªå·ä»ãã®å
¥å£ïŒ5000 ã䜿çšäžã ã£ãå Žåã¯ã€ã³ã¹ããŒã©ãŒãå¥ã®ããŒããéžã³ãruntime/.env ã« GRDM_PORT_WEB ãšããŠèšé²ããŠããŸãã5000 ãšæ±ºãã€ãããå¿
ãå ±åã«è¡šç€ºããã URL ãŸãã¯ããŒãã䜿ã£ãŠãã ããã
泚æïŒ2026-11-06 æç¹ïŒ:
coreãããã¡ã€ã«ïŒèµ·åãããµãŒãã¹ã®ååä»ãã®çµïŒã®å®å šãªèµ·åã¯ããŸã å®è¡èšé²ã§æ€èšŒã§ããŠããŸãããember-osf-web ã® Dockerfile ã¯çŸè¡ Docker ã§ã¯çµããªããããmanifest ã¯ãã®éšåã«ã€ããŠãã€ãžã§ã¹ãåºå®ã®é åžæžã¿ã€ã¡ãŒãžããã§ã«äœ¿ãèšå®ã«ãªã£ãŠããŸãïŒÂ§3.5ã»Â§6ïŒã次ã®å®è¡èšé²ã¯ DEMO-20 ã«è¿œèšãããŸãã
- macOS 14 以äžãApple Silicon (arm64): Docker Desktop ãã€ã³ã¹ããŒã«æžã¿
- Ubuntu 24.04ãamd64ïŒIntel/AMD 系㮠CPU ã®çš®é¡ãApple Silicon 㯠arm64ïŒãŸã㯠arm64: Docker Engine ãã€ã³ã¹ããŒã«æžã¿
- Windows 11 + WSL2ïŒWindows Subsystem for Linux 2ãWindows ã®äžã§ Ubuntu ãåããä»çµã¿ãREF-01ïŒã® Ubuntu 24.04: Docker Desktop ãã€ã³ã¹ããŒã«æžã¿
Note: ã€ã³ã¹ããŒã©ãŒã¯ååææ¡ä»¶ã確èªããŸãããã¹ããæªå¯Ÿå¿ãªãçµäºã³ãŒã 10ãDocker ãç¡ãã»åããŠããªãã»Compose ã buildxïŒè€æ° CPU åãã€ã¡ãŒãžãäœãæ©èœïŒãã©ã°ã€ã³ãç¡ããªã 11 ã§çµãããŸãã察å¿ãã¹ãã®äžèŠ§ã¯ SPEC-02 §8 ãåç §ã
åææ¡ä»¶ããŸã æã£ãŠããªãã³ã³ãã¥ãŒã¿ã§ã¯ãinstall.sh ã®ä»£ããã« OS ã«åã£ãã¹ã¯ãªãããå®è¡ããŸããã©ãã倿Žç¹ã瀺ãã管çè
ã®æäœã®åã«å°ããæåŸã« install.sh ãå®è¡ããŸãã--yes ãä»ãããšå
ã«ãã¹ãŠåæãã--dry-run ãä»ãããšäºå®ãèŠãã ãã§ãããªããžããªã®ãã©ã«ãã§å®è¡ããŸãã
| OS | ã³ãã³ã |
|---|---|
| Ubuntu 24.04 | ./installer/install-ubuntu.sh |
| macOSïŒApple SiliconïŒ | ./installer/install-macos.sh |
| Windows 11ïŒPowerShell ã§ïŒ | powershell -ExecutionPolicy Bypass -File .\installer\install-windows.ps1 |
æåŸ ããçµæ: äºå®ã衚瀺ãããçããåŸã«ã€ã³ã¹ããŒã©ãŒã®å ±åã web ã® URL ã§çµãããŸãã
Windows ã§å¿
èŠãªã®ã¯ããªããžããªã®ãã®ã¹ã¯ãªãããã¡ã€ã«äžã€ã ãã§ããWSL2 ãæå¹ã«ããUbuntu 24.04 ãå
¥ããDocker Desktop ãš WSL 飿ºã確èªãããªããžããªã WSL ã®äžã« clone ããŸããWindows ã®ãã£ã¹ã¯ã¯ WSL ããé
ãæ¹è¡ãå€ããã®ã§ã/mnt/c ã®äžã«ã¯æ±ºããŠçœ®ããŸãããå®è¡ããåã«ã¹ã¯ãªãããèªãã§ãã ããã-ExecutionPolicy Bypass ã¯ãã®äžåã®å®è¡ã ãã«å¹ããŸãã
Note: çµ±åãªããžããªã¯éå ¬éã§ãããã«ãã®åã«ãå°å ¥ãå®è¡ããå ŽæïŒWindows ã§ã¯ WSL ã®äžïŒã§ git ã«èªåã®æš©éãèšå®ããŠãã ãããäŸ:
gh auth loginã®åŸã«gh auth setup-gitãã¹ã¯ãªããã¯ããŒã¯ã³ãå°ãããèªãŸããä¿åããŸããã
LimaïŒmacOS ã§ Linux ã®ä»®æ³ãã·ã³ãåããéå ·ïŒã䜿ããšãMac ã§ Ubuntu ã®æé ãææ©ã詊ããŸãïŒDEMO-21ïŒã
Warning: Lima ã® Ubuntu ãã³ãã¬ãŒãã¯ãèšå®ã«ç¬èªã®
mounts:ãæžããŠãäžèЧã䜵åããããããããŒã ãã£ã¬ã¯ããªã VM ã«ïŒèªã¿åãå°çšã§ïŒmount ããŸãããããš GitHub ã®ããŒã¯ã³ãæã€~/.config/gh/hosts.ymlã VM ã®äžããèªããŸããinstall-ubuntu.shã¯ãå ±æãã©ã«ãã® mount å ã®çŽäžã«.config/gh/hosts.ymlã».git-credentialsã».netrcã».docker/config.jsonã®ã©ããããããšçµäº 10 ã§æ¢ãŸããŸããããããæ·±ãã¯æ¢ããªãã®ã§ãäžã®æé ã¯ãã¯ãå¿ èŠã§ãã
VM ã®èšå®ãæžã㊠VM ãäœããèµ·åããåã«ããŒã ã® mount ãå€ããŸããMac ã§å®è¡ããŸãïŒ
limactl create --name grdm-ubuntu2404 --tty=false my-vm.yaml # base: template:ubuntu-24.04 ãšç¬èªã® mounts
# ~/.lima/grdm-ubuntu2404/lima.yaml ãéãã - location: "~" ã®è¡ãæ¶ã
limactl start grdm-ubuntu2404
limactl shell grdm-ubuntu2404 -- mount | grep -E 'virtiofs|9p|sshfs'æåŸ ããçµæ: èªåã§éžãã ãã©ã«ãã ãã衚瀺ãããããŒã ãã£ã¬ã¯ããªã§çµããè¡ã¯ãããŸããã
Apple Silicon ã® Mac ã§ Ubuntu amd64 ã詊ãã«ã¯ãmy-vm.yaml ã« vmType: qemu ãš arch: x86_64 ãæžããå
ã« brew install qemu lima-additional-guestagents ãå®è¡ããŸãïŒLima ã¯ãã®ããã« QEMU ãš amd64 ã®ã²ã¹ããšãŒãžã§ã³ãã䜿ããŸãïŒãä»®æ³ãã·ã³å
šäœããšãã¥ã¬ãŒã·ã§ã³ããã®ã§ã宿©ãããã£ãšé
ããæåã®èµ·åã® --timeout ã¯é·ãããŸããuid ã 1000 ã§ãªãäžè¬å©çšè
ã«ããã«ã¯ user: {name: grdm, uid: 2002, home: /home/grdm} ãè¶³ããŸãïŒDEMO-22ïŒã
ããŒã¯ã³ç¡ãã§ VM ã«éå
¬éãªããžããªãæž¡ãã«ã¯ãèªã¿åãå°çšã® bare ãã©ãŒïŒMac ã§ git clone --mirrorïŒãå
±æããVM ã®äžã§ git config --global url."file:///<ãã©ãŒ>.git".insteadOf https://github.com/RCOSDP/<ãªããžããª>.git ãšã㊠git ããããžåããŸãã
Note: ãããã®ã¹ã¯ãªãã㯠Docker Desktop ãå ¥ããŸãããã©ã€ã»ã³ã¹ãæå±çµç¹ã«ããããã§ããHomebrew ãå ¥ããŸããã
install-macos.shã眲åä»ãããã±ãŒãžã®å ¥æå ãæ¡å ããŸããçç±ã¯ ADR-08 ã«ãããŸãã
ã€ã³ã¹ããŒã©ãŒã¯ãã¹ãã®ãããã¯ãŒã¯èšå®ãäžåå€ãããruntime/ ã®äžã«èªå·±å®çµåã®ç°å¢ãäœããŸããäºã€ã® Docker ComposeïŒäžã€ã®èšå®ãã¡ã€ã«ããè€æ°ã®ã³ã³ããããŸãšããŠèµ·ããéå
·ïŒãããã¯ãŒã¯ã䜿ããŸãïŒ
- å
éšãããã¯ãŒã¯
grdmâ ãµãŒãã¹é㯠Compose ã®ãµãŒãã¹åïŒäŸ:web,api,postgresïŒã§éä¿¡ããŸããããŒãã¯å ¬éããããã€ã³ã¿ãŒããããžã®çµè·¯ããããŸããã - å
¬éãããã¯ãŒã¯
grdm-edgeâ ãã©ãŠã¶ãå±ãå¿ èŠã®ãã 7 ãµãŒãã¹ïŒweb,api,admin,wb,mfr,fakecas,ember_osf_webïŒãããã«ãæ¥ç¶ãã127.0.0.1ã«ããŒããå ¬éããŸããéåžžã® bridge ãããã¯ãŒã¯ãªã®ã§ããã® 7 ãµãŒãã¹ã¯å€åãéä¿¡ïŒegressïŒããã§ã«å¯èœã§ãããã以å€ã®ãµãŒãã¹ã¯ãæç€ºçã«ä»äžããªãéãå€åãéä¿¡ãæã¡ãŸããïŒÂ§4ïŒã
flowchart TD
subgraph HOST["ãã¹ãïŒmacOS / Ubuntu / WSL2ïŒ"]
BROWSER["ãã©ãŠã¶ â http://127.0.0.1:GRDM_PORT_WEB"]
subgraph DOCKER["Docker Compose"]
INTERNAL[å
éšãããã¯ãŒã¯ grdm]
PUBLISHING[éåžž bridge ãããã¯ãŒã¯ grdm-edge]
end
end
subgraph SERVICES["皌åäžã®ãµãŒãã¹"]
web[webïŒæ¢å®ããŒã 5000ïŒ]
api[apiïŒæ¢å®ããŒã 8000ïŒ]
postgres[postgres]
rabbitmq[rabbitmq]
end
BROWSER -->|"127.0.0.1:<web ããŒã>"| web
web -->|"http://api:8000"| api
api -->|"postgres:5432"| postgres
web -->|"rabbitmq:5672"| rabbitmq
BROWSER --- PUBLISHING
web --- PUBLISHING
api --- PUBLISHING
web --- INTERNAL
api --- INTERNAL
postgres --- INTERNAL
rabbitmq --- INTERNAL
./installer/install.sh --yes 㯠.venv/ ã« Python ã®ä»®æ³ç°å¢ïŒvenvãã·ã¹ãã ãšã¯å¥ã®ãPython ãšã©ã€ãã©ãªã ãã®ç§çšãã©ã«ãïŒãäœãããããž grdm-dev ãã€ã³ã¹ããŒã«ããŠãã grdm-dev install ãå®è¡ããŸãããã®ã³ãã³ãã¯æ¬¡ã®æé ããã®é çªã©ããã«å®è¡ããæåã« 0 以å€ã§çµãã£ãæ®µã§æ¢ãŸããŸãïŒSPEC-02 §2.1ãinstaller/grdm_dev/install.pyïŒïŒ
doctorplansecrets initâruntime/.envããŸã ç¡ããšãã ãcompose renderbuilduphealth --networkscanreport
åå
¥è©ŠéšïŒacceptã§3.9ïŒã¯ãã®èªåæé ã«å«ãŸããŸãããå°å
¥åŸã«æåã§å®è¡ããŸãã以äžã®åç¯ã¯åæé ã®èª¬æã§ãåææºåã .venv/ ãäœã£ãåŸãªãåç¬ã§ãå®è¡ã§ããŸãã
ãã¹ãããã¹ãŠã®åææ¡ä»¶ãæºããã確èªããŸãïŒåææºåã§ .venv/ ãã§ããåŸã«åç¬ã§å®è¡ïŒïŒ
.venv/bin/grdm-dev doctoræå: OSãCPUãã¡ã¢ãªã空ã容éãDocker ã®ããŒãžã§ã³ã TOONïŒJSON ã®ããŒã¿ãçãæžããããã¹ã圢åŒã人ã«ã AI ã«ãèªã¿ããããREF-01ïŒã§è¡šç€ºããŸãã
倱æçµäºã³ãŒã: 10 â 察å¿å€ã®ãã¹ãïŒOSã»CPUã»ã¡ã¢ãªããŸã㯠Python < 3.11ïŒã11 â Docker ãç¡ããåããŠããªãããŸã㯠Compose / buildx ãã©ã°ã€ã³ãç¡ãã
ã©ã®ã€ã¡ãŒãžãäœããã©ã®ãµãŒãã¹ãèµ·åããã確èªããŸãïŒ
.venv/bin/grdm-dev plan --profile coremanifestïŒãããã§ã¹ãïŒã¯ãã©ã®éšåãã©ã®æ£ç¢ºãªãœãŒã¹çããçµããã®äžèЧã§ãïŒmanifest/upstreams.jsonãREF-01ïŒããããã¡ã€ã«ã¯èµ·åãããµãŒãã¹ã®ååä»ãã®çµã§ãminimumã»coreïŒæ¢å®ïŒã»full ããããŸãïŒSPEC-02 §4ïŒãéžæã¯ runtime/.env ã« GRDM_PROFILE ãšããŠä¿åãããæ¬¡å以éã䜿ãããŸãã
æå: ãµãŒãã¹ãšå ¬éããŒãã® TOON ã¬ããŒãã衚瀺ãããŸãã
倱æçµäºã³ãŒã: 20 â manifest ãäžæ£ããŸã㯠TOON ã®æé²ã JSON ãšäžèŽããªãã
ä¹±æ°ã®ç§å¯ãçæããã¢ãŒã 0600ïŒææè
ã®ã¿èªã¿æžãå¯ïŒã§ runtime/.env ã«æžããŸãïŒ
.venv/bin/grdm-dev secrets initæå: runtime/.env ãä¹±æ°ã®ããŒã¿ããŒã¹ãã¹ã¯ãŒããDjango ã®ç§å¯éµãCASïŒGRDM ã䜿ããµã€ã³ã€ã³ã®ä»çµã¿ïŒã®éµã§çæãããŸãã
倱æçµäºã³ãŒã: 2 â äœ¿çšæ³ã®èª€ãïŒäŸ: runtime/.env ãããã®ã« --force ãè¶³ããªãïŒã
Security note: ã€ã³ã¹ããŒã©ãŒã¯ 決ã㊠æ¢å®å€ãäŸã®ãã¹ã¯ãŒããæžããŸããããã¹ãŠã®ç§å¯ã¯ OS ã®ä¹±æ°æºããçæãããŸãã
manifest ãšãããã¡ã€ã«ãã Docker Compose ãã¡ã€ã«ãçæããŸãïŒ
.venv/bin/grdm-dev compose render --profile coreæåïŒçµäºã³ãŒã 0ïŒ: runtime/docker-compose.yml ããã¹ãã«åãããŠèšå®ããããµãŒãã¹ã§çæãããæ¢å®ããç§»åããããŒããããã°å ±åãããŸãã
倱æçµäºã³ãŒã: 20 â manifest ãäžæ£ã2 â äœ¿çšæ³ã®èª€ãïŒäŸ: runtime/.env ãç¡ãïŒå
ã« secrets init ãå®è¡ïŒã--egress ã«ç¥ããªããµãŒãã¹åãæå®ïŒã12 â å¿
èŠãªããŒãã䜿çšäžã§ã+100 ã®ç¯å²ã«ç©ºãã®ä»£æ¿ãç¡ãïŒÂ§6ïŒã
ãã¹ãŠã®ã€ã¡ãŒãžããã«ããŸãã¯ååŸããŸãïŒ
.venv/bin/grdm-dev buildæå: å
šã€ã¡ãŒãžããã«ããŸãã¯ååŸãããTOON ã¬ããŒãã«ãã®ç¶æ
ïŒbuiltãprebuilt ãªã©ïŒã衚瀺ãããŸãã
倱æçµäºã³ãŒã: 30 â ã€ã¡ãŒãžã®ãã«ããŸãã¯é
åžæžã¿ã€ã¡ãŒãžã®ååŸã«å€±æïŒäŸ: EOL ããŒã¹ã arm64 ã§ãšãã¥ã¬ãŒã·ã§ã³ãªãã«çµããªãïŒãEOL 㯠end of lifeãã€ãŸãäœã£ã人ããã°ã穎ãçŽããŠãããªããªã£ãç¶æ
ã§ãïŒREF-01ïŒããšãã¥ã¬ãŒã·ã§ã³ã¯ Docker å
èµã® CPU å€æã§ linux/amd64 ã®ã€ã¡ãŒãžã arm64 ã® CPU äžã§åããããšã§ãé
ããªããŸããå€ãã®ã€ã¡ãŒãžã§åããŸãã
DEMO-20 ã®å®éã®ã±ãŒã¹:
- modular-file-rendererïŒãã¡ã€ã«ã®ãã¬ãã¥ãŒãäœããµãŒãã¹ïŒ:
pandas==0.25.1ã® arm64 wheelïŒãã«ãæžã¿ã® Python ããã±ãŒãžãã¡ã€ã«ãç¡ããš pip ããœãŒã¹ããçµãå¿ èŠãããããã® EOL ããŒã¹ã§ã¯å€±æããïŒãååšããªããããbuild_platform: linux/amd64ïŒãšãã¥ã¬ãŒã·ã§ã³ïŒã§æ£åžžã«ãã«ãã- ember-osf-web: åœæã¯ãããŒã¹ã€ã¡ãŒãžãçŸè¡ Docker ã®æåŠãã Docker manifest v2 schema 1 ã䜿ã£ãŠããããããœãŒã¹ããã®ãã«ãã¯ã©ã® CPU ã§ã倱æããmanifest ã«ã¯ãã€ãžã§ã¹ãåºå®ã®
prebuilt_imageãèšå®ããŠbuildããã«ãã®ä»£ããã«ãããååŸããŠããŸããïŒDEMO-20ïŒããã®åŸ Dockerfile ã¯è¿ä»£åãããŸããïŒRDM-ember-osf-web-dev2027 PR #2ïŒãããŸã®build㯠ember-osf-web ãåºå®ã³ãããããã䜿ãã® CPU äžã§ãšãã¥ã¬ãŒã·ã§ã³ãªãã«éç㪠nginx ã®ã€ã¡ãŒãžãžçµã¿ãè¡ã¯builtã«ãªããŸãã
å šãµãŒãã¹ãèµ·åããå¥åº·ã«ãªããŸã§åŸ ã¡ãŸãïŒ
.venv/bin/grdm-dev up --profile coreæå: å
šãµãŒãã¹ãå¥åº·ãšå ±åããup ãå ±åãã web ã® URLïŒhttp://127.0.0.1:<GRDM_PORT_WEB>ãæ¢å®ããŒã 5000ïŒã§ãã©ãŠã¶ãéããŸãããã©ãŠã¶ãéããªããªã --no-open ãä»ããŸãã
倱æçµäºã³ãŒã: 40 â äžã€ä»¥äžã®ãµãŒãã¹ãå¶éæéå
ã«å¥åº·ã«ãªããªãã£ãã
æåã§ãµãŒãã¹ã®å¥åº·ã確èªããŸãïŒ
.venv/bin/grdm-dev health # ãµãŒãã¹ã®å¿çã®ã¿
.venv/bin/grdm-dev health --network # å ããŠãå
¬éããŒãããã¹ãŠ 127.0.0.1 ã ãã§åŸ
ã¡åããŠãããæ€èšŒæå: å
šãµãŒãã¹ãå¥åº·ãšå ±åããŸãã--network ä»ããªãå ±åã« loopback_only: true ã衚瀺ãããŸãã
倱æçµäºã³ãŒã: 40 â äžã€ä»¥äžã®ãµãŒãã¹ãäžå¥åº·ã--network ä»ããªããã³ã³ããã®ããŒãã 127.0.0.1 以å€ã®ã¢ãã¬ã¹ã«çµã³ä»ããŠããå Žåããéåžžã® health ã¯ãã¹ããžã®é²åºãæ€æ»ããªããããã«ãŒãããã¯éå®å
¬éã蚌æã§ããã®ã¯ health --network ã ãã§ããèªåã® install æé 㯠health --network ãå®è¡ããŸãã
SPEC-03 ã®ã»ãã¥ãªãã£éãå šéšåãããŸãïŒ
.venv/bin/grdm-dev scanãã©ã°ãªãã® scan ã¯ãã¹ãŠã®éšåãå®è¡ããŸããåºæ¬å¯ŸçãTrivyïŒã€ã¡ãŒãžã®äžã®æ¢ç¥ã®åŒ±ç¹ãäžèЧã«ããã¹ãã£ããŒïŒã® SBOMïŒãœãããŠã§ã¢éšå衚ãã€ã¡ãŒãžã«å
¥ã£ãŠããéšåã®äžèЧïŒãš CVE äžèЧïŒCVE ã¯æ¢ç¥ã®åŒ±ç¹äžã€ã«ä»ãå
¬éçªå·ïŒãgitleaks ã®ç§å¯æ€æ»ãSemgrepïŒãœãŒã¹ã³ãŒãããå±éºãªãã¿ãŒã³ãæ¢ãéçè§£æïŒãOWASP ZAP ã®åçæ€æ»ïŒæ»æè
ã®ããã«çšŒåäžã®ãµã€ãã調ã¹ãéå
·ïŒã§ãã--baselineã»--secretsã»--dynamic ã¯ããããäžéšåã ããåããé宿€æ»ã§ãå
𿀿»ã§ã¯ãããŸããïŒ
.venv/bin/grdm-dev scan --baseline # éå®: runtime/docker-compose.yml ãš runtime/.env ã®åºæ¬å¯Ÿçã®ã¿
.venv/bin/grdm-dev scan --secrets # éå®: ãªããžããªã«å¯Ÿãã gitleaks ã®ã¿
.venv/bin/grdm-dev scan --dynamic # éå®: OWASP ZAP ã® baseline ã®ã¿ïŒå¥åº·ãªãµãŒãã¹ãå¿
èŠïŒç¯ç®ããšã®éã®èŠåïŒmanifest/milestone.jsonãçŸåšã¯ M3ãææè
ã 2026-11-13 ã« M2 ãéããã®ã§ã蚱容ãªã¹ã㯠M2 ã®ä»¶æ° 58 é
ç®ãŸã§ããæãŠãªãã鲿ããŒããåç
§ãADR-03ãSPEC-03 §5ïŒ: éã®ããŒã¿ãããªãã¡ manifest/milestone.jsonã蚱容ãªã¹ã manifest/allowlist.jsonïŒç¥ã£ãŠããŠæéä»ãã§åãå
¥ããæ€åºãæžããäžèЧïŒãšãã®åºæº manifest/allowlist.baseline.json ã¯ãM1 ãå«ãã©ã®ç¯ç®ã§ãèªããŠåœ¢ãæ£ãããªããã°ãªããªããèªããªããã¡ã€ã«ããå
ã€ã®æ¬ã®ã©ãããæ¬ ãã蚱容ãªã¹ãé
ç®ã¯çµäº 50ïŒSPEC-03 §5.1 第1é
ïŒãåºæ¬å¯Ÿçã®éåïŒæ¢å®ã®ç§å¯ãã«ãŒãããã¯ä»¥å€ãžã®å
¬éãprivileged: trueãå
éšãããã¯ãŒã¯ grdm ã®æ¬ èœïŒãã©ã®ç¯ç®ã§ãçµäº 50ãéã®ããŒã¿ãæå¹ã§åºæ¬å¯Ÿçã«åæ Œããå Žåã«éããM1ãM3 ã§ã¯è匱æ§ã®ææã¯å ±åã®ã¿ïŒçµäº 0 ã§èšé²ããïŒãM2 ããã¯èš±å®¹ãªã¹ããå¢ãããŠã¯ãªããªããscan ã¯é
ç®æ°ã manifest/allowlist.baseline.json ãšæ¯ã¹ãå¢ããŠããã°çµäº 50ïŒM1 ã§ã¯ä»¶æ°ãå ±åããã ãïŒãM4 ã§ã¯èš±å®¹ãªã¹ãã«ãªã HIGH ãŸã㯠CRITICAL ã®ææãäžä»¶ã§ãããã°çµäº 50ãå ã㊠M4 ã®åæ Œã«ã¯ãååã®å®éã® AI ã¬ããããŒã ïŒéé¢ç°å¢ã«å¯ŸããŠèš±å¯ãåããŠè¡ãæ»ææ€èšŒãSPEC-03 §6ïŒãå®äºããèŠã€ãã£ã䟵å
¥çµè·¯ããã¹ãŠä¿®æ£ã蚱容ãªã¹ãç»é²ããŠããããšãå¿
èŠã§ãã¬ããããŒã ã®äºå確èªïŒgrdm-dev redteam preflightã宿œåã«éé¢ã蚌æããæºåã®æ€æ»ïŒã¯ãã®å®æ€èšŒã§ã¯ãªããM5 ã§ã¯ CRITICAL ã HIGH ã®ææã¯èš±å®¹ãªã¹ãã«ãã£ãŠãäžä»¶ã§çµäº 50ã蚱容ãªã¹ãã« CRITICALã»HIGH ã®é
ç®ããã£ãŠã¯ãªããïŒããã° scan ã¯çµäº 50ïŒãAI ã¬ããããŒã ãæªè§£æ±ºã®äŸµå
¥çµè·¯ãŒããå ±åããªããã°ãªããªããscan èªèº«ã匷å¶ããã®ã¯ããŒã¿æå¹æ§ã»åºæ¬å¯Ÿçã»ä»¶æ°ã»é倧床ã®èŠåã§ãããM4 ã®ã¬ããããŒã å®äºãš M5 ã®çµè·¯ãŒãã¯ãææè
ãã¬ããããŒã ã®èšŒè·¡ãšãšãã«èšé²ããç¯ç®ã®åå
¥æ¡ä»¶ã§ïŒSPEC-03 §6â7ïŒãscan ãæ€æ»ãããã®ã§ã¯ãªãã
æå: çµäº 0ãruntime/reports/scan_<æ¥ä»>.jsonïŒãš TOONïŒã®å ±åã«ãåºæ¬å¯Ÿçã®åæ ŒãšçŸåšã®ç¯ç®ã§ã®ææã瀺ãããŸãã
倱æçµäºã³ãŒã: 50 â çŸåšã®ç¯ç®ã§éã«èœã¡ãïŒäžã®èŠåïŒã51 â ã¹ãã£ããŒãåãããªãïŒTrivyã»gitleaksã»Semgrep ãç¡ãããŸãã¯è匱æ§ããŒã¿ããŒã¹ãååŸã§ããªãïŒã52 â ãµãŒãã¹ãå¥åº·ã§ãªãã®ã« --dynamic ãæ±ããã
åçéšåã®éç: å¿
é ãµã€ã³ã€ã³ïŒENABLE_PUBLIC_ACCESS=falseãæ¢å®ïŒã§ã¯ãweb ã¯å¿åã®èŠæ±ã«ãµã€ã³ã€ã³ã®ããŒãžãžã®è»¢éããè¿ãããZAP ã¯ãããéããŸãããã¹ãã£ã³èªèº«ããã®è»¢éã確ããã転éå
ãèšå®æžã¿ã®ãµã€ã³ã€ã³ã®ã¢ãã¬ã¹ã§ãããšãã ããweb ã¯æ³šãZAP NOT RUN on webãã€ãã§ skipped_targets ã«èŒããçµäº 0 ã«ãªãããŸãããã®ãšããµã€ã³ã€ã³ã®åããã®ããŒãžã¯ ZAP ã§ã¯æ€æ»ãããŠããŸããã転éå
ãå¥ã®å Žæã§ãããªã©ã察象ã«å±ããªãã»ãã®å€±æã¯çµäº 51 ã®ãŸãŸã§ãã
åå
¥è©ŠéšïŒSPEC-04ïŒã¯ install ã§ã¯å®è¡ãããŸãããæ¢åã® .venv/ ã«ãä»»æã® Python 远å äŸåãš Chromium ãäžåºŠã ãæºåããŸãïŒ
.venv/bin/pip install -e "installer[accept]"
PLAYWRIGHT_BROWSERS_PATH=.venv/.playwright .venv/bin/playwright install chromiumLinuxïŒUbuntu 24.04ïŒã§ã¯ãsudo ã䜿ãã³ãã³ããããšäºã€èŠããŸãïŒDEMO-21ïŒã次ã®ã³ãã³ãã¯äžã®äºã€ã®åã«å®è¡ããŸãããããç¡ããš Playwright ã®ãã©ã€ããŒãèµ·åããŸããïŒ
sudo apt-get install -y libatomic1次ã®ã³ãã³ãã¯äžã®äºã€ã®åŸã«å®è¡ããChromium ã®ã·ã¹ãã ã©ã€ãã©ãªãå
¥ããŸãïŒèªåã§ sudo ãæ±ããŸãïŒïŒ
PLAYWRIGHT_BROWSERS_PATH=.venv/.playwright .venv/bin/playwright install-deps chromium次㫠--seed ãä»ããŠè©Šéšãå®è¡ããŸãã--seed ã¯äœ¿ãæšãŠã®è©Šéšå©çšè
ãäœæãããã©ãŠã¶ã®ã·ããªãªãå®è¡ããåãäžåã®å®è¡ã®äžã§ãã®å©çšè
ãåé€ããŸãïŒäºåã«å¥éãã·ãŒããããŠããæé ã¯ãããŸããïŒïŒ
.venv/bin/grdm-dev accept --seedæå: å
šè©Šéšãåæ Œããdocs/demo/runs/<run-id>/ ã«å ±åãæžãããŸãã
倱æçµäºã³ãŒã: 2 â 远å äŸåãŸã㯠Chromium ãæªæºåïŒã¡ãã»ãŒãžã«äžã®äºã€ã®ã³ãã³ãã衚瀺ãããïŒã40 â çµ±åã®äºå確èªã«å€±æãããã©ãŠã¶è©Šéšãéå§ããªãã£ãïŒå
ã« health ãçŽãïŒã60 â äžä»¶ä»¥äžã®è©Šéšã倱æããã
Tip:
--only <ã·ããªãª>ã§äžã€ã ãå®è¡ã--headedã§ãã©ãŠã¶ã®ç»é¢ã衚瀺ããŸãã
.venv/bin/grdm-dev up # ãµãŒãã¹èµ·åãå¥åº·ã«ãªããŸã§åŸ
ã€
.venv/bin/grdm-dev down # ã³ã³ãã忢ãããªã¥ãŒã ãæ®ã
.venv/bin/grdm-dev reset # 忢ã runtime/volumes/ ãåé€Tip: 確èªããã³ãããçãã«ã¯
--yesã远å ã
docker compose -f runtime/docker-compose.yml logs -f web apiNote: çæããã
runtime/docker-compose.yml㯠manifest ã®ãµãŒãã¹åã䜿ããŸãã
.venv/bin/grdm-dev compose render --profile full --yes
.venv/bin/grdm-dev up --yesgrdm-edge äžã®å
¬éãµãŒãã¹ 7 çš®ïŒweb, api, admin, wb, mfr, fakecas, ember_osf_webïŒã¯ãã€ã³ã¿ãŒããããžã®å€åãéä¿¡ããã§ã«å¯èœã§ãããã以å€ã®ãµãŒãã¹ã¯æ¢å®ã§ã¯æã¡ãŸããïŒADR-02 §4ïŒã--egress ã¯æå®ãããµãŒãã¹ã grdm-edge ã«ãæ¥ç¶ããŠããã®å€åãéä¿¡ã远å ããŸãïŒ
# full ãããã¡ã€ã«ãåæïŒrdmcp ãš aipf_mcp_data_grdm 㯠core ã«å«ãŸããªãïŒãå
ã«éžã¶ããåãã³ãã³ãã§æå®ããã
.venv/bin/grdm-dev compose render --profile full --egress rdmcp,aipf_mcp_data_grdm
.venv/bin/grdm-dev compose render --egress none # ä¿åããä»äžãæ¶ãéžæã¯ runtime/.env ã® GRDM_EGRESS_SERVICES ã«ä¿åããã以éã® render ã§ãç¶æãããscan --baseline ã®å ±åã«è¡šç€ºããã--egress none ã§æ¶å»ãããŸããéžæäžã®ãããã¡ã€ã«ã«ç¡ããµãŒãã¹åãæå®ãããšäœ¿çšæ³ã®èª€ãïŒçµäº 2ïŒã§ãã
| ãµãŒãã¹ | ãã¹ãåŽããŒã | ãããã¡ã€ã« |
|---|---|---|
| web | 5000 | minimum |
| api | 8000 | minimum |
| admin | 8001 | core |
| wb (WaterButler) | 7777 | core |
| mfr (Modular File Renderer) | 7778 | core |
| fakecas | 8080 | minimum |
| ember_osf_web | 4200 | core |
Note: ããŒãã䜿çšäžãªãïŒäŸ: macOS ã® AirPlay ãš 5000ïŒã
compose renderãæ¬¡ã®ç©ºãããŒããåããruntime/.envã«GRDM_PORT_<SERVICE>ãšããŠèšé²ããŸãïŒÂ§6ïŒã
ã€ã³ã¹ããŒã©ãŒã¯ M1 ããæ¬¡ã®å¯Ÿçãå®è£ ããŸãïŒSPEC-03 §3ïŒïŒ
- ç§å¯: å
šãã¹ã¯ãŒããšéµã¯å°å
¥æã«ä¹±æ°ã§çæãã
runtime/.envïŒã¢ãŒã0600ïŒã«æžããæ±ºã㊠Git ã«ã³ãããããŸããã - ãããã¯ãŒã¯: ãµãŒãã¹ã¯å
éš Compose ãããã¯ãŒã¯ïŒ
internal: trueïŒã§éä¿¡ããŸãããã©ãŠã¶åãã®ããŒãã¯127.0.0.1ã«ã ãå ¬éãããhealth --networkããããæ€èšŒããŸãã - ã³ã³ããå
ç¢å: é root ãŠãŒã¶ãŒïŒå
šæš©éãæã€ç®¡çè
ãŠãŒã¶ãŒã§ããã°ã©ã ãåãããªãïŒãèªã¿åãå°çšã«ãŒããã¡ã€ã«ã·ã¹ãã ã
cap_drop: [ALL]ãå šãµãŒãã¹ã®æ¢å®ã§ãè³æºå¶éïŒã¡ã¢ãªãCPUãããã»ã¹æ°ïŒãä»ããŸããprivileged: trueã¯ã©ãã§ãçŠæ¢ã§ããæ¢å®ã«èããããªããµãŒãã¹ïŒäŸ: èµ·åæã«ã€ã¡ãŒãžå ãžæžã蟌ãå¿ èŠããã PostgreSQLã»RabbitMQã»Elasticsearch ã®ã€ã¡ãŒãžïŒã«ã¯ãmanifest/hardening.jsonã«ãµãŒãã¹ããšã®èšé²ä»ãäŸå€ããããç·©ãã察çãçç±ãèŠçŽãæ¥ãè§£æ¶äºå®ã®ç¯ç®ãæèšããŸãããããã£ãŠèªã¿åãå°çšã«ãŒãã¯ãèãããããµãŒãã¹ãã«é©çšãããå šãµãŒãã¹ã§ã¯ãããŸããã - ãµãã©ã€ãã§ãŒã³: ã€ã¡ãŒãžã¯ããã€ãžã§ã¹ããïŒæ£ç¢ºãªæçŽïŒã§ååŸãã
latestã®ãããªåãã¿ã°ã¯äœ¿ããŸããã - ãµã€ã³ã€ã³: RDM-osf.io-dev2027 PR #8 以éããã¹ãŠã®ããŒã¿ã®ããŒãžãš API ã®çµè·¯ã§ãµã€ã³ã€ã³ãå¿
èŠã§ãïŒ
ENABLE_PUBLIC_ACCESS=falseãæ¢å®ïŒãgrdm-dev compose render --public-access trueã§ãå ¬éãããžã§ã¯ãã®å¿åé²èŠ§ãæ»ããŸãã管çã¢ããªã¯ãã¹ã¯ãŒãã®ããšã«ã¯ã³ã¿ã€ã ã³ãŒããæ±ããŸãïŒPR #10ïŒãã³ãŒããç»é²ããŠããªã管çè ã¯ãæåã®ãµã€ã³ã€ã³ã§ç»é²ç»é¢ãžéãããã¢ããã°ã¬ãŒãã®åŸã¯ãã¹ãŠã®ç®¡çè ãããäžåºŠãµã€ã³ã€ã³ããŸãã - æ€çŽ¢: Elasticsearch 8 ã«ã¯ãå°å ¥ããšã®èªèšŒå±ã«ãã TLS ãšãæ€çŽ¢ã®çŽ¢åŒã«éã£ãå©çšè ã§æ¥ç¶ããããŒãã¯å ¬éããŸããïŒADR-14ïŒã
äžèšã¯ã€ã³ã¹ããŒã©ãŒã課ãèŠæ±äºé ã§ããå®éã®çšŒåç°å¢ããããæºãããŠãããã¯ããã®ã¬ã€ãã§ã¯ãªã
health --networkãšscanã®çµæã瀺ããŸãã
ã€ã³ã¹ããŒã©ãŒãå®ããªããã®:
- OS èªäœãžã®æ»æïŒäŸ: ã«ãŒãã«ã®è匱æ§ïŒ
- éçºè ãžã®ãã£ãã·ã³ã°
- æ¬çª GRDM ãµãŒãã¹ïŒãã®ã¬ã€ãã¯éçºçšã®ã¿ïŒ
compose render ã¯ãèŠæ±ããããŒããŸã㯠runtime/.env ã«ä¿åãããããŒãïŒGRDM_PORT_<SERVICE>ãã©ã¡ããç¡ããã° SPEC-02 §4 ã®æ¢å®ïŒãèµ·ç¹ã«ãããããæå€§ 100 äžãŸã§ç©ºãããŒããæ¢ããŸãããã®ãããžã§ã¯ãèªèº«ã®çšŒåäžã³ã³ãããæã€ããŒãã¯ãã®ãŸãŸä¿ã¡ãŸããå¥ã®ããã°ã©ã ãããŒãã䜿ã£ãŠããã°ããµãŒãã¹ã¯æåã«èŠã€ãã£ã空ãã®åè£ãžç§»ãããã®éžæã GRDM_PORT_<SERVICE> ãšããŠèšé²ãããrender ãå ±åããŸããçµäºã³ãŒã 12 ã«ãªãã®ã¯ããã®ç¯å²ã«ç©ºãã®ä»£æ¿ããŸã£ãããªããšãã ãã§ãã
察å¿: å
ã®ããŒãã䜿ããããã°çžæã®ããã°ã©ã ãæ¢ãããããã§ãªããã° compose render / plan ã瀺ãããŒãããã®ãŸãŸäœ¿ãã
# macOS: AirPlay ã¯ããŒã 5000 ã䜿ã
sudo lsof -i :5000
# AirPlay ãäžèŠãªãããã»ã¹ãçµäºãããdoctor 㯠Docker ãã€ã³ã¹ããŒã«ãããŠããªããåããŠããªãããŸã㯠Compose ãã©ã°ã€ã³ããªããšå€±æããŸãã
察å¿: Docker DesktopïŒmacOSã»WindowsïŒãŸã㯠Docker EngineïŒUbuntuïŒãã€ã³ã¹ããŒã«ãç ⥠27ãCompose v2 ãã©ã°ã€ã³ãå¿
èŠã§ããUbuntu ã§ã¯ ./installer/install-ubuntu.sh ã Docker Engine ãå
¥ããŸãã
ã€ã¡ãŒãžãã³ã³ãã¥ãŒã¿ã®ã¢ãŒããã¯ãã£ã§çµããªãããŸãã¯é åžæžã¿ã€ã¡ãŒãžãååŸã§ããªããšãã«èµ·ããŸãã
DEMO-20 ã®å®éã®ã±ãŒã¹:
- modular-file-renderer on arm64: ããŒã¹ Python 3.5 ã€ã¡ãŒãžã arm64 åãã®
pandas==0.25.1wheel ãæããªããããbuild_platform: linux/amd64ïŒãšãã¥ã¬ãŒã·ã§ã³ïŒã§æ£åžžã«ãã«ãã - ember-osf-web on ä»»æãã©ãããã©ãŒã : ããŒã¹ã€ã¡ãŒãžã Docker manifest v2 schema 1 ã䜿ã£ãŠãããããçŸè¡ Docker ãååŸãæã¿ããœãŒã¹ããã®ãã«ãã¯å€±æããŠããã
çŸç¶: ember-osf-web ã¯ãã prebuilt_image ã䜿ããŸãããè¿ä»£åãã DockerfileïŒRDM-ember-osf-web-dev2027 PR #2ïŒã¯ ember-cli ã®ãã«ããã䜿ãã® CPU äžã® Node ã®æ®µã§å®è¡ããŠéç㪠nginx ã®ã€ã¡ãŒãžãäœãã®ã§ãbuild ã¯ã»ãã®éšåãšåãããã«ãããçµã¿ãŸãïŒmanifest/upstreams.jsonïŒããã® Node ã®æ®µã¯åããŠããé Docker ãšã³ãžã³ã®ã¡ã¢ãªãæ° GiB 䜿ããŸããember-osf-web ã®ãã«ããçµäº 30 ã§å€±æãããããŸããšã³ãžã³ã®ã¡ã¢ãªã確ãããŠãã ããã
health ã¯ãµãŒãã¹ãå¿çããªããšå€±æããŸããhealth --network ã¯ããã«ãå
¬éããŒãã 127.0.0.1 以å€ã®ã¢ãã¬ã¹ã§åŸ
ã¡åããŠãããšå€±æããŸããéåžžã®ã³ãã³ãã¯ãã®æ€æ»ãè¡ããŸããã
察å¿: docker compose -f runtime/docker-compose.yml logs <service> ã§ãã°ã確èªãããµãŒãã¹ãåèµ·åããŸããã«ãŒãããã¯ä»¥å€ã®åŸ
åãããã° runtime/docker-compose.yml ã確èªãïŒãã¹ãŠã® ports: 㯠127.0.0.1: ã§å§ãŸãå¿
èŠãããïŒãcompose render ãããçŽããŸãã
以äžã®è¡šã¯ãREADME.legacy.md ãå®éã«èšè¿°ããŠããæ¹æ³ãš 2027 ã€ã³ã¹ããŒã©ãŒãæ¯èŒããŸãã
| éå»ã®æ¹æ³ïŒREADME.legacy.mdïŒ | æ°ããæ¹æ³ïŒ2027 ã€ã³ã¹ããŒã©ãŒïŒ | çç± |
|---|---|---|
ãµãŒãã¹å士ãéä¿¡ã§ããããããã¹ãã«ã«ãŒãããã¯å¥å 192.168.168.167 ãèšå®ããïŒsudo ãå¿
èŠïŒ |
Compose ã®ãµãŒãã¹åã§éä¿¡ããå
éšãããã¯ãŒã¯ grdm + 127.0.0.1 ã«å
¬éããå
¬éãããã¯ãŒã¯ grdm-edge |
sudo äžèŠããã¹ãã®ãããã¯ãŒã¯å€æŽãªããLAN ãžã®é²åºãªããmacOS/Ubuntu/WSL2 ã§åãèšå®ïŒADR-02ïŒ |
web ãš api ã® local-dist.py ãæã§ local.py ã«ã³ããŒãããäžã€ã® URL ããã©ãŠã¶ãšãµãŒãã¹ã®äž¡æ¹ã䜿ã |
çæãããèšå®ã¯å
éš URLïŒãµãŒãã¹åïŒãšå€éšã®ãã©ãŠã¶çš URLïŒhttp://127.0.0.1:<ããŒã>/ïŒãåãã |
å¥åãªãã§ã転éãšçµ¶å¯Ÿ URL ããã©ãŠã¶ããæ£ããåãïŒADR-02 §4ïŒ |
ã€ã¡ãŒãžã niicloudoperation/*:latest ã«å·®ãæ¿ããCPU ããšã® platform: è¡ãã³ã¡ã³ãã§æã€ docker-compose.override.yml ãææžããã |
grdm-dev compose render ã manifest ãšãããã¡ã€ã«ãã runtime/docker-compose.yml ãçæãããplatform: 㯠manifest ã® build_platform ããæ±ºãŸã |
æåç·šéãªãããã¹ãåºæã®ãã¡ã€ã«ã誀ã£ãŠã³ãããããªããå šå¡åãåºå |
é
åžã€ã¡ãŒãžïŒniicloudoperation/*:latestãquay.io/centerforopenscience/*ïŒããèµ·åããPython/Node ã¢ãžã¥ãŒã«ã¯ *_requirements ãµãŒãã¹ã§ããªã¥ãŒã ã«ã€ã³ã¹ããŒã«ãã |
manifest ã§åºå®ãããœãŒã¹çãããã«ããããé åžæžã¿ã€ã¡ãŒãžã¯èšé²ä»ãã»ãã€ãžã§ã¹ãåºå®ã®äŸå€ã«éã | 粟å¯ãªåçŸæ§ãåãã¿ã°ãªããå€ãã¢ãžã¥ãŒã«ã®ããªã¥ãŒã ãªã |
Apple Silicon ã§ã¯ docker-compose.yml ã® Elasticsearch ã®å¶éã»ã·ã³ã°ã«ããŒãèšå®ã®ã³ã¡ã³ããæã§å€ã |
compose render ã doctor ã®çµæããè³æºå¶éããmanifest/hardening.json ãããµãŒãã¹ããšã®äŸå€ãæžã |
ãã¹ãããšã®ç·šéã§ã¯ãªãäžã€ã®çæãã¡ã€ã« |
äžæµã® Compose ãã¡ã€ã«ã忢±ããæ¢å®èªèšŒæ
å ±ïŒäŸ: postgres/postgresãSPEC-03 §3.1ïŒ |
secrets init ãçæããä¹±æ°ã®ç§å¯ã runtime/.envïŒã¢ãŒã 0600ïŒã«çœ®ããæ¢å®å€ãæ®ãã° scan --baseline ã倱æãã |
æ¢å®èªèšŒæ å ±ãæ®ããªã |
Note: éå»ã®æé ã¯åèã®ããã«
README.legacy.mdã«ãã®ãŸãŸæ®ããŠããŸããæ§ã¬ã€ãèªäœã¯æ¢å®ãã¹ã¯ãŒããèšè¿°ããŠããããããã¯æ§ã¬ã€ããé Œã£ãŠããäžæµã® Compose ãã¡ã€ã«ã«ç±æ¥ããŸãã
- 2026-11-12 â Elasticsearch 8ãy-websocket ã ããå¿
é ãµã€ã³ã€ã³ã管çè
ã® 2 段éãµã€ã³ã€ã³ïŒADR-13 §6ãADR-14ïŒã æ¢åã®å°å
¥ã¯æ¬¡ã®é ã§ã¢ããã°ã¬ãŒãããŸãã
git pullãgrdm-dev secrets init --missingïŒELASTIC8_PASSWORDãšELASTIC8_OSF_PASSWORDãè¶³ããã»ãã®å€ã¯å€ãããSHAREJS_SECRETãæšãŠãŸãïŒãgrdm-dev compose renderãgrdm-dev buildãããäžåºŠgrdm-dev compose renderãgrdm-dev upããã®ããšäžåºŠã ãdocker compose exec web invoke migrate_searchã§æ€çŽ¢ã®çŽ¢åŒã PostgreSQL ããäœãçŽããŸãïŒElasticsearch 2 ã®ããŒã¿ã¯ç§»ããŸãããruntime/volumes/elasticsearch_dataã»mongo_dataã»mongo_tlsã¯ãã䜿ãããªãã®ã§ãæã§æ¶ããŸãïŒãsharejsãšmongoã¯ç¡ããªã£ãã®ã§ãããŒã 7007 ã¯ããå ¬éãããŸãããã¢ããã°ã¬ãŒãåŸã®æåã®ç®¡çè ã®ãµã€ã³ã€ã³ã¯ã¯ã³ã¿ã€ã ã³ãŒãã®ç»é²ãæ±ããŸããäžåºŠã ã衚瀺ããããªã«ããªãŒã³ãŒããä¿ç®¡ããŠãã ããã - 2026-11-06 â Metadata ã¢ããªã³çšã® waffle ãã©ã°èšå®ïŒPR #17ïŒã
README.legacy.mdã®èµ·åæé ã§ã¯ã3 éãã®èµ·åæé ããããã§ãååã® DB ãã€ã°ã¬ãŒã·ã§ã³çŽåŸã«docker compose run --rm web python3 manage.py waffle_flag ember_edit_draft_registration_page --everyoneãäžåºŠå®è¡ããããã«ãªããŸãããwaffle ãã©ã°ïŒããŒã¿ããŒã¹ã«ä¿åãããååä»ãã®ãªã³ïŒãªãã®ã¹ã€ããã§ãéžãã å©çšè ã«æ©èœãæå¹ã«ãããã®ïŒã¯ãMetadata ã¢ããªã³ã® Project Metadata ç·šéç»é¢ãéãããã«å¿ èŠã§ãã2027 ã€ã³ã¹ããŒã©ãŒïŒgrdm-devïŒã«ã¯ãŸã ãã®æé ãç¡ããããMetadata ã¢ããªã³ãå¿ èŠãªå Žåã¯åãmanage.py waffle_flagã³ãã³ããwebãµãŒãã¹ã«å¯ŸããŠæã§å®è¡ããŠãã ãããIncorporated from PR #17 by yacchin1205 (2026-11-06).
| Term | English note | æ¥æ¬èªæ³š |
|---|---|---|
| Container | A box that holds one program and everything it needs, so it runs the same on any computer. | äžã€ã®ããã°ã©ã ãšå¿ èŠãªãã®ãäžç®±ã«å ¥ããŠãã©ã®ã³ã³ãã¥ãŒã¿ã§ãåãããã«åããããã®ç®±ã |
| Docker Compose | A tool that starts many containers together from one description file. | äžã€ã®èšå®ãã¡ã€ã«ããå€ãã®ã³ã³ããããŸãšããŠèµ·ããéå ·ã |
| Loopback / 127.0.0.1 | The address that means "this same computer"; nothing outside can reach it. | ããã®åãã³ã³ãã¥ãŒã¿ããæãçªå°ãå€ããã¯å±ããªãã |
| Internal network | A private network inside Docker that services use to talk without publishing ports. | Docker ã®äžã ãã«ããç§èšãããã¯ãŒã¯ã§ãããŒããå ¬éããã«ã³ã³ããå士ãéä¿¡ã§ããã |
| Egress | Traffic sent from a service to the outside network (the Internet). | ãµãŒãã¹ããå€éšãããã¯ãŒã¯ïŒã€ã³ã¿ãŒãããïŒãžåºãéä¿¡ã |
| Manifest | The list of components and the exact source revisions they are built from (manifest/upstreams.json). |
éšåãšããããçµãæ£ç¢ºãªãœãŒã¹çã®äžèЧïŒmanifest/upstreams.jsonïŒã |
| Profile | A named subset of services to run: minimum, core, or full. |
èµ·åãããµãŒãã¹ã®ååä»ãã®çµãminimumã»coreã»fullã |
| TOON | A compact text form of JSON data that people and AI read easily. | JSON ã®ããŒã¿ãçãæžããããã¹ã圢åŒã人ã«ã AI ã«ãèªã¿ãããã |
| Digest | The exact fingerprint of one image version (sha256:...). |
äžã€ã®ã€ã¡ãŒãžçã®æ£ç¢ºãªæçŽïŒsha256:... ã®åœ¢åŒïŒã |
| Non-root user | A regular user account (not the computer's administrator). | ã³ã³ãã¥ãŒã¿ã®ç®¡çè ã§ãªãéåžžã®ãŠãŒã¶ã¢ã«ãŠã³ãã |
| EOL | End of life: the vendor no longer fixes bugs or security holes. | end of lifeãäœã£ã人ããã°ã穎ãçŽããŠãããªããªã£ãç¶æ ã |
| Wheel | A prebuilt Python package file; without one, pip must compile from source. | ãã«ãæžã¿ã® Python ããã±ãŒãžãã¡ã€ã«ãç¡ããš pip ããœãŒã¹ããçµãå¿ èŠãããã |
| Emulation | Running an image built for another CPU (e.g., linux/amd64 on arm64) through Docker's CPU translation. |
å¥ã® CPU åãã®ã€ã¡ãŒãžïŒäŸ: arm64 äžã§ linux/amd64ïŒã Docker ã® CPU 倿ã§åããããšã |
| WSL2 | Windows Subsystem for Linux 2: a way to run Linux inside Windows. | Windows Subsystem for Linux 2ãWindows ã®äžã§ Linux ãåããä»çµã¿ã |
| CVE | A public record number for one known security weakness (e.g., CVE-2026-12345). |
äžã€ã®æ¢ç¥ã®åŒ±ç¹ã«ä»ãå
¬éã®çªå·ïŒäŸ: CVE-2026-12345ïŒã |
| Baseline controls | Security checks that every install must pass from milestone M1. | M1 ããå šå°å ¥ã«å¿ é ã®ã»ãã¥ãªãã£ãã§ãã¯ã |
| Milestone (M1âM5) | A numbered stage of the 2027 plan; the security gate gets stricter at each one. | 2027 èšç»ã®çªå·ä»ã段éãã»ãã¥ãªãã£éã¯æ®µéããšã«å³ãããªãã |