Skip to content

chore: place deploy buttons for DEEIX Chat before Configuration - #901

Open
cosark wants to merge 1 commit into
DEEIX-AI:devfrom
cosark:add-one-click-deploy
Open

cosark wants to merge 1 commit into
DEEIX-AI:devfrom
cosark:add-one-click-deploy

Conversation

@cosark

@cosark cosark commented Oct 23, 2026

Copy link
Copy Markdown

Summary

A new One-Click Deploy section sits between Quick Start and Configuration, with deploy buttons for RepoCloud and Railway.
Readers who would rather run DEEIX Chat on a hosted server than prepare the Docker profiles by hand get one-click access to two providers; the RepoCloud one is a ready-made template that needs no other instructions.
The Railway template is community-made and builds from this repository (template page).

Change type

  • Bug fix
  • Feature
  • Documentation
  • Refactor
  • Configuration / deployment
  • Security hardening
  • Other

Affected areas

  • Frontend / UI
  • Backend / API
  • Authentication / authorization
  • Conversations / streaming
  • Files / RAG / extraction
  • Model routing / providers
  • MCP / tools
  • Billing / payments
  • Admin console
  • Deployment / Docker / configuration
  • Documentation

Verification

Documentation only: README.md gains five lines (the heading, two buttons, and blank lines) and nothing else changes. I rendered the README on my fork branch and checked that both buttons and their links load.

  • Not run; reason: no code or configuration changed, so pnpm check, pnpm test and pnpm build do not apply.

Screenshots, API examples, or logs

None: no UI, API, or operational behavior changes.

Configuration, migration, and compatibility notes

None: no config file, environment variable, schema, Docker, URL, CORS, or API contract is touched.

Documentation

  • Documentation is not needed for this change.
  • Documentation was updated.
  • Documentation still needs to be updated.

Security and privacy

  • No secrets, tokens, credentials, local config, or personal data are included.
  • User data access remains scoped by authenticated user context unless an admin-only path explicitly requires broader access.
  • Security-sensitive behavior was reviewed, including authentication, authorization, provider routing, file processing, billing, and admin APIs where relevant.

Checklist

  • I searched existing issues and pull requests.
  • Changes are focused and do not include unrelated refactors.
  • Tests or static verification were run where practical.
  • User-facing behavior, deployment steps, API contracts, or configuration changes are documented.
  • Generated artifacts are included only when this project explicitly requires them.
  • Caches, build output, .pyc files, .env files, and local storage data are not committed.

@github-actions

Copy link
Copy Markdown

This pull request has had no activity for 7 days. It will be closed in 7 days if there is no further activity.

@github-actions github-actions Bot added the stale label Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant