zener79
Joined 10 years ago
Karma
47
Submissions
32
Member since
Dec 15
Recent submissions
Comment · 9 months ago
Comment · 8 years ago
Hi, and many thanks for your comment :-)
Currently the search engine we offer with HardyPress is very simple: we index the site content during the deploy process and we provide APIs to retrieve results (or you can use our native modal box with no additional coding).
You can read more about this here: https://www.hardypress.com/guides/hardypress-site-search/
Regarding plugins, currently about 90% of the plugin we reviewed are fully compatible, because the do not have any dynamic behavior on the frontend. If your site use some plugins marked as "incompatible", our system suggest you an alternative to replace the plugins behavior.
I perfectly understand your concern about HardyPress being a new "hosting provider", but HardyPress infrastructure is entirely built on the cloud, currently on Amazon AWS and the static generated sites are hosted on Amazon S3 Buckets that we use as pull-zones for the CDN, so your websites are really unbreakable and they'll stay up, no matter what!
You don’t need to trust us to feel safe!
If you want to have full control of your data you can always download your static generated site and host it somewhere else as your wishes. In this way you will use HardyPress only as a Static Site Generator plus the benefits that we will proxy your contact forms, and we'll make the search work!
Comment · 8 years ago
Yep, you get the point.
Plugin support is a real challenge... anyway we are seriously building a white list of compatible plugins, and so far they are about 90% of the total. For the remaining 10% it is usually always possible to replace them with some external service (facebook-comments or disqus for comments, our Zapier app for mailchimp/drive/dropbox integration, beds24 as booking system, etc)
We also thought about something like your idea (keep a second installation live somewhere to submit the data), but, as you will have to host your real WP somewhere, you will lose one of the main benefits of HardyPress, namely to have your site unbreakable.
Comment · 8 years ago
Ok, about this we will release soon a new feature where users will be able to deploy their static site on a custom ftp/sftp server.
Adding a git repo as destination won't be a problem :-)
Comment · 8 years ago
I see your point, but I also think that most of the value in what we are offering here is the ability to turn WordPress on/off on demand, so you can forget about it after the changes.
How could this be achieve without hosting files and DB?
Comment · 8 years ago
Actually there are a couple of things that I'd like to clarify:
1) There is no WordPress backend to maintain as it doesn't exists unless you turn it on in a temporary/hidden/virtual environment to make your changes. For the rest of the time it simply doesn't exists. No PHP, no MySql, nothing that can break. You don't even need to keep your installation updated if you don't want to.
2) The pages are not served from an S3 bucket but from a CDN with 20 edge server around the world. The bucket is only a "source of true" where the CDN loads the files when the "cache" is invalidated. This reduce the TTFB (Time to first byte) up to 10x from any location respect a traditional hosting service.
Comment · 8 years ago
There are already some plugins that "staticize" your website, but
1) you still need to have and maintain secure the WordPress Installation somewhere. With HardyPress WP can be paused and restored when needed with a click.
2) you have to download the static version and upload it somewhere else manually (your client certainly can't do it on their own). HardyPress does it with a click.
3) contact forms and search will stop working. With HardyPress, if you use CF7, everything will work seemlessy.
To solve the problems above HaryPress needs to hosts your WP installation.
Comment · 8 years ago
Many thanks Jason for your effort on posting it on ProductHunt.
We were thinking of postponing the launch on PH when the new version of the site is ready, but that's okay :-)
You don't need to transfer the domain to us (we are not registrar), you just need to set a CNAME when your site on HardyPress is production ready
Comment · 8 years ago
404 for me. Maybe it is a private repo and you are logged in
I built LastSignal because I was uncomfortable trusting a third party with extremely sensitive information (final messages, recovery instructions, etc.).
LastSignal is a self-hosted dead man's switch: you prepare encrypted messages that are automatically delivered to chosen recipients if you stop responding to periodic check-ins.
Security-wise, the server is treated as untrusted by design:
- messages are encrypted client-side
- the server never sees plaintext
- the operator cannot decrypt stored data
I've documented the security model, threat assumptions, and known limitations here:
https://lastsignal.app/security/
Source code:
https://github.com/giovantenne/lastsignal
This is an early but usable version. I'm especially interested in feedback on the threat model, edge cases, and assumptions around liveness and delivery.
Happy to answer questions.