fix: replaced urls for docker-compose and .env.example files

[AngeloB-AIS]

I made an earlier overhaul of the docker-compose doc that turned out to be unnecessary. At present, only the URLs needed to be updated to resolve the issue of users not being able to access the cloud-postgresql version of the docker deployment (which, at this point, is essentially 1:1 with non-cloud-postgresql version). I left the clost-postgresql tab because it explains which variables the users need to change when using an external db.

[AngeloB-AIS]

@CodiumAI-Agent /review

[AngeloB-AIS]

@CodiumAI-Agent /improve

[QodoAI-Agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Security	Enhance security by managing sensitive environment variables through secure methods Recommend using a more secure method to handle sensitive data like environment variables, possibly through encrypted secrets management or environment-specific files that are not downloaded via public URLs. open-source/guides/setup/docker-compose.mdx [39] -curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/.env.example +# Use secure secrets management for handling sensitive data Suggestion importance[1-10]: 8 Why: Suggesting the use of secure secrets management for handling sensitive data addresses a significant security concern, especially for production environments.	8
Best practice	✅ Add verification to ensure critical files are downloaded successfully Suggestion Impact: The commit added verification messages to confirm the successful download of the docker-compose.yaml and .env.example files, as suggested. code diff: - curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/docker-compose.yaml + curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/docker-compose.yaml && echo "Downloaded docker-compose.yaml successfully" || echo "Failed to download docker-compose.yaml" ``` 3. Download the `.env.example` file from the following link. ```bash - curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/.env.example + curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/.env.example && echo "Downloaded .env.example successfully" || echo "Failed to download .env.example" Consider adding error handling or a verification step after downloading the docker-compose.yaml and .env.example files to ensure the files are downloaded correctly before proceeding. open-source/guides/setup/docker-compose.mdx [33-39] -curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/docker-compose.yaml +curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/docker-compose.yaml && echo "Downloaded docker-compose.yaml successfully" || echo "Failed to download docker-compose.yaml" ... -curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/.env.example +curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/.env.example && echo "Downloaded .env.example successfully" || echo "Failed to download .env.example" Suggestion importance[1-10]: 7 Why: Adding verification after downloading files ensures that the setup process does not proceed with missing or corrupt files, which is crucial for deployment success.	7
	Prevent conflicts by cleaning up old configuration files before downloading new ones Suggest adding a cleanup step or script to remove or archive old docker-compose.yaml and .env.example files before downloading new ones to prevent potential conflicts or confusion with multiple versions. open-source/guides/setup/docker-compose.mdx [33-39] -curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/docker-compose.yaml +rm -f docker-compose.yaml .env.example && curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/docker-compose.yaml ... curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/.env.example Suggestion importance[1-10]: 6 Why: Cleaning up old files before downloading new ones can prevent version conflicts and ensure that the setup uses the most recent configurations.	6
	✅ Ensure environment variables are correctly set by checking the .env file contents Suggestion Impact: The commit added a command to display the contents of the .env file after renaming it, which aligns with the suggestion to check the .env file contents. code diff: - mv .env.example .env + mv .env.example .env && cat .env ``` 5. Start the Multiwoven using the following command. @@ -80,7 +80,7 @@ 2. Download the production `docker-compose.yaml` file from the following link. ```bash - curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/docker-compose.yaml + curl -LO https://aiseepublicstorage.blob.core.windows.net/mw-public-main/docker-compose.yaml && echo "Downloaded docker-compose.yaml successfully" || echo "Failed to download docker-compose.yaml" ``` 3. Rename the file .env.example to .env and update the **PostgreSQL** environment variables. @@ -93,7 +93,7 @@ The default port for PostgreSQL is 5432. If you are using a different port, update the ```DB_PORT``` environment variable. ```bash - mv .env.example .env + mv .env.example .env && cat .env ``` Include instructions to check the contents of the .env file after renaming from .env.example to ensure all necessary environment variables are correctly set before starting the application. open-source/guides/setup/docker-compose.mdx [45] -mv .env.example .env +mv .env.example .env && cat .env Suggestion importance[1-10]: 5 Why: Checking the contents of the .env file after renaming it can prevent configuration errors and ensure that all necessary environment variables are set correctly.	5

[AngeloB-AIS]

@CodiumAI-Agent /describe

[QodoAI-Agent]

Title

fix: replaced urls for docker-compose and .env.example files

---

User description

I made an earlier overhaul of the docker-compose doc that turned out to be unnecessary. At present, only the URLs needed to be updated to resolve the issue of users not being able to access the cloud-postgresql version of the docker deployment (which, at this point, is essentially 1:1 with non-cloud-postgresql version). I left the clost-postgresql tab because it explains which variables the users need to change when using an external db.

---

PR Type

Bug fix, Documentation

---

Description

• Updated the URLs for downloading the docker-compose.yaml and .env.example files to new locations.
• Added verification messages to confirm successful downloads or report failures.
• Changed file extension references from .yml to .yaml for consistency.
• Modified instructions to rename .env.example to .env and print its contents to verify changes.

---

Changes walkthrough 📝

	Relevant files
Documentation	docker-compose.mdx Update URLs and instructions in Docker Compose setup guide open-source/guides/setup/docker-compose.mdx Updated URLs for downloading docker-compose.yaml and .env.example. Added download verification messages for files. Changed file extension from .yml to .yaml. Updated instructions to rename .env.example and print its contents. +11/-11

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[RafaelOAiSquared]

The section for In-Built PostgreSQL and the section Cloud PostgreSQL use the same docker-compose file.