Dify: v0.6.12-fix1

## 🛠️ v0.6.12-fix1 > [!WARNING] > Fixed the issue where the WebApp URL was incorrect and the problem where the model and tools icons weren’t showing up after starting from Docker Compose with default `.env`. --- ### 🎉 Upgrade to new docker compose deployment #### Key Changes 1. **Persistent Custom Environment Variables**: Users can now declare environment variables in .env that remain persistent across deployments. This change ensures that custom configurations are not lost during upgrades or redeployments. 2. **Unified Vector Database Services**: All vector database services have been consolidated into a single Docker file. Users can switch between different vector databases by modifying the `VECTOR_STORE` environment variable in your local `.env`. This simplifies the management of various vdb services and allows for more dynamic deployments. 3. **Mandatory .env File**: Unlike the previous deployment method, the new method requires an [.env] file before running `docker compose up`. Users should start by copying the `.env.example` file to create their own `.env` file. This step is crucial for configuring the deployment to meet specific needs. 4. **Legacy Support**: The previous deployment files have been moved to a `docker-legacy` directory. These files will no longer be maintained, but they are available for use if needed. #### Migrating For existing users who's customized `docker-compose.yaml`, `ssrf_proxy/squid.conf` or `nginx/conf.d/default.conf`, you may need to modify the corresponding environment variables in `.env` to reflect your existing changes. We are actively seeking feedback from the community to refine and enhance the deployment process. As more users adopt this new method, we will continue to make improvements based on your experiences and suggestions. #### How to Get Started To get started with the new deployment method: - Ensure you have Docker and Docker Compose installed on your system. - Navigate to the new `docker` directory. - Copy the `docker/.env.example` file to a new file named `.env` and customize it as needed. - Run `docker compose up` to start the services. We encourage all users to transition to this new method to take advantage of the improved flexibility and configuration options. Your feedback during this beta phase is invaluable and will help us make the deployment process even better. For detailed configuration options and environment variable settings, refer to the `.env.example` file and the Docker Compose configuration files in the [docker](https://github.com/langgenius/dify/tree/main/docker) directory. --- ## Upgrade Guide ### Docker compose deployments > [!WARNING] > The `docker-compose.yaml` has been refactored. If you've made any changes to the file, make sure to check out the "Upgrade to new docker compose deployment" section above for usage and migration tips. 1. Back up your customized docker-compose YAML file (optional) ```bash cd docker cp docker-compose.yaml docker-compose.yaml.$(date +%s).bak ``` 2. Get the latest code from the main branch ```bash git checkout main git pull origin main ``` 3. Stop the service，Command, please execute in the docker directory ```bash docker compose down ``` 4. Back up data ```bash tar -cvf volumes-$(date +%s).tgz volumes ``` 5. Upgrade services ```bash docker compose up -d ``` ### Source Code deployments 1. Stop API server, Worker and Web frontend Server. 2. Get the latest code from the main branch: ```bash git checkout main git pull origin main ``` 3. Update Python dependencies: ```bash cd api poetry install ``` 7. Then, let's run the migration script: ```bash poetry shell flask db upgrade ``` 8. Finally, run API server, Worker and Web frontend Server again. ## What's Changed * add README for new docker/ directory by @guchenhe in https://github.com/langgenius/dify/pull/5724 * Chore/set entrypoint scripts permissions by @guchenhe in https://github.com/langgenius/dify/pull/5726 * Rename README to README.md by @guchenhe in https://github.com/langgenius/dify/pull/5727 * chore: support both $$ and $ latex format by @ZuzooVn in https://github.com/langgenius/dify/pull/5723 * fix: couldn't log in or resetup after a failed setup by @takatost in https://github.com/langgenius/dify/pull/5739 * fix: app config does not use empty string in the env by @takatost in https://github.com/langgenius/dify/pull/5741 * fix: env SMTP_PORT is empty caused err when launching by @takatost in https://github.com/langgenius/dify/pull/5742 **Full Changelog**: https://github.com/langgenius/dify/compare/0.6.12...0.6.12-fix1