Feature: Add mapped volumes to docker-compose

[BackedUpBooty]

Is your feature request related to a problem? Please describe. If the containers are removed, recreated or migrated then all tag/analytics information is lost.

Describe the solution you'd like Volume mappings which allows for mapped folders and data to be hosted as per the user's requirements for db/login/tag and platform info migration if/when necessary, something like:

mongodb:
  volumes:
    - ./data:/data

Describe alternatives you've considered Not sure what other container folders may need to be mapped so various configs persist

Additional context Add any other context or screenshots about the feature request here.

[cwbeck]

@BackedUpBooty - we're going to provide a number of self-hosted options/examples via docker-compose and Terraform.

Thank you for submitting the issue, but I'm going to close this out as it is now firmly on our roadmap.

[BackedUpBooty]

Understood, thanks for letting me know. I took a look through the repo, have you published a road map? I'd really like to keep up to date with this project.

[cwbeck]

@BackedUpBooty - internally yes, externally no. We had a rough high-level roadmap on our old README, but we have made changes (actually based on customer feedback!) and we are going to re-share it in a more structured way and perhaps using GitHub projects.

I'd 'watch' the repo for updates, we push releases out and detail changes there. You can also follow us on twitter twitter.com/scale8_com.

If you have any immediate requirements or suggestions though, we'd love to hear them. We've enabled discussions in the repo for exactly this. Our hope is features will get requested, upvoted and easier to prioritise. 💡

[BackedUpBooty]

Cheers, watched and starred, I'll head over to the discussions tab