3 ms·
We're building something like what you describe (YC S20) - https://layerci.com https://layerci.com - it's similar to OP but meant for standard containers instea
by colinchartier 6y ago
We're building something like what you describe (YC S20) - https://layerci.com https://layerci.com - it's similar to OP but meant for standard containers instead of serverless.
TL;DR:
1. Install on GitHub https://github.com/apps/layerci/installations/new https://github.com/apps/layerci/installations/new
2. Create files called 'Layerfile' to configure the pipeline
Docker Compose example for step 3: https://layerci.com/docs/examples/docker-compose https://layerci.com/docs/examples/docker-compose
Then just point it at a docker swarm cluster or run the standard docker/ecs integration: https://docs.docker.com/cloud/ecs-integration/ https://docs.docker.com/cloud/ecs-integration/
- zackmorris 6y agoThank you! I remember in the 90s, if I thought of a website or invention, I figured I had about 2-3 years to make it (certainly less than 5) before someone else did. That number dropped to maybe 6 months by 2010, and today most things are either about to be released or were released 2 weeks ago (minimum). So I'm not sure if I manifested what you made by needing it months ago, is what I'm saying. Anyway, the value proposition of LayerCI may not exactly be in the CI/CD stuff. What caught my eye was the 12 staging servers with high power CPUs and the layer caching like Docker (which takes multi-minute build times down to seconds). I think if you manage to include backups and monitoring from the start, you'll really have something. And if you've already done them, good job manifesting that.