not sure if this by design or a little small bug thing, but when you bootstrap a new project (we got the option to create a project) it places the .env outside of the project, both docker compose or node will not call the .env generated by the dockerize tool (at least my enviroment didn't)
the docs/readme don't mention we should move the .env, so i believe this was not intentional?
🤷♀️ What did you do
npx @strapi-community/dockerize@latest
🕵️♀️ Stack trace
@strapi-community/dockerize v1.16.2 by Simen Daehlin
Easy add docker support for a Strapi Project
https://github.com/strapi-community/strapi-tool-dockerize
🎉 You, and 1477 other people have used this tool this month
🍿 JavaScript project detected
📂 Detected Yarn & NPM ...
✔ Which package manager do you want to use ? (Strapi Recommends yarn) › Yarn
📦 Using YARN
⛔️ Strapi project not detected
✔ Do you want to create a new Strapi Project … Yes
✔ Whats the name of the project? … strapi-dockerize-test
✔ Do you want to use TypeScript … Yes
✔ Do you want to assign a path for new project ? (leave blank for current directory ) … <pressed enter> /home/ubuntu/Desktop/strapi/strapi-install
📝 Path is valid, proceeding!
🚀 Creating Strapi Project from npx create-strapi-app@latest - please wait...
npm WARN
exec The following package was not found and will be installed: create-strapi-app@4.14.5
Creating a quickstart project.
Creating a new Strapi application at /home/ubuntu/Desktop/strapi/strapi-install/strapi-dockerize-test.```
-----
? Do you want to create a docker-compose file? 🐳 › Yes
🐛 Bug Report
not sure if this by design or a little small bug thing, but when you bootstrap a new project (we got the option to create a project) it places the .env outside of the project, both docker compose or node will not call the .env generated by the dockerize tool (at least my enviroment didn't)
the docs/readme don't mention we should move the .env, so i believe this was not intentional?
🤷♀️ What did you do
🕵️♀️ Stack trace
👩💻 Environment
📺 Additional context/Screenshots