eduardo at November 18th, 2015 18:01 — #1
If I create a self-hosted account, can I host multiple sites on it?
dkenzik at November 19th, 2015 08:05 — #2
If you setup Webhook on your own, you can certainly host multiple sites.
eduardo at November 19th, 2015 13:54 — #3
I think I may have not formulated my question correctly, I apologize.
What I mean, is, if I create a google/firebase/etc account to self-host, will that work for multiple sites or do I have to create a google/firebase/etc account PER site?
dkenzik at November 19th, 2015 13:59 — #4
The platform accounts you create (or use) are used for all of the sites that you create using "wh create -f xxxxx".
eduardo at November 19th, 2015 14:09 — #5
Ok, I'll venture and try to setup a self-hosting account
eduardo at November 20th, 2015 19:13 — #6
The self-hosting guide mentions Found.no for Elastic Search, but that's a hefty $45/mo. The guide does mention there are alternatives.
Can someone mention a free, or cheap one?
dkenzik at November 23rd, 2015 20:44 — #7
When I configured self-hosting I used a trial of Found.no just to get things going but ended up not continuing using it longer than the trial.
We've standardized on a Google CSE as it provides a better bang-for-the-buck at $100/yr for the non-ad-based results. And, in my experience, it's an easier expense to work into your client fees.
I think @budparr is self-hosting with many production sites. Maybe he has some feedback?
budparr at November 23rd, 2015 21:06 — #8
@dkenzik you're using CSE for the control panel search? I didn't know that's possible. I find the found.no (which I'm using and paying for) to be rather sluggish - I've created reports for clients on the front-end with their content listed and links to the edit screen to get around it. One of those things that if this were an active project we'd be trying to improve. I think my found.no bill is about $50/mo.
dkenzik at November 24th, 2015 11:12 — #9
@budparr - Sorry if I mispoke. I didn't realize the control panel uses Found.no, too. I was only referring to the public side of the site.
We don't self-host anymore and rely on Webhook's hosting.