Depends on what you call a personal project, it might even be an overkill for some. My problem with it is that it does not seem to be as actively developed and gaining traction as other alternatives and support for it might get removed in the future. That is only an assumption though, I've used it before and it is much easier to start with than k8s.
For really simple cases what worked well was to use docker-machine to provision a remote host. When developing I'd use the local docker, for production I'd switch the active docker to the remote host via docker-machine and just use docker-compose to bring a container up and down.
For really simple cases what worked well was to use docker-machine to provision a remote host. When developing I'd use the local docker, for production I'd switch the active docker to the remote host via docker-machine and just use docker-compose to bring a container up and down.