This does have some security concerns as it provides information to a potentially bad actor that they did not have before.

The Rolify gem is great if the complexity is needed. Otherwise, I feel like this is a simple enough implementation that would accomplish many use cases as well as not introduce another dependency.

ah.. like it!

  nelsonchavespro  it looks like you're passing in the limit value as a string. What happens if you use an integer instead?

If you need other services like Sidekiq, ElasticSearch or anything else, you would be able to add the appropriate services in the docker-compose files. Yes, the DB, redis and other services (outside of the app services) should go on the managed services. This would provide a certain level of backups appropriately. 

It's also not ideal that the postgres, redis, etc are dockerized (whether it is in the docker swarm or kubernetes) since the service could become unhealthy and reboot at any point in time. Since these aren't redundant services, it could bring down the application unexpectedly while they're being restarted.

If you wanted to use managed services, you could still use the docker swarm and portainer. You'd need to pass the environment variables through to the app services which can be done through portainer or some other mechanism.