Volume directories not created

[msamblanet]

When running nvl init, the resulting docker-compose.yml references a number of folders for mapping volumes that do not exist. I believe it would be best if these folders were created by the init process.

If the team agrees, I can provide a PR to add this to the initialization.

[adalinesimonian]

What folders in particular seem to be the culprits?

[christiansmith]

I'd guess views, email, public, keys... are there more?

[msamblanet]

Just did a fresh build - the following volume directories did not exist:

• redis/data
• redis/logs (well this is future for Redis logs volumes not mapped for docker #32)
• connect/email
• connect/protocols
• connect/providers
• connect/public
• connect/views
• nginx/logs

Is it possible these are auto-created by docker-compose? They were not created by docker create or docker run...

[adalinesimonian]

So the status quo is currently:

Directory	Why it may not be there by default
connect/keys	Created in unreleased version of connect-cli
connect/email	Optional, only necessary if overwriting/adding email templates
connect/protocols	Optional, only necessary if overwriting/adding protocol definitions
connect/providers	Optional, only necessary if overwriting/adding provider definitions
connect/public	Optional, only necessary if overwriting/adding static assets
connect/views	Optional, only necessary if overwriting/adding view templates
redis/data	?
redis/logs	#32
nginx/logs	#32

[adalinesimonian]

@christiansmith What's up with redis/data?

[christiansmith]

redis/data I believe is created also when the containers are launched by docker compose.

[christiansmith]

Given that not everyone using Docker will use Docker Compose, I think we should definitely create the mandatory directories with nvl init.

[msamblanet]

I'll submit a CR for the "init' command to pre-create all the folders - should be up shortly. Even if not needed in all cases, it should not hurt.

[adalinesimonian]

Fixed by #35