Ettore Di Giacinto
7efb20bd1f
For a kind that declares files.transfer, the connector manager gives the add-on a handle and not the bytes, in both directions. Inbound, the add-on streams the file to the host. The chat upload then reads it from the blob store, so a 6 MB PDF reaches the chat. Outbound, the manager checks the access of the chat to the file, gives the process that runs the add-on only the hash and the size of the content, and the add-on pulls the chunks. The file limit of such a kind has no inline cap: it is the smallest of the host ceiling, the ability the kind declares and the limit the owner set for the bot, and the sentence names the number and the layer. A kind without transfer keeps the 1 MiB inline cap, and its sentence says so. Checks: the files of one message may add up to three times the limit; the media type that the add-on states must be among the types the kind declares; an outbound file must have a type that the kind declares and must not start with an HTML page. Every transfer writes one audit line with direction, binding, size, result, layer and time, and no name or content. The binding page no longer says "larger files need streaming" for a kind that streams. The specs run the real Telegram and Slack add-ons, the real gateway and the real file operations over scripted platform APIs, with a 6 MB file in each direction. Not in this change: a daily byte counter per binding, and a virus scan (the table has a hook that accepts everything). Assisted-by: Claude:claude-sonnet-5-5 go test
LocalAI website
LocalAI documentation website
Requirement
In this project, the Docsy theme component is pulled in as a Hugo module, together with other module dependencies:
$ hugo mod graph
hugo: collected modules in 566 ms
hugo: collected modules in 578 ms
github.com/google/docsy-example github.com/google/docsy@v0.5.1-0.20221017155306-99eacb09ffb0
github.com/google/docsy-example github.com/google/docsy/dependencies@v0.5.1-0.20221014161617-be5da07ecff1
github.com/google/docsy/dependencies@v0.5.1-0.20221014161617-be5da07ecff1 github.com/twbs/bootstrap@v4.6.2+incompatible
github.com/google/docsy/dependencies@v0.5.1-0.20221014161617-be5da07ecff1 github.com/FortAwesome/Font-Awesome@v0.0.0-20220831210243-d3a7818c253f
If you want to do SCSS edits and want to publish these, you need to install PostCSS
npm install
Running the website locally
Building and running the site locally requires a recent extended version of Hugo.
You can find out more about how to install Hugo for your environment in our
Getting started guide.
From the LocalAI repository root, run:
make docs
The Hugo configuration lives in the docs directory. To invoke Hugo
directly instead, run:
cd docs
hugo server
Running a container locally
You can run docsy-example inside a Docker
container, the container runs with a volume bound to the docsy-example
folder. This approach doesn't require you to install any dependencies other
than Docker Desktop on
Windows and Mac, and Docker Compose
on Linux.
-
Build the docker image
docker-compose build -
Run the built image
docker-compose upNOTE: You can run both commands at once with
docker-compose up --build. -
Verify that the service is working.
Open your web browser and type
http://localhost:1313in your navigation bar, This opens a local instance of the docsy-example homepage. You can now make changes to the docsy example and those changes will immediately show up in your browser after you save.
Cleanup
To stop Docker Compose, on your terminal window, press Ctrl + C.
To remove the produced images run:
docker-compose rm
For more information see the Docker Compose documentation.
Troubleshooting
As you run the website locally, you may run into the following error:
➜ hugo server
INFO 2021/01/21 21:07:55 Using config file:
Building sites … INFO 2021/01/21 21:07:55 syncing static files to /
Built in 288 ms
Error: Error building site: TOCSS: failed to transform "scss/main.scss" (text/x-scss): resource "scss/scss/main.scss_9fadf33d895a46083cdd64396b57ef68" not found in file cache
This error occurs if you have not installed the extended version of Hugo. See this section of the user guide for instructions on how to install Hugo.
Or you may encounter the following error:
➜ hugo server
Error: failed to download modules: binary with name "go" not found
This error occurs if you have not installed the go programming language on your system.
See this section of the user guide for instructions on how to install go.