nekrasovp commented on issue #8688: URL: https://github.com/apache/incubator-devlake/issues/8688#issuecomment-3839683755
Thanks for the response @dosubot! However, I need to clarify the actual issue here. The problem isn't about finding files in the repository - the `docker-compose.yml` file doesn't exist in the `main` branch at all. Looking at the repository structure, I can only find `docker-compose-dev.yml` which is specifically for development purposes, not production deployments. Historically, the release process worked like this: Pre-v1.0.0 releases (Working as documented): - Release artifacts included docker-compose.yml and env.example as downloadable files - These files were also committed to devops/releases/lake-vX.X.X/ directory - Users could follow the [official documentation](https://devlake.apache.org/docs/GettingStarted/DockerComposeSetup/) which says: _"Download docker-compose.yml and env.example from the latest release"_ v1.0.0+ releases (Broken): - Release artifacts no longer include `docker-compose.yml` and `env.example` - No files in `devops/releases/` for these versions - The [Release SOP documentation](https://devlake.apache.org/docs/DeveloperManuals/Release-SOP/) explicitly states these files should be uploaded: _"Open the URL https://github.com/apache/incubator-devlake/releases/, draft a new release, fill in the form and upload two files docker-compose.yml and env.example"_ - Official setup documentation is now broken since there's nothing to download Current confusion: - There's no docker-compose.yml in the main branch (only `docker-compose-dev.yml`) - There are multiple compose files scattered in the repo with different purposes - It's completely unclear which file new users should use for production setup - The documented installation process literally cannot be followed Questions: 1. Was removing `docker-compose.yml` and `env.example` from v1.0.0+ releases an intentional breaking change? 2. If yes, which compose file should users use for production? Should they create their own based on `docker-compose-dev.yml`? 3. If no, can these files be restored to the release artifacts and `devops/releases/` folder? 4. Should the documentation be updated to reflect the new process (whatever it is)? This creates a significant onboarding barrier for new users trying to follow the official installation guide. Any clarification would be greatly appreciated! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
