1,097 karma · joined November 14, 2017
All databases that run locally (mongo included) are supported, here's the doc page for that: https://layerci.com/docs/advanced-workflows/layerfiles-can-s...
We have a secrets dashboard, they are stored encrypted in our database (though many users have something like hashicorp vault with a central repository, with only the access key stored in our database). The secrets are only viewable by admins of your organization.
Most of our users build their docker images within LayerCI, then push to ECS by adding a write-only access key as a secret. Deployment is often done with something like Terraform or ArgoCD.
Thanks for mentioning the typo!
We used to sell the features, but that actually didn't work super well - maybe we can add a "technical details" page for the nerds ;)
We also auto-hibernate the instances, so you don't have to pay for a bunch of separate databases running in parallel.
Don't just listen to me though, try the free tier for yourself! A lot of our users combine LayerCI for developer tooling and vercel/netlify/GCP/AWS for deployment, they're quite complimentary.
If your frontend/backend are in separate repositories, I'd reference this doc page: https://layerci.com/docs/advanced-workflows/routing
We even support self-hosted GitLab, so if you use a custom SSO provider there, developers could use that oauth flow for authentication + authorization.
You can "SNAPSHOT disabled" if you'd like certain steps to always run
Happy to chat more and send you some swag if you try it out and write a blog post about your experience :) colin@layerci.com
You can't 'FROM vm/osx' or 'FROM vm/windows' yet, it's relatively difficult to navigate licensing as a startup unfortunately.
This is actually exactly what our platform helps with - instead of micromanaging this (and updating the configurations) you can rely on a friendly SaaS to do it for you.
I wouldn't call us "better" than Docker, we're more like "Take Docker and make it work better for CI/CD and staging servers"
But I suppose "npm install" is a simplistic example, "npm run setup_our_ci_environment" would be a more likely step for a larger CI pipeline
There is in fact a burgeoning industry of devops consultants that set up CI pipelines for companies, I'd encourage you to consider it if you like the work!
A lot of our customers are in fintech (payroll, banking, etc) so we've spent a lot of effort on our security model: https://layerci.com/security
For databases - usually users have a named S3 bucket and use a secret to authenticate, since we take memory snapshots, the top of your Layerfile can be "start the database and populate it from this specific anonymized dump" and then you can edit the file in S3 and re-run without snapshots if you'd like to reload it.
Here's the doc page for that: https://layerci.com/docs/advanced-workflows/layerfiles-can-s...
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 script or docker container the same way you'd run it in production.
- 10 hours / month of maintenance + 200 hours of setup @ $60/hr = $13k in the first year, not including any infrastructure costs.
If you just redirected that money to a hosted offering you'd get significantly more powerful servers without needing to allocate engineering / management resources - it also makes it significantly easier to push updates & monitor uptime on the host's end.
Even traditionally hosted tools like Atlassian's suite are moving to cloud for the same reason: https://www.atlassian.com/migration/journey-to-cloud
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
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 (kubectl run cypress)
4(c) Create ephemeral environment (EXPOSE WEBSITE localhost:8000)
Because we take memory snapshots after each step, you'd effectively get a fresh, fully-provisioned kubernetes cluster immediately after pushing instead of re-running all the steps every time (you'd skip to step 3) and then run 4{a,b,c} in parallel (they'd all "fork" the VM and get a separate copy of all of the resources)
Here are a few links that go into more detail:
- https://layerci.com/docs/tuning-performance/run-repeatable
TL;DR:
1. Install on GitHub 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
Then just point it at a docker swarm cluster or run the standard docker/ecs integration: https://docs.docker.com/cloud/ecs-integration/
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/big-list-of-naughty-strings at master via a pull request [1].
[1] https://github.com/minimaxir/big-list-of-naughty-strings/com...
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 around with software, as well as discussing it and submitting your own favorites for the community to use.
Submitting is currently pretty difficult, but we'll try to add any projects you submit, even if you don't have a screenshot or staging configuration for it.
Our hypervisor does the logic though, we don't rely on the OS of the staging server itself for anything (think PXE)
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 tests.
> How do you run your layer file locally? They can be approximated by running a docker container and just copy/pasting the commands. We haven't built this yet because I know it will be a huge time sink to make it reliable (see, e.g., vagrant)
> Can you describe automated tests in a layer file? We tell you if any step fails (e.g., returns non-zero exit code) so you can just as easily run "./deploy.sh" as "./test.sh" - you can also start a webserver and run E2E or acceptance tests against it, for example.
> generate cross-service end to end code coverage We are trying to avoid anything that isn't very general - it's possible to run https://codecov.io/ within Layer if you want functionality like this.
Let us know if you have a chance to try out the tool and have any other feedback. :)