Deploy Dify v1.19.0

Deploy and Host Dify v1.19.0 on Railway

Build AI workflows, chatflows and Classic Knowledge applications with Dify Community Edition. This basic template uses one public Gateway and private application, database, queue, vector, plugin, sandbox and storage services.

About Hosting Dify v1.19.0

Wait for all services to start, then open the Gateway URL and immediately complete the one-time administrator setup. Custom domains are optional: Web and API traffic share one origin, without two domains or manual cookie-domain settings. Add your own model-provider credentials in Dify; provider usage is billed separately.

Uploads use persistent SeaweedFS S3-compatible storage. Redis requires authentication, internal keys are generated per deployment, and the scheduler runs periodic jobs. The private HTTP proxy blocks private network destinations.

First deployment: required steps

1. Deploy and wait for initial database migrations and application startup. The Gateway can become healthy before the API is ready; brief initial upstream errors are not a reason to recreate the project.
2. Open the generated HTTPS domain on Gateway. Complete administrator setup immediately; if needed, open /install on that same domain, then sign in.
3. Install/configure the model-provider plugin you need and enter your own provider credentials in Dify. Provider usage is billed separately.
4. Run a sample workflow. For semantic/vector retrieval, configure an embedding provider before indexing documents. The included Classic Knowledge economy/keyword mode has a different requirement from embedding-based retrieval.

Steps removed from the old installation flow

• No pair of custom Web/API domains or shared cookie-domain setting is required. Keep the generated Gateway as the single public origin; COOKIE_DOMAIN may remain empty.
• No MinIO console, manual S3 bucket creation, bucket-provisioning client or manually generated internal secret is required. SeaweedFS and generated references handle this.
• No manual Redis password wiring, sandbox-key repair, scheduler creation or plugin-storage permission workaround is required for a fresh deployment. These are included in the saved template.
• The old bucket-provisioner role is now Gateway. Keep it running: it routes the dashboard, API and files.

Optional configuration includes SMTP/Resend for mail, custom domains, model providers and backups. Mail-variable examples are not working mail credentials. If you add a custom domain, keep Web and API on the same Gateway origin and update Api.HOST and Web.HOST consistently. Do not expose the private services just to complete setup.

Common Use Cases

• Build and execute AI workflows and chatflows.
• Install model-provider plugins and connect supported providers.
• Upload documents for Classic Knowledge and RAG after configuring an embedding model.

Dependencies for Dify v1.19.0 Hosting

Dify API, Web, Worker and Scheduler 1.19.0; PostgreSQL; Redis; Weaviate; Dify plugin daemon and sandbox; SeaweedFS; Squid proxy; Nginx Gateway. Persistent volumes and regular backups are required.

This basic edition excludes Agent V2, its local runtime, collaboration and optional KnowledgeFS. Those features require additional upstream services and configuration. Remote plugin debugging is disabled. Code requiring private network access is restricted by the proxy policy.

Why Deploy Dify v1.19.0 on Railway

The template connects core services, generated credentials, persistent storage and one-domain routing. Railway bills CPU, memory, storage and network usage; this multi-service stack is not free. Resource needs grow with workers, documents, vectors and traffic.

Deployment Dependencies

A Railway workspace with capacity for all 12 services and persistent volumes. External model/embedding providers and mail providers require your own accounts and credentials. See the Dify source and license.

Existing installations

These changes configure new deployments and do not migrate existing data. Existing MinIO uploads need an explicit migration to SeaweedFS; do not attach MinIO data directly to SeaweedFS. Older Weaviate installations need the upstream staged upgrade path.

Dify is maintained by langgenius. This independent Railway template is maintained by RailGenius. Upstream project and license: https://github.com/langgenius/dify.

Version 1.19.0 and upgrade scope

API, Web, Worker and Scheduler use1.19.0; plugin daemon uses0.6.14-local. API, Worker and Scheduler share OPS_TRACE_QUEUE=ops_trace_v2. Fresh database migrations run automatically with the API.

These are fresh-install template updates, not an in-place upgrade of your existing project. For existing projects, back up databases, files, vectors, configuration and secrets, follow the full migration chain and review the upstream tracing-queue transition before rolling an upgrade. Existing traces are not backfilled; new App packages use formatv2 and require a compatible importer. See the official1.19.0 release and upgrade guide.

Validation on4November2026 covers first administrator setup/login, upload/preview, Python code execution and a complete workflow, Classic Knowledge economy indexing, official provider-plugin installation and stored upload persistence after replacing storage. Paid model inference, embedding retrieval and external nested-trace export were not exercised.