Discussions

Hi, is there a way to set up a test environment before going to production? I am migrating from Heroku and have recently containerized my application, I want to make sure nothing was broken during the process and do a test run of how MedStack works.

So there are 3 main concerns - How does my MedStack account handle backup/restore? Does my account have disaster recovery? Do you handle restore requests on weekends and how long does it take to restore? Is there a way I can get a file manager on my account?

We want to remove access to our developers to database and storage but want to leave them access to the control panel to supervise the process of deployment. We noticed that you provide 4 roles: Owner, Technical, Billing, and Compliance but none of them does not meet our expectations. Is it possible to configure medstack in a way to achieve it?

We are in the process of migrating our application from a monolith to a micro-services approach and will need the ability to apply updates to service containers in a rolling fashion. Are there any plans to expose update related flags in the service configuration? Most likely we would require these flags: --update-delay --update-parallelism --update-failure-action --stop-grace-period And it would be nice to also have access to these: --update-max-failure-ratio --update-order For now, can you provide us with the default values for these flags? Any update on this would be appreciated it since it will most likely be a hard requirement for new deployments in the near future and would like to make sure that the values used would be appropriate for us. Thank you!

How does Medstack ensure that deleted data is in fact deleted by the underlying cloud provider is there a time interval after which this occurs.

By default, the MongoDB image persists its database under a volume located at `/data/db`. Any idea how I can change this via Medstack control? This is easy enough to configure in a docker-compose file, as represented below. With the following configuration, the MongoDB database gets stored under `/mongodb/data` instead of `/data/db`. I'd like to match this behavior in my MedStack cluster. ``` mongo: container_name: mongo-server image: mongo environment: MONGO_INITDB_ROOT_USERNAME: **** MONGO_INITDB_ROOT_PASSWORD: **** volumes: - /mongodb/data:/data/db ports: - 27017:27017 ``` References: https://www.mongodb.com/compatibility/docker https://hub.docker.com/_/mongo

Is there any way to access Docker nodes, services container performance metrics like CPU & memory utilization, storage consumption, or I/O other than though the dashboard ??

How can I get my app service to communicate with my redis service? I currently am setting the `REDIS_URL` in my application to `redis://host.docker.internal:6379/0`, but I can't seem to connect.

There is an old invitation for a user that I want to delete. But my only option is to "Resend". I don't want to do that.

Is it possible to run Mirth Connect on MedStack Control?