3 ms·

I'm not familiar enough with the gaps between Github Actions and Docker compose to understand fully what this is doing. I recall when I deployed my first docke

I'm not familiar enough with the gaps between Github Actions and Docker compose to understand fully what this is doing. I recall when I deployed my first docker-compose app it took less than 5 minutes (create droplet, login, git clone, copy in my secrets, docker-compose up) I left that droplet running ($20/month) but if I wanted to tear it down regularly then it's a short script to do so. Now - I'm pretty green on all this stuff and it was brain-dead simple even for me. What's the gap I'm missing that you're trying to fill?

crohr 6y ago
It may be simple for you to do, but you just described having to provision a server, manually checkout your code using SSH agent forwarding or HTTPS auth, setup your environment variables, and then launch the app. And manually repeat the last steps as many times as you push to your branch. At this point you’re the only one to know about your preview server, and you need to not forget to destroy it when you’re done. PullPreview handles all of the synchronisation mechanism, as well as providing pretty URLs, automated SSH access to any GutHub users, source IP filtering, port firewalling, HTTPS support etc. Plus the whole integration into GitHub so that you don’t need to retrieve the preview URL by yourself, and you get notified if anything goes wrong during the deploy, with full logs available. That’s the gap we’re trying to fill :)