1
0
mirror of https://github.com/imartinez/privateGPT.git synced 2025-05-06 15:27:21 +00:00
privateGPT/fern
Otto L 1efac6a3fe
feat(llm - embed): Add support for Azure OpenAI ()
* Add support for Azure OpenAI

* fix: wrong default api_version

Should be dashes instead of underscores.
see: https://learn.microsoft.com/en-us/azure/ai-services/openai/reference

* fix: code styling

applied "make check" changes

* refactor: extend documentation

* mention azopenai as available option and extras
* add recommended section
* include settings-azopenai.yaml configuration file

* fix: documentation
2024-03-15 16:49:50 +01:00
..
docs feat(llm - embed): Add support for Azure OpenAI () 2024-03-15 16:49:50 +01:00
openapi feat: Add stream information to generate SDKs () 2024-02-02 16:14:22 +01:00
docs.yml feat(nodestore): add Postgres for the doc and index store () 2024-03-14 17:12:33 +01:00
fern.config.json feat(docs): upgrade fern () 2024-03-11 23:02:56 +01:00
generators.yml Move Docs to Fern () 2023-11-16 23:25:14 +01:00
README.md Refactor documentation architecture () 2023-11-19 18:46:09 +01:00

Documentation of privateGPT

The documentation of this project is being rendered thanks to fern.

Fern is basically transforming your .md and .mdx files into a static website: your documentation.

The configuration of your documentation is done in the ./docs.yml file. There, you can configure the navbar, tabs, sections and pages being rendered.

The documentation of fern (and the syntax of its configuration docs.yml) is available there docs.buildwithfern.com.

How to run fern

You cannot render your documentation locally without fern credentials.

To see how your documentation looks like, you have to use the CICD of this repository (by opening a PR, CICD job will be executed, and a preview of your PR's documentation will be deployed in vercel automatically, through fern).

The only thing you can do locally, is to run fern check, which check the syntax of your docs.yml file.

How to add a new page

Add in the docs.yml a new page, with the following syntax:

navigation:
  # ...
  - tab: my-existing-tab
    layout:
      # ...
      - section: My Existing Section
        contents:
          # ...
          - page: My new page display name
            # The path of the page, relative to `fern/`
            path: ./docs/pages/my-existing-tab/new-page-content.mdx