Merge branch 'main' into npm-deps
This commit is contained in:
commit
8b0e4a1a9c
5 changed files with 22 additions and 12 deletions
11
.github/workflows/publish-sdk-python.yml
vendored
11
.github/workflows/publish-sdk-python.yml
vendored
|
|
@ -25,8 +25,8 @@ jobs:
|
||||||
with:
|
with:
|
||||||
python-version: '3.12'
|
python-version: '3.12'
|
||||||
|
|
||||||
- name: Install build tools
|
- name: Install uv
|
||||||
run: pip install build twine
|
uses: astral-sh/setup-uv@v4
|
||||||
|
|
||||||
- name: Extract version from pyproject.toml
|
- name: Extract version from pyproject.toml
|
||||||
id: version
|
id: version
|
||||||
|
|
@ -46,14 +46,13 @@ jobs:
|
||||||
|
|
||||||
- name: Build package
|
- name: Build package
|
||||||
if: steps.check.outputs.exists == 'false'
|
if: steps.check.outputs.exists == 'false'
|
||||||
run: python -m build
|
run: uv build
|
||||||
|
|
||||||
- name: Publish to PyPI
|
- name: Publish to PyPI
|
||||||
if: steps.check.outputs.exists == 'false'
|
if: steps.check.outputs.exists == 'false'
|
||||||
run: twine upload dist/*
|
run: uv publish
|
||||||
env:
|
env:
|
||||||
TWINE_USERNAME: __token__
|
UV_PUBLISH_TOKEN: ${{ secrets.UV_PUBLISH_TOKEN }}
|
||||||
TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
|
|
||||||
|
|
||||||
- name: Skip publish (version exists)
|
- name: Skip publish (version exists)
|
||||||
if: steps.check.outputs.exists == 'true'
|
if: steps.check.outputs.exists == 'true'
|
||||||
|
|
|
||||||
10
.github/workflows/publish-sdk-typescript.yml
vendored
10
.github/workflows/publish-sdk-typescript.yml
vendored
|
|
@ -12,6 +12,9 @@ jobs:
|
||||||
publish:
|
publish:
|
||||||
name: Publish to npm
|
name: Publish to npm
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
|
permissions:
|
||||||
|
contents: read
|
||||||
|
id-token: write
|
||||||
defaults:
|
defaults:
|
||||||
run:
|
run:
|
||||||
working-directory: sdks/typescript
|
working-directory: sdks/typescript
|
||||||
|
|
@ -26,6 +29,9 @@ jobs:
|
||||||
node-version: '20'
|
node-version: '20'
|
||||||
registry-url: 'https://registry.npmjs.org'
|
registry-url: 'https://registry.npmjs.org'
|
||||||
|
|
||||||
|
- name: Update npm to latest
|
||||||
|
run: npm install -g npm@latest
|
||||||
|
|
||||||
- name: Extract version from package.json
|
- name: Extract version from package.json
|
||||||
id: version
|
id: version
|
||||||
run: |
|
run: |
|
||||||
|
|
@ -51,9 +57,7 @@ jobs:
|
||||||
|
|
||||||
- name: Publish to npm
|
- name: Publish to npm
|
||||||
if: steps.check.outputs.exists == 'false'
|
if: steps.check.outputs.exists == 'false'
|
||||||
run: npm publish --access public
|
run: npm publish --access public --provenance
|
||||||
env:
|
|
||||||
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
|
|
||||||
|
|
||||||
- name: Skip publish (version exists)
|
- name: Skip publish (version exists)
|
||||||
if: steps.check.outputs.exists == 'true'
|
if: steps.check.outputs.exists == 'true'
|
||||||
|
|
|
||||||
|
|
@ -1 +1 @@
|
||||||
1. If you modified the built-in flows or created custom flows in your [OpenRAG Langflow instance](/agents), and you want to preserve those changes, then you must [export your flows](https://docs.langflow.org/concepts-flows-import) before starting this process. Afterwards, you can import your flows or reference the exported flow JSON as needed.
|
1. If you modified the built-in flows or created custom flows in your [OpenRAG Langflow instance](/agents), [export your flows](https://docs.langflow.org/concepts-flows-import) before starting this process. Although OpenRAG can preserve changes to the built-in flows, it doesn't preserve user-created flows. As a general best practice, exporting your flows is recommended to create backups of your customizations. Afterwards, you can reimport your flows or reference the exported flow JSON as needed.
|
||||||
|
|
@ -157,13 +157,18 @@ You can [monitor ingestion](#monitor-ingestion) to see the progress of the uploa
|
||||||
|
|
||||||
## Ingest knowledge from URLs {#url-flow}
|
## Ingest knowledge from URLs {#url-flow}
|
||||||
|
|
||||||
|
When using the OpenRAG chat, you can enter URLs into the chat to be ingested in real-time during your conversation.
|
||||||
|
|
||||||
|
:::tip
|
||||||
|
Use [UTF-8 encoding](https://www.w3schools.com/tags/ref_urlencode.ASP) for URLs with special characters other than the standard slash, period, and colon characters.
|
||||||
|
For example, use `https://en.wikipedia.org/wiki/Caf%C3%A9` instead of `https://en.wikipedia.org/wiki/Café` or `https://en.wikipedia.org/wiki/Coffee%5Fculture` instead of `https://en.wikipedia.org/wiki/Coffee_culture`.
|
||||||
|
:::
|
||||||
|
|
||||||
The **OpenSearch URL Ingestion** flow is used to ingest web content from URLs.
|
The **OpenSearch URL Ingestion** flow is used to ingest web content from URLs.
|
||||||
This flow isn't directly accessible from the OpenRAG user interface.
|
This flow isn't directly accessible from the OpenRAG user interface.
|
||||||
Instead, this flow is called by the [**OpenRAG OpenSearch Agent** flow](/chat#flow) as a Model Context Protocol (MCP) tool.
|
Instead, this flow is called by the [**OpenRAG OpenSearch Agent** flow](/chat#flow) as a Model Context Protocol (MCP) tool.
|
||||||
The agent can call this component to fetch web content from a given URL, and then ingest that content into your OpenSearch knowledge base.
|
The agent can call this component to fetch web content from a given URL, and then ingest that content into your OpenSearch knowledge base.
|
||||||
|
|
||||||
Like all OpenRAG flows, you can [inspect the flow in Langflow](/agents#inspect-and-modify-flows), and you can customize it.
|
Like all OpenRAG flows, you can [inspect the flow in Langflow](/agents#inspect-and-modify-flows), and you can customize it.
|
||||||
|
|
||||||
For more information about MCP in Langflow, see the Langflow documentation on [MCP clients](https://docs.langflow.org/mcp-client) and [MCP servers](https://docs.langflow.org/mcp-tutorial).
|
For more information about MCP in Langflow, see the Langflow documentation on [MCP clients](https://docs.langflow.org/mcp-client) and [MCP servers](https://docs.langflow.org/mcp-tutorial).
|
||||||
|
|
||||||
## Monitor ingestion
|
## Monitor ingestion
|
||||||
|
|
|
||||||
|
|
@ -139,6 +139,8 @@ To reset your OpenRAG deployment _and_ delete all OpenRAG data, see [Reinstall O
|
||||||
|
|
||||||
3. Repeat the [setup process](/install#setup) to restart the services and launch the OpenRAG app. Your OpenRAG passwords, OAuth credentials (if previously set), and onboarding configuration are restored from the `.env` file.
|
3. Repeat the [setup process](/install#setup) to restart the services and launch the OpenRAG app. Your OpenRAG passwords, OAuth credentials (if previously set), and onboarding configuration are restored from the `.env` file.
|
||||||
|
|
||||||
|
4. If you exported customized flows, [import your flows](https://docs.langflow.org/concepts-flows-import) into Langflow after completing the onboarding process.
|
||||||
|
|
||||||
</TabItem>
|
</TabItem>
|
||||||
<TabItem value="env" label="Self-managed services">
|
<TabItem value="env" label="Self-managed services">
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue