Search Results for "llama-cpp-static"

...If you need to run IPFS in a Docker container, you can still have Web UI available by exposing both the Gateway and Web UI ports. The end-to-end tests (E2E) test the full app in a headless Chromium browser. They spawn real IPFS node for HTTP API and a static HTTP server to serve the app. The purpose of those tests is not being comprehensible, but act as a quick regression and integration suite.

...Deploy a single WASM smart contract to deploy the whole web app. You only need to deploy a single smart contract using WebAssembly to host your app's HTTP backend, static resources, and blockchain logic. There is an HTTP gateway to NEAR blockchain which allows smart contract to handle arbitrary GET requests. Every smart contract on NEAR also gets a corresponding API endpoint which can be accessed through regular HTTP requests. You can load any required data in web4_get by returning list of URLs to preload in preloadUrls field. ...

Upload static websites to IPFS pinning services and optionally update the DNS. The goal of ipfs-deploy is to make it as easy as possible to deploy a static website to IPFS.

This repo contains all the metadata of the yearn ecosystem. Contents of the data directory are synced to IPFS for storage, accessible through our gateway meta.yearn.network. Consistency of the stored data is verified by small scripts and schemas. Any document can be added to the data directory, but there are some special checks to ensure consistency and ease of accessibility. All JSON files that share names with the files in the schema directory must follow the defined schema, otherwise,...

...Although, it can not encrypt IPFS nor WebTorrent files added to your site and purely encrypts the actual content, which you enter through the text editor or devtools, as well as embedded Base64 files. Send Texts, Music, Pictures and Videos embedded in HTML with CSS and JavaScript through WebRTC, WebTorrents or IPFS, live edited P2P as well as static Torrents + IPFS. With WebRTC/WebTorrent (NOT IPFS - more details) - No conversation data passes a server nor is saved anywhere but sent directly from browser to browser. Your website disappears from the aether as soon as you close or reload your tab, except of your WebTorrent/IPFS snapshots.

Soy is a collection of smart contracts and tools to enable you to build your site on the distributed web. By virtue of using ENS and IPFS your content will be quickly accessible all over the world without having to set up or manage any infrastructure. Scripting with Soy usually looks something like this. This is an example of creating a new Soy instance and using it to register a domain and publish the content hash for the site. Once you have ENS set up to point to an ipfs hash, simply add...