I am thinking of trying to implement push notifications into my website. Essentially I would just need to message individual users of personal updates not everyone that has agreed. I have looked and researched a lot and its confusing where to start, what I need, what language to use etc.
I use 1and1.co.uk for my hosting and would like to use PHP to instigate the push. Is this possible from what they offer and if so where do I start?
All the paid stuff seems to offer just bulk notifications and that is not what I need and why should I pay for it if its possible to do myself.
Also how difficult and time consuming is the process?
If I get enough advice and manage to get it working, I will write a step by step tuition as there is nothing out there with a simple answer and instructions.
Thanks and regards
If you don't need it in time, you can do it using Ajax polling, which means executing Ajax requests every few seconds.
Related
I am in the process of delivering a product.
What my product needs to do is spin up and down multiple instances on google cloud.
Basically, I have a main instance which I plan to control the rest of them. A 'worker factory' if you will.
What would be a good way to communicate results from the workers back to the main instance.
The actually worker already inserts its results to a sql table also hosted by google, before spinning down.
However I am looking to additionally send off a log file to the main instance.
What would be the best way of doing this?
p.s - I am not extremely familiar with networking, however I am looking to learn
There are likely many ways to achieve your goal. One thought is to use Publish/Subscribe. In this concept, you create a resource called a topic and your main instance would register a subscription to the topic. Now, when your workers wish to transmit information they would executed a publish on the topic. There is no networking knowledge needed to make this all work. The topic becomes a centralized drop-off for information published.
Here are the docs on pub/sub: https://cloud.google.com/pubsub/docs/
I work for an advertising agency working with several clients who we are building and managing wordpress websites for. One issue that arises every time with a new install, is the issue with emails not sending/receiving. We usually solve this by installing an SMTP plugin and set it up using the clients Office 365 email account or whatever provider they have.
The problem is that this is a little time consuming, as well as some of our clients either don´t want to give away their account information/they don't know their account information/they change passwords and forms stop working.
We need a stable email solution that we can use on a wide spectrum of client pages, and that we hopefully don´t need to set up every time we make a new webpage. Does anyone have any solutions/suggestions for this?
Any help would be greatly appreciated.
Before I get into the recommendation, WordPress should use your servers default sendmail configuration so it’s possible something is misconfigured here as it should work out of the box.
But if you want something a little more bulletproof I recommend SendGrid.
One of the problems with all your sites using the same mail server is if one is blacklisted for something the others go down. With SendGrid, which is free for 10k send a month I think, you can issue an api key for each site and if one has an issue it you can easily identify it in SendGrid.
I have setup dozens of API Keys and the plug-in. It’s fast and simple and takes about 5 minutes in total. They have great delivery, detailed reports and are cheap even if you need a lot of sends.
You can Signup for an account and use the SendGrid plugin from the Wordpress repository.
I'm using Application insights for outside-in testing, but my code is not instrumented with it. I don't want to receive the weekly email summary about my service, since most columns are blank.
How can I disable the email being sent? (Note I do not want to just unsubscribe myself from it)
It appears this is not available yet, though someone has proposed it on the Application Insights uservoice site, and AI folks have commented on it:
https://feedback.azure.com/forums/357324-application-insights/suggestions/14444583-ability-to-disable-weekly-digest
I'd suggest upvoting that if you need it.
While not what you want, it looks like the only option at this time is to unsubscribe.
As of 6/18/2018, application insights is no longer sending digest emails at all.
see https://learn.microsoft.com/en-us/azure/application-insights/automate-custom-reports for details, the suggestion is to use other tools, like Logic Apps or Flows to query and generate your own content.
Best I could find was this wiki entry
I I thought "surely there must be more to it than this".
Am I missing something?
From the doc:
What is WebHook?
The concept of a WebHook is simple. A WebHook is an HTTP callback: an
HTTP POST that occurs when something happens; a simple event-notification via HTTP POST.
A web application implementing WebHooks will POST a message to a URL
when certain things happen. When a web application enables users to
register their own URLs, the users can then extend, customize, and
integrate that application with their own custom extensions or even
with other applications around the web. For the user, WebHooks are a
way to receive valuable information when it happens, rather than
continually polling for that data and receiving nothing valuable most
of the time. WebHooks have enormous potential and are limited only by
your imagination! (No, it can't wash the dishes. Yet.)
Why should I care?
As integrated as we perceive the web, most web applications today
operate in silos. With the rise of API's we've seen mashups and some
degree of integration between applications. However, we have not seen
the vision of the programmable web: a web where you as the user can
"pipe" data between apps much like the Unix command line. Some say RSS
is the answer. They are wrong. The heart is in the right place, but
the implementation is wrong. RSS is still useful, but it is not going
to bring us the true programmable web.
We just need a simple way to get data out in real-time to let the user easily do whatever >they wantwith it. That means no polling, no content constraints, and no XML
parsing. That means no RSS. Using HTTP is simpler and easier to use.
PHP is a very popular and accessible programming environment, so it's
likely to be used often for writing hooklets... getting data from a
web POST in PHP is as simple as $_POST['something']. And making the
request to the user script is as simple as making an HTTP request,
something already built-in to most programming environments. In fact,
web hooks are easier to implement than an API.
I am looking for a product to solve a particular task and I'm having a hard time sorting out which product or type of product can accomplish the task. I am looking for something to handle POSTing notifications via HTTPS.
One of my use cases is a mechanical turk type scenario. A client will request a task be started via an API call. A human will get this request do the task, tell the system the task is complete, and the system will send a HTTPS POST to a subscriber. So it's a long-running async request.
I am looking for something that will take care of making this POST for me. I would like something that is reliable and durable. Of course I can write the POST myself, but all of the other niceties that come with a queuing application would be nice to have (and I don't wish to implement all that myself).
I have been looking at a number of queuing, MOM, and ESB products. From what I can tell the queuing products don't seem to push notify over HTTPS and the MOM and ESB are a little too heavy handed I think. For example I think BizTalk will do what I need but that has a lot of overhead. The one solution I did find was Amazon's Simple Notification Service, but that appears to only send from the amazon.com domain, but I want the messages to be sent from my domain.
Can anyone help identify a product that will help? Maybe I'm just overlooking something, not sure what I am looking for, or have to choose a different way of implementing this.
The answer I was looking for was webhooks. Here's a great presentation on what they are and how they can be utilized.
if you want a serverless way to do webhooks, check out IronWorker's webhook support, here's an article on it: http://blog.iron.io/2012/04/one-webhook-to-rule-them-all-one-url.html
nginx has a messaging module that may be just what you need.