add init / avoid removing .env

[delcroip]

add init to start from env file, this is usefull for duplicating a project for instance to create a dev version

remove just rename .env to avoid loosing the db key

Project name added on the compose to be able to still use docker-compose command

correct URL if COMMOM_NAME used

[delcroip]

i see your point with init, so I create recreate to start for an existing env file and init just create an env file

[delcroip]

here the doc for PROJECT_NAME https://docs.docker.com/compose/reference/#use--p-to-specify-a-project-name

[mrjones-plip]

Hi @delcroip - I was on holiday for the month of July - sorry for the delay in getting back to you. I'll jump into this PR in the next week or so.

[mrjones-plip]

Thanks for the continued work on this!

After jumping back into the code, I think I'm lacking a larger picture of what the use case is here for init and recreate. Can you do a brief write up of the real world problem you're trying to solve?

[garethbowen]

@delcroip Thanks for this! Do you have time to dust it off and work on the feedback that @mrjones-plip shared?

[delcroip]

Thx I will check, i am currently checking using container_name directive In the compose to allow both the scripts and plain compose usage