How does your business respond to customer concerns and inquiries? Do you have a social customer care plan in place? To explore how to improve customer care for your business, I interview Dan Gingiss. More About This Show The Social Media Marketing podcast is an on-demand talk radio show from Social Media Examiner. It’s designed [...]
This post Social Customer Care: Apps and Processes for Success first appeared on .
- Your Guide to the Social Media Jungle
Appico is a user experience and interface design studio. We help enterprises approach things from the needs of the user and turn complex processes into simple and consumer relatable solutions.
There are many situations in which you might decide that self-hosting your website is the way to go. You may be a freelancer, an entrepreneur, or be running a personal or even non-profit site. You may wish to host the site on an always-on PC in your basement, or on a small server in your workplace.
Regardless of the situation, on-premise hosting is usually a bad idea. In this post, you'll have some reasons for that explained, in the hopes of providing useful information or warnings to both business decision makers as well as developers who are inexperienced with the "operations" side of the Internet - in this case, hosting websites.
Depending on your Internet Service Provider (ISP) and your situation (whether you have a business class service package or a residential one), you may run into issues with your ISP blocking port 80 — the port to which most Internet traffic defaults. You may also be issued warnings or even have your service shut down if you host websites on-premise. This is most common when you are trying to host a site from your home connection and the ISP prefers that if you wish to do so, you purchase a business Internet package that is perhaps thrice as expensive.
However, some ISPs can still provide limitations even to the business class packages that can thwart your attempts to get your website up and running. Additionally, you will also need a static IP address, which may be an added cost, depending on how your ISP plans work. Most home (and some business) connections use dynamic IP addresses, which means that they change from time to time. If your IP address, the way by which your network can be found online, sometimes changes, you will have no easy, reliable way to point users who come to yourdomain.com to your on-premise hosting setup.
There are security risks in anything you do on the Internet, of course, but hosting a website on your network opens you up to even more, especially if you're not certain of what you're doing. Websites big and small are subjected to denial of service attacks and scripting attacks, sometimes at mind-blowing volume. Your website can be for a single freelancer, a small startup, a two hundred person small company, or an enterprise outfit, and they all will attract attacks — some of which may even be automated and not even take into account the content of the site in question.
Hosting a web server on your network, if you're not careful, may open your network up to a Pandora's Box of security troubles that you'd never have to deal with if you hosted your website with a cloud service provider rather than on premise. Do you know enough about web servers (and, if your web server is Linux, do you know the command line)?
Another point to consider about self-hosting your website is that you have less options for dealing with things like downtime and service outages.
If your power goes out in the typical residential or small business location, you have no control over the situation that follows. How long will it be out? Minutes? Hours? Days, even? It depends on the circumstance. What if a child touches or damages something they shouldn't, if it's in your home? What about in the office, if a careless employee spills a drink, or pulls the wrong cord?
Even if you secure your website on a server in a server cage in a dedicated room in your office, you can still run into random events such as a plumbing leak or an Internet service outage. If your bandwidth is exceeding the allotted amount, your ISP may throttle or shut down your connection. Many of these things are entirely out of your control.
All of these points are mitigated by using a hosting service which uses a professional datacenter to house its servers. They will have multiple power and Internet providers, generators, cooling, security, fire suppression systems, offsite backups. Some even have redundancy to other locations. It's more than you can possibly provide in-house, if you're the average small business or individual.
Let's take a few looks at the costs of self-hosting your website:
Continue reading %Why Self-Hosting Your Website Is a Bad Idea%
Setting up LogRocket is easy, and only requires adding a few lines of code to your app:
npm i --save logrocket.
import LogRocket from 'logrocket';
// Initialize LogRocket with your app ID
LogRocket.init(<your_application_id>);
import { applyMiddleware, createStore } from 'redux';
const store = createStore(
reducer, // your app reducer
applyMiddleware(middlewares, LogRocket.reduxMiddleware()),
);
That’s it for the basic setup- this is all you need to get started with LogRocket!
LogRocket also has plugins for alternate Flux implementations like ngrx and vuex, which you can read about here.
Replaying a session in LogRocket is like seeing it happen in your own browser. You can inspect Redux actions with the full action payload as well as the previous and next states.
LogRocket captures both network requests and responses and lets you dig in to specific requests and see the headers and body. The waterfall chart shows timings, making it easy to see which requests were slow, or if a potential race condition occurred.
Sometimes Redux logs alone aren’t enough to understand a bug, especially when dealing with user-reported issues. LogRocket’s video replay helps here by letting you see exactly what a user saw in your app.
Since this video is actually a reconstruction of the DOM (and not a real video) you can inspect HTML/CSS to understand visual bugs, or play at 2x speed to gain a quick understanding of what a user did in the app when handling support issues.
Being able to replay user sessions and see Redux logs is helpful across the development workflow.
Continue reading %Redux Logging in Production with LogRocket%
