Skip to content

Conversation

@fbugarski
Copy link
Contributor

No description provided.

Signed-off-by: fbugarski <filipbugarski@gmail.com>
Signed-off-by: fbugarski <filipbugarski@gmail.com>
Copy link
Contributor

@SammyOina SammyOina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add screenshots for ui parts, also make sure for split parts of the developer-guide, make sure the tutorials are complete and not split off

@@ -0,0 +1,28 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove this since we replaced it with our own chat

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

replace with our ui chat

- Optional: apply LoRA
- Train
- Export GGUF
- Upload to Cube AI
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is incomplete from the original dev guide

You can obtain it in the Cube AI UI under **Profile → Tokens**.

```json
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use yaml, same as in the getting started guide


## How Cube AI Uses Attestation Today

Cube AI runs inside **AMD SEV-SNP–based Confidential VMs (CVMs)**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we support both amd sev-snp and intel-tdx

Comment on lines 63 to 74
## Future Roadmap (User-Facing Attestation)

Cube AI will introduce **public attestation verification** features, allowing applications to verify that they are interacting with a trusted instance.

Planned enhancements include:

### 🔹 API Endpoint for Attestation Reports

Applications will be able to request:

```bash
GET /attestation/report
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this already exists POST /attestation you can test it

}
EOF
```
This guide introduces the basics of Cube AI using the **web interface only**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't have state web interface only, or no cli being used

```

Update the `apiKey` with your `access token`, the `apiBase` with the URL of your Cube AI instance, and replace `<your-domain-id>` with the domain ID from step 4. These values should reflect the actual deployment settings you're working with.
You should now see the Cube AI login screen.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add screenshots


---

## 3. Create a Domain (UI Only)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't need to add UI only

Comment on lines +53 to +58
1. From the dashboard, click **Create Domain**
2. Enter a **Name** and **Route**
3. Click **Create**
4. When the domain appears in the list, click **Open Domain**

You are now inside your new domain.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

screenshots

For VS Code and development tooling, continue to the:

For a more detailed explanation of how to connect to Cube AI with the continue extension, check out [this video demonstration](https://www.youtube.com/watch?v=BGpv_iTB2NE).
👉 **Continue Integration** page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be a link

Signed-off-by: fbugarski <filipbugarski@gmail.com>
Signed-off-by: fbugarski <filipbugarski@gmail.com>
@drasko drasko merged commit 2364923 into main Dec 18, 2025
1 check passed
@fbugarski fbugarski deleted the docsreview branch December 18, 2025 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants