Closed beonma closed 3 weeks ago
Thank you for opening your first issue! 🙏❤️ One of our team members will review it and get back to you as soon as it possible. 😊
@beonma thanks for raising an issue an proposing a solution 😊 Can you maybe open a PR wit these changes? I think we can also fully move over to the new “docker compose” command without supporting the old one. In dev environments it’s easier for us to enforce this 😊
Hey @mattinannt ! for sure, I've submitted a pull request with the mentioned changes, including updates to a documentation file. Please feel free to make any necessary additions or deletions as you see fit.
Issue Summary
While working on the project, I opted to utilize the local development environment. After cloning the repository and installing the necessary packages, I attempted to initiate the development environment with the
pnpm go
command, which relies on Docker. However, the command failed. Upon investigation, I discovered that the failure was due to the deprecation of thedocker-compose
command in newer versions of Docker.Steps to Reproduce
Expected behavior
should start a development environment.
Other information
Below is a basic solution I made to address the issue in the
scripts
property ofpackages/databse/package.json
:I'm not sure if this will suffice for now, but at least I haven't encountered any noticeable issues thus far.
Screenshots
No response
Environment
Desktop (please complete the following information)