Added 2 sections; added logo

This commit is contained in:
Bruno Silva committed 2025-07-06 19:26:36 -04:00
1 parent edf922539a
commit c079a055e8
39 files changed
+1065 -6

No files matched your search

@@ -0,0 +1,90 @@
## How to install Ollama on a linux machine?
To install **Ollama** on a Linux machine, follow these steps:
**1. Check Prerequisites**
- Ensure your system meets the minimum requirements: **64-bit CPU**, at least **8GB RAM** (16GB recommended), and **10–12GB free disk space**. A **GPU** (NVIDIA or AMD) is strongly recommended for optimal performance, but Ollama can run on CPU if necessary.
- Make sure you have **curl** installed. If not, install it using:
```bash
sudo apt-get install curl
```
- For GPU support, verify your drivers (e.g., with `nvidia-smi` for NVIDIA GPUs).
**2. Install Ollama**
- The simplest way is to run the official installation script:
```bash
curl -fsSL https://ollama.com/install.sh | sh
```
This script will:
- Download and install Ollama to `/usr/local/bin`
- Create the `ollama` user and necessary groups
- Set up and start the Ollama systemd service
**3. Verify Installation**
- Check that Ollama is installed and running:
```bash
ollama --version
systemctl status ollama
```
By default, Ollama runs as a service and listens on `localhost:11434`.
**4. (Optional) Manual or Docker Installation**
- For manual installation or advanced setups, you can download the binary or use Docker:
- Manual:
```bash
curl -fsSL https://ollama.com/download/ollama-linux-amd64.tgz | sudo tar zx -C /usr
```
Then set up the systemd service as described in the documentation.
- Docker:
```bash
docker pull ollama/ollama
docker run -d --gpus=all -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama
```
This is useful for containerized environments.
**5. Pull and Run a Model**
- After installation, fetch a language model (e.g., Llama 2):
```bash
ollama pull llama2
```
- Run the model:
```bash
ollama run llama2
```
**6. Troubleshooting**
- If GPU support is not detected, ensure your drivers and toolkits (e.g., `nvidia-cuda-toolkit`) are installed and repeat the installation.
**Summary Table:**
| Step | Command/Action |
| :-- | :-- |
| Update system | `sudo apt-get update && sudo apt-get upgrade` |
| Install curl | `sudo apt-get install curl` |
| Install Ollama | `curl -fsSL https://ollama.com/install.sh | sh` |
| Verify installation | `ollama --version` and `systemctl status ollama` |
| Pull a model | `ollama pull llama2` |
| Run a model | `ollama run llama2` |
After these steps, Ollama should be ready to use on your Linux system.
+7
View File
@@ -0,0 +1,7 @@
{
"label": "Section 2: Building and Using AI Systems",
"position": 3,
"link": {
"type": "generated-index"
}
}
Binary file not shown.

After

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

+55
View File
@@ -0,0 +1,55 @@
---
sidebar_position: 1
---
# Manage Docs Versions
Docusaurus can manage multiple versions of your docs.
## Create a docs version
Release a version 1.0 of your project:
```bash
npm run docusaurus docs:version 1.0
```
The `docs` folder is copied into `versioned_docs/version-1.0` and `versions.json` is created.
Your docs now have 2 versions:
- `1.0` at `http://localhost:3000/docs/` for the version 1.0 docs
- `current` at `http://localhost:3000/docs/next/` for the **upcoming, unreleased docs**
## Add a Version Dropdown
To navigate seamlessly across versions, add a version dropdown.
Modify the `docusaurus.config.js` file:
```js title="docusaurus.config.js"
export default {
themeConfig: {
navbar: {
items: [
// highlight-start
{
type: 'docsVersionDropdown',
},
// highlight-end
],
},
},
};
```
The docs version dropdown appears in your navbar:
![Docs Version Dropdown](./img/docsVersionDropdown.png)
## Update an existing version
It is possible to edit versioned docs in their respective folder:
- `versioned_docs/version-1.0/hello.md` updates `http://localhost:3000/docs/hello`
- `docs/hello.md` updates `http://localhost:3000/docs/next/hello`
+88
View File
@@ -0,0 +1,88 @@
---
sidebar_position: 2
---
# Translate your site
Let's translate `docs/intro.md` to French.
## Configure i18n
Modify `docusaurus.config.js` to add support for the `fr` locale:
```js title="docusaurus.config.js"
export default {
i18n: {
defaultLocale: 'en',
locales: ['en', 'fr'],
},
};
```
## Translate a doc
Copy the `docs/intro.md` file to the `i18n/fr` folder:
```bash
mkdir -p i18n/fr/docusaurus-plugin-content-docs/current/
cp docs/intro.md i18n/fr/docusaurus-plugin-content-docs/current/intro.md
```
Translate `i18n/fr/docusaurus-plugin-content-docs/current/intro.md` in French.
## Start your localized site
Start your site on the French locale:
```bash
npm run start -- --locale fr
```
Your localized site is accessible at [http://localhost:3000/fr/](http://localhost:3000/fr/) and the `Getting Started` page is translated.
:::caution
In development, you can only use one locale at a time.
:::
## Add a Locale Dropdown
To navigate seamlessly across languages, add a locale dropdown.
Modify the `docusaurus.config.js` file:
```js title="docusaurus.config.js"
export default {
themeConfig: {
navbar: {
items: [
// highlight-start
{
type: 'localeDropdown',
},
// highlight-end
],
},
},
};
```
The locale dropdown now appears in your navbar:
![Locale Dropdown](./img/localeDropdown.png)
## Build your localized site
Build your site for a specific locale:
```bash
npm run build -- --locale fr
```
Or build your site to include all the locales at once:
```bash
npm run build
```