osiloke

Secured HLS setup with Nginx as media server

This example is part of this article.

This is an example for an HLS delivery with basic security. Nginx compiled with nginx-rtmp-module & secure-link is used as media server. Features:

• Domain filtering
• Referrer filtering
• Embed buster

osiloke

1. Make it look like the icon the user taps grows to fill the entire screen making for a seamless transition.
2. Keep it simple. A splash screen should only show for a few milliseconds. It shouldn’t have a lot of information on it — it is, after all, a dreaded loading screen.
3. With all of this in mind we’ll start with a a square image at three sizes (@1x = 200px, @2x = 400px, @3x = 600px).

Preparing the App
If you’ve tried to set up a splash screen in React Native then you may have experience a white screen flash before your content loads. If your app has a white background this is often not very noticable, but it’s still a pain. Today we’re going to make it very noticable if we have any flashes of white. To do that we’ll set a dark background color in our app.

Replace App.js with

import React, { Component } from 'react';

osiloke

smartctl 5.43 2016-09-28 r4347 [x86_64-linux-2.6.32-042stab076.5] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST1000DM003-1CH162
Serial Number:    S1D6PXSW
LU WWN Device Id: 5 000c50 05b663c77
Firmware Version: CC44
User Capacity:    1,000,204,886,016 bytes [1.00 TB]

osiloke

package main

import (
	"crypto/sha512"
	"encoding/base64"
	"fmt"
	"math/rand"
	"time"
)

osiloke

Zimbra Letsencrypt SSL Renew

Zimbra Version: Release 8.6.0_GA_1153.RHEL7_64_20141215151110 RHEL7_64 FOSS edition

Based on Zimbra Article KB 22434 : https://wiki.zimbra.com/wiki/Installing_a_LetsEncrypt_SSL_Certificate

Let's Begin

Log on Zimbra user then stop proxy and mail box service for renew proccess.

su zimbra

osiloke

https://silentadmin.gsans.com/everything-else/moving-zimbra-8-6-to-zimbra-8-7-1-on-a-new-server/
Moving Zimbra 8.6 to Zimbra 8.7.1 on a new server

Disclaimer: I have the NETWORK/PRO version but chose not to use the backups. This method should work with both the free and paid version as a result. I have used a variation of this for every update since version version 7. We perform offsite backups and use tar to handle the sparse 80GB ldap file.  This can run hot without the need to stop zimbra for most cases. The plan is to run this often and just before final cut-over do your shutdown as an extra precaution.  You should be able to minimize your disruption to the production server. If you are just testing out the update process, you may never have to shutdown the production. I don’t and haven’t had any ldap issues testing while learning what it going to take to upgrade zimbra on my testing machines. You can test the new server with these hot images and even perform an upgrade test with this method.  As the bac

osiloke

Migrating email accounts from a cPanel hosting environment to Mail-in-a-Box

Part 1: Pregame

1. Send a mass email to all of your account holders, letting them know that you will be migrating their email accounts to a new server. Send them the instructions from MiaB control panel for connecting to your MiaB server from their mobile/Outlook/Gmail/etc, if applicable. Also, send them a link to the new webmail address. Be sure to give adequate advanced notice (several days, if possible). Advise them to not change their passwords during this time (their passwords will be preserved during migration).
2. Create a new "test" email account in the MiaB control panel for your domain. This will let MiaB set up the DNS records needed for the domain.

Part 2: Copy credentials

Copy the email account credentials from your cPanel host to MiaB:

osiloke

03-20 23:33:28.768 7141-8096/com.dostow.apps.internal D/LeakCanary: In com.dostow.apps.internal:0.0.1:1.
03-20 23:33:28.768 7141-8096/com.dostow.apps.internal D/LeakCanary: * com.dostow.apps.ui.college.CollegeActivity has leaked:
03-20 23:33:28.768 7141-8096/com.dostow.apps.internal D/LeakCanary: * GC ROOT android.accounts.AccountManager$BaseFutureTask$Response.this$1
03-20 23:33:28.768 7141-8096/com.dostow.apps.internal D/LeakCanary: * references android.accounts.AccountManager$3.mCallback (anonymous class extends android.accounts.AccountManager$Future2Task)
03-20 23:33:28.768 7141-8096/com.dostow.apps.internal D/LeakCanary: * references android.accounts.AccountManager$GetAuthTokenByTypeAndFeaturesTask$1.this$1 (anonymous class implements android.accounts.AccountManagerCallback)
03-20 23:33:28.769 7141-8096/com.dostow.apps.internal D/LeakCanary: * references android.accounts.AccountManager$GetAuthTokenByTypeAndFeaturesTask.mActivity
03-20 23:33:28.769 7141-8096/com.dostow.apps.internal D/LeakCanary: * leaks 

osiloke

<android.support.design.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent">
    <android.support.v7.widget.RecyclerView
        android:id="@android:id/list"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        style="@style/myRecyclerViewStyle"/>
    <me.henrytao.smoothappbarlayout.SmoothAppBarLayout

osiloke

<android.support.design.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent">
    <android.support.v7.widget.RecyclerView
        android:id="@android:id/list"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        app:layout_behavior="@string/appbar_scrolling_view_behavior"
        style="@style/myRecyclerViewStyle"/>