Overture docs update - #257
Conversation
|
|
||
| :::info Need Help? | ||
| If you encounter any issues or have questions about our API, please don't hesitate to reach out through our relevant [**community support channels**](https://docs.overture.bio/community/support). | ||
| If you encounter any issues or have questions about our API, please don't hesitate to reach out through our [**support page**](/community/support) or our [**discussion forum**](https://github.com/overture-stack/docs/discussions?discussions_q=). |
There was a problem hiding this comment.
same issue here. the full url being replaced was the right approach
There was a problem hiding this comment.
/community/support is still there
| - [**Stage Overview**](https://docs.overture.bio/develop/Stage/overview) | ||
| - [**Setting up the Development Environment**](https://docs.overture.bio/develop/Stage/setup) |
There was a problem hiding this comment.
are these capital S in stage required by docusaurus? I'd try to avoid making urls case sensitive whenever possible. odds are these links are fine with lowercase
There was a problem hiding this comment.
i believe docusaurus, it renders the name in the sidebar based on the folder name
There was a problem hiding this comment.
to confirm, that means you named the folder with capitals?
The site renamed /docs/core-software/* to /build/* to /develop/*, moved /docs/contribution to /develop/contributing, /guides/getting-started to /deploy, and /guides/administration-guides to /use. Each old path only resolved through a redirect hop. Verified every new target against a local site build.
bbc361f to
607490f
Compare
| # one (donor) and NEXT_PUBLIC_ARRANGER_API_URL is just http://localhost:5050. # | ||
| # ---------------------------------------------------------------------------------- # | ||
| arranger: | ||
| image: ghcr.io/overture-stack/arranger-search-server:${ARRANGER_TAG:-b5c6051b} |
There was a problem hiding this comment.
the fallback should be a release version, never a commit ref tag. will provide 3.1.0 soon, we're just finishing some touches, so marking this as pending in my local Stage's debt doc (which I will push soon after we merge this PR)
no actionable here for you now
|
nice work overall, @MitchellShiell! this is a real improvement over the Prelude dependency: self-contained, idempotent, and in particular I like that the security posture is handled properly (localhost-only binding, security plugin explicitly called out as dev-only in three places, no real credentials in the compose file). A couple of smaller notes:
|
Documentation for the Overture docs site.
The setup guide told readers to clone the Prelude
docs-demo/search-portal-workshopbranch to get a back end to develop against. Prelude is being retired as the source of component dev environments, so Stage now ships its own, a newdev-services/directory, anddocs/setup.mdis rewritten around it.Nothing under
components/,pages/orglobal/is touched. The only source addition isdev-services/.dev-services/(new)Stage is front-end scaffolding: its table, facets and query bar are Arranger UI components, so they render nothing without an Arranger search API behind them, and Arranger needs a search engine in turn. This supplies both, so no second repository is required.
docker-compose.yml9200), a one-shotsetupcontainer, Arranger search server (5050)Makefileup,down,status,logs,resetconfigs/opensearch/donor-mapping.jsondonor-indexand itsdonor_centricaliasconfigs/arranger/donor/base,extended,facets,table,matchboxdata/donor.ndjson_bulkformREADME.mdWorth a reviewer's attention:
npm run dev, so the copy you edit is the copy you see. The old Prelude demo brought up its own Stage on3000, which is why readers were told to develop on3001, to avoid colliding with a portal they were not editing.127.0.0.1only.make upis idempotent and waits. Thesetupcontainer applies the template, creates the index and alias, bulk-loads, then exits; later starts skip finished work.--waitplus Arranger's healthcheck means it does not return until Arranger is serving the catalogue.make resetis the only destructive target and prompts for a typedDELETE.docs-demo/ai-assisted-data-discoverydemo, so a portal built here lines up with that one.opensearchproject/opensearch:2.17.1andghcr.io/overture-stack/arranger-search-server:b5c6051b, overridable viaOPENSEARCH_TAG/ARRANGER_TAG. The Arranger pin is an unreleased commit build, so it wants bumping to a release tag once one is cut with the catalogue behaviour these configs rely on.docs/setup.mdcd dev-services && make up.elastic/myelasticpassword. None of it applies now.NEXT_PUBLIC_ARRANGER_INDEXcorrected fromdatatable1-indextodonor-index, and each variable now citesdev-services/configs/arranger/donor/base.jsonas the file that sets it.{"data":{"records":{"hits":{"total":373}}}}), so the back end can be confirmed before touching Stage.NEXT_PUBLIC_ARRANGER_API_URLneeds no catalogue path: Arranger mounts a single registered catalogue at the root, switching to/<catalogue>/graphqlonly once there is more than one.3001recommendation stays but its reason is corrected: it is just about leaving3000free.README.mdStale
docs/core-software/Stage/*links →/develop/Stage/*, contributing →/develop/contributing, getting started →/deploy.Before merging
dev-services/anddocs/setup.mdhave to land together; the guide walks through a directory that does not exist onmain.ARRANGER_TAGis acceptable, or swap it for a release tag.