Shutting down
by Chris HardieI recently decided that it is time to shut down WP Lookout, and today I publicized an announcement about that and sent out notice to my users. I have a full "shutdown checklist" that I'll be working on over the next month. The announcement post summarizes my reasoning, basically that it's not providing enough value to enough people to justify the (relatively small but non-zero) time and expense involved. It's been a great experience and I'm so glad I built and launched WP Lookout. Now, on to other things!
-
1
Sorry to hear your project is shutting down. Will you be looking to put the code for it online anywhere in case someone else wanted to keep it running as is?
-
2
I'm open to sharing the code. It would be a non-trivial amount of work to prepare it for public release / open sourcing, so I don't think I will undertake that effort unless/until I understand that it would be beneficial for specific people/organizations/use cases.
-
1
What tech stack / platform does it run on? Taking a look thru your blog it looks laravel and on aws, but is there anything that closely ties to aws services that couldn't run elsewhere (Azure)?
I recently launched Site Assistant for WordPress (https://site-assistant.ourwebservices.co.uk) and am wondering how Lookout works under the hood and if there would be a away to have a synergy between the two.
Site Assistant can check sites after updates (and other on-page stuff) and think the tracking and notifications features could be useful.
It would be a shame for your hard work to simply turn off and it would be useful to learn what you have done. I haven't started on the customer portal / plugin route yet as still early days.
-
-