Tried to figure out what it actually is but this blurb left me perplexed
> Bedrock is a static site generator that enables design and dev teams to efficiently work together. It is a perfect tool for design agencies looking for a perfect deliverable for developers to work with, neatly splitting the line where coding designers shine and developers should take over.
I guess it's just a perfect static site generator that shines sometimes.
It isn't very impressive scaling given what are relatively low numbers in the internet age. We aren't really talking much more than 100 requests/posts a second. I have old Rails sites that put through more than that on a 10-year-old CPU.
I am wondering what the issue is, both in why it is failing on relatively low traffic numbers and also why it is they are struggling to fix it for over 3 hours at this point.
Koru Kids | London | Full-time Onsite | Full Stack Ruby Engineer #4 | https://www.korukids.co.uk/
Koru Kids is growing quickly. We’re on a mission to improve childcare in London, and looking for someone experienced, creative & friendly to join the team as our fourth full stack engineer.
We’re building a managed marketplace that enables families to find and share high quality nannies. As an engineer on the Koru Kids team, you’ll be designing and building tech to make complex matching problems a breeze, to give families and nannies a solution that just works, and to supercharge our nanny recruitment and training processes.
You’ll be working in Ruby for most of the backend, with Rails, PostgreSQL and Redis making up the majority of our core product. You’ll be using modern frontend tooling, with ES6 and Tachyons. When it comes to shipping code, you’ll be sending pull requests and doing code reviews in GitHub, and checking that CircleCI is happy before anything goes live. You’ll mostly be deploying to Heroku, with some heavy lifting on AWS. (That said, our priority is making sure we’re using the right tools for the job and we’re open to adding to or changing up our tech and tooling as appropriate.)
We’re looking a mid-level or experienced generalist or backend web developer who thrives in small, fast-moving engineering teams.
Koru Kids is growing quickly. We’re on a mission to improve childcare in London, and looking for someone experienced, creative & friendly to join the team as our fourth full stack engineer.
We’re building a marketplace that enables families to find and share high quality nannies. As an engineer on the Koru Kids team, you’ll be designing and building tech to make complex matching problems a breeze, to give families and nannies a solution that just works, and to supercharge our nanny recruitment and training processes.
You’ll be working in Ruby for most of the backend, with Rails, PostgreSQL and Redis making up the majority of our core product. You’ll be using modern frontend tooling, with ES6 and Tachyons. When it comes to shipping code, you’ll be sending pull requests and doing code reviews in GitHub, and checking that CircleCI is happy before anything goes live. You’ll mostly be deploying to Heroku, with some heavy lifting on AWS. (That said, our priority is making sure we’re using the right tools for the job and we’re open to adding to or changing up our tech and tooling as appropriate.)
We’re looking a mid-level or experienced generalist or backend web developer who thrives in small, fast-moving engineering teams.
Koru Kids is growing quickly. We’re on a mission to improve childcare in London, and looking for someone experienced, creative & friendly to join the team as our second full stack engineer.
We’re building a marketplace that enables families to find and share great quality nannies. To do this, we’re building great software for our families, supporting our matching team with critical tools that make complex matching problems a breeze, and using technology to supercharge our nanny recruitment and training processes.
We’re continuously improving our product, building key features that will move the needle in a big way. Instead of an endless product roadmap, we run short development cycles to test assumptions and make smart decisions quickly. This isn’t a sprint and there’s no project managers, we work closely with the rest of the business to make sure we deliver the most value to our customers.
Our stack uses Ruby for most of the backend, with Rails, PostgreSQL and Redis making up the majority of our core product. We use modern front end tooling, with ES6, React and Tachyons. When it comes to shipping code, we love GitHub code reviews and making CircleCI happy before anything gets into production. We mostly deploy to Heroku, with some heavy lifting on AWS. We favour feature flags over staging environments and deploy to production as often as we need to; deployment cycles shouldn’t get in the way of delivering value.
We’re looking for an experienced Ruby developer who thrives in small, fast-moving engineering teams.
Koru Kids is growing quickly. We’re on a mission to improve childcare in London, and looking for someone experienced, creative & friendly to join the team as our second full stack engineer.
We’re building a marketplace that enables families to find and share great quality nannies. To do this, we’re building great software for our families, supporting our matching team with critical tools that make complex matching problems a breeze, and using technology to supercharge our nanny recruitment and training processes.
We’re continuously improving our product, building key features that will move the needle in a big way. Instead of an endless product roadmap, we run short development cycles to test assumptions and make smart decisions quickly. This isn’t a sprint and there’s no project managers, we work closely with the rest of the business to make sure we deliver the most value to our customers.
Our stack uses Ruby for most of the backend, with Rails, PostgreSQL and Redis making up the majority of our core product. We use modern front end tooling, with ES6, React and Tachyons. When it comes to shipping code, we love GitHub code reviews and making CircleCI happy before anything gets into production. We mostly deploy to Heroku, with some heavy lifting on AWS. We favour feature flags over staging environments and deploy to production as often as we need to; deployment cycles shouldn’t get in the way of delivering value.
We’re looking for an experienced Ruby developer who thrives in small, fast-moving engineering teams.
Koru Kids is growing quickly. We’re on a mission to improve childcare in London, and looking for someone experienced, creative & friendly to join the team as our second full stack engineer.
We’re building a marketplace that enables families to find and share great quality nannies. To do this, we’re building great software for our families, supporting our matching team with critical tools that make complex matching problems a breeze, and using technology to supercharge our nanny recruitment and training processes.
We’re continuously improving our product, building key features that will move the needle in a big way. Instead of an endless product roadmap, we run short development cycles to test assumptions and make smart decisions quickly. This isn’t a sprint and there’s no project managers, we work closely with the rest of the business to make sure we deliver the most value to our customers.
Our stack uses Ruby for most of the backend, with Rails, PostgreSQL and Redis making up the majority of our core product. We use modern front end tooling, with ES6, React and Tachyons. When it comes to shipping code, we love GitHub code reviews and making CircleCI happy before anything gets into production. We mostly deploy to Heroku, with some heavy lifting on AWS. We favour feature flags over staging environments and deploy to production as often as we need to; deployment cycles shouldn’t get in the way of delivering value.
We’re looking for an experienced Ruby developer who thrives in small, fast-moving engineering teams.
Thanks! Yes this file could be used to see the compoments needed to install redash.
However I'd really prefer some complete step-by-step instructions to actually understand better what's going on. For example similar to the instructions gitlab provides for installing in your server (https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...)
