colinchartier

15 ms·

91.
by colinchartier 6y ago
One of the benefits of Layerfiles vs Dockerfiles is that those two examples will do the same thing - we monitor which files are read so you don't have to micromanage copying specific steps. But I suppose "npm install" is a si
92.
by colinchartier 6y ago
The type of CI you're describing would be in the "simple" category in the OP - if your goal is just "run a single docker build and check if it fails" there are lots of free hosted tools you can set up (github action
93.
by colinchartier 6y ago
We're actually in the process of getting SOC2 and pen tests ourselves - another benefit of a hosted offering is it can (eventually) integrate into your compliance system (e.g., vanta) A lot of our customers are in fintech (payroll, ban
94.
by colinchartier 6y ago
Thanks, Malthe - it's been great working with your team.
95.
by colinchartier 6y ago
If the state is broken, you can "rerun without snapshots" via the dropdown in the top right - and since future runs load the latest snapshot, they'd use a "clean" one. For databases - usually users have a named S3 b
96.
by colinchartier 6y ago
Hey Alok, RUN BACKGROUND basically does "./thecommand&" so it will stop after a restart, the onboarding example is ephemeral for simplicity. If you want things to persist across restarts you'd have to add a systemd s
97.
by colinchartier 6y ago
BYO resources for CI sounds good in theory, but considering costs it's almost always a worse proposition: - 10 hours / month of maintenance + 200 hours of setup @ $60/hr = $13k in the first year, not including any infrastruct
98.
by colinchartier 6y ago
Hey Kurt, we're big fans of fly.io! Happy to chat about tech sometime, I think you folks are using firecracker for a similar use-case? Drop me a line at colin@layerci.com
99.
by colinchartier 6y ago
With Kubernetes, a typical workflow might look like this: 1. Start kubernetes cluster 2. Build docker images 3. Deploy docker images (helm, kubectl, argocd, ...) 4(a) Run unit tests (kubectl exec -l k8s-app=web rake test) 4(b) Run e2e tests
100.
Launch HN: LayerCI (YC S20) - Staging servers that act like (and replace) CI
174 points by colinchartier 6y ago|61 comments
101.
by colinchartier 6y ago
We're building something like what you describe (YC S20) - 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&#x2
102.
by colinchartier 6y ago
The GitHub flavor of git essentially has two parts: Repository (i.e., minimaxir/big-list-of-naughty-strings), and branch (i.e., master) In this case, someone merged eliabieri/big-list-of-naughty-strings at master to minimaxir&#x2F
103.
by colinchartier 6y ago
Hey HN, We built this as a little hackathon project on top of our "get a dozen staging servers" platform at https://layerci.com The "show layer" gallery lets you create instantaneous staging servers to play a
104.
Show HN: Try out OSS webapps before installing them(show.layerci.com)
2 points by colinchartier 6y ago|2 comments
105.
by colinchartier 6y ago
Sort of, you can think of it as an entire socket-activated OS. Our hypervisor does the logic though, we don't rely on the OS of the staging server itself for anything (think PXE)
106.
by colinchartier 6y ago
> monorepo with many microservices We scan the entire repository for Layerfiles, so you could, say, create a layerfile per service for unit tests, and a bigger Layerfile in the repo root that does the whole deployment and runs a few E2E
107.
by colinchartier 6y ago
Thank you! It took a lot of refining to find a pitch that resonated. Let us know if you have a chance to try out the tool and have any other feedback. :)
108.
by colinchartier 6y ago
We (the founders) are heading off for the night. If anyone wants to get in touch, my email is colin@layerci.com
109.
by colinchartier 6y ago
1. Not yet unfortunately, we didn't want to waste time creating a separate auth system when we only integrate with GitHub for now anyways. To see a short demo though, here's an earlier one we made: https://www.youtube.c
110.
by colinchartier 6y ago
Would love to chat! Let us know if we got the right person on Linked In :)
111.
by colinchartier 6y ago
Glad you asked! If you do the Django tutorial after clicking "try now", you can see an example of a postgres database that gets set up for every run. Since we give full VMs instead of just containers, you can keep the database run
112.
by colinchartier 6y ago
Glad we're solving something that you empathize with. I'll never turn down a warm intro, so let me know if you think we'd be useful to any folks at your previous company.
113.
by colinchartier 6y ago
We think it's important to find a profitable path to beating Google or Amazon - even the best tech in the world will not convince someone to use your cloud service if they are afraid of counterparty risk. Our goal is actually to help t
114.
by colinchartier 6y ago
We do even more, we take snapshots as the "Layerfile" runs - this basically lets you merge the memory dump semantics you mention with the interface of Docker. Also, we monitor which files are read by any step in the process, and l
115.
by colinchartier 6y ago
Let us know what you think, and we'd be happy to jump in a call to show you a demo or get you set up.
116.
by colinchartier 6y ago
You should try it! Our baking interface looks more like Docker than a traditional VM provision (ala Packer) Also, we keep the baked images around for a week and trigger them whenever they are requested (with, say, HTTP, or terminal access)
117.
by colinchartier 6y ago
Sort of - FireCracker is less suited for testing use-cases because it still cold-boots. We use the same kernel features that let laptops resume when the lid is opened instead, they're less mature for production but much faster for stag
118.
by colinchartier 6y ago
We spent six months developing a hypervisor that lets us treat any linux VM as a lambda - We pass on the efficiency to our users as a value add.
119.
by colinchartier 6y ago
Hey HN, We're Lyn & Colin and we built Layer - It creates a unique staging server for every commit. Before Layer, I was CTO of a startup with a 10-person developer team, and dealing with staging servers (and end-to-end tests) was o
120.
Show HN: Layer – Get a dozen staging servers per developer(layerci.com)
155 points by colinchartier 6y ago|39 comments

More ›