You're right, our own landing page is very simple and so are the landing pages we generate.
It's also a very competitive space with online website builders like Squarespace, Wix, Typeform and many, many others. With this early version of LampBuilder, our main differentiators are the startup focus, the speed with which you can get your site ready and the fact that we're free for use with custom domains.
Your suggestion of examples on the home page is a good one. We'll also need to work hard to ensure there is a compelling enough reason for startups to choose LampBuilder over all the other options for landing pages.
Hi Matt, thanks for taking the time to test it out for giving detailed feedback!
It looks like your page triggered a bug in our publish flow. I've applied a fix and so your published site should be working again now.
Thanks for the encouragement and the suggestions, it's great to hear from someone who builds landing pages from a living! They're all good suggestions and we'll keep them in mind as we iterate on the product.
Thanks! That's good feedback, currently the images are selected from the open source collection at https://undraw.co, but as a next step we'll add the option for AI generated images.
I mentioned it in a comment above, but one way in which it feels shoehorned in is the fact that you can only have one Firestore per Google Cloud project. Having only one Firestore per project makes setting up test or staging environments a hassle.
Hi, I’ve enjoyed using Firestore so far, but one aspect I find very limiting is the fact that you are limited to one Firestore database per Google Cloud project. Are there any plans to change this? Allowing multiple Firestore databases would make setting up staging and testing environments much easier.
Hi there. :) I'm an engineer on the Cloud Firestore team. I can't speak to if or when we'll be able to remove this restriction, but please know that the folks working on this (like me) are very aware of what a pain in the butt this is. I'm sorry that I can't give you a more satisfying answer, but I hope we'll be able to change this soon. Thanks for being a customer!
When deciding to go with Patroni, did you have a look at CruncyDB? We're deciding between the two and kubernetes support on CrunchyDB and documentation seems to be more comprehensive.
It looks like you are talking here about postgres-operator by Crunchy
Yeah, crunchy was a little faster with releasing it than Zalando, but try you look closer how they deploy postgres on kubernetes.
Somehow it feels that they are trying to map 1 to 1 the same approach how folks used to run postgres on bare metal. That is: deploy master pod, wait until it's up and running, deploy a replica pod, and so on...
It doesn't really look cloud-k8s-native.
In my opinion such deployment should look absolutely different. You just need to deploy k8s manifest, which will create Secrets, StatefulSet and Service which will be used to connect to the master.
The rest should happen automatically:
* StatefulSet will start N pods with postgres
* pods (Patroni) will elect leader.
* elected leader will initialize (initdb) a new cluster
* all other pods will get basebackup from the leader and become replicas
* if the master(leader) pod die - other pods will elect a new leader
* StatefulSet will start a replacement of failing pod and it will join the cluster as a new replica
And more important all it should happen without connection to Etcd, ZooKeeper or Consul. It should just use Kubernetes API.
The idea of wallets with dozens of digital currencies ties in with another idea which I've been intrigued by recently.
Apart from the payment mechanism functionality, units of cryptocurrency are much like shares in a company.
The Cypherfunks experiment (www.thecypherfunks.com) illustrates this concept: Imagine anybody could own shares in the music industry. To make this possible bands simply accept payment in a specific cryptocurrency (e.g. FUNK). As more people support bands using this form of payment, the value of the cryptocurrency grows and the entire network of bands and their supporters benefits.
It's also a very competitive space with online website builders like Squarespace, Wix, Typeform and many, many others. With this early version of LampBuilder, our main differentiators are the startup focus, the speed with which you can get your site ready and the fact that we're free for use with custom domains.
Your suggestion of examples on the home page is a good one. We'll also need to work hard to ensure there is a compelling enough reason for startups to choose LampBuilder over all the other options for landing pages.