InfyChat Third Party Setup

Pusher Configuration

Go to pusher website and do sign up or if you already have an account then do a login.

After login, you will be redirected to the following screen.

Click on the “Create new app” button. After clicking this button you get below screen.

Enter the name of your app. Select a cluster of your choice. Select “JS” from front-end tech and “Laravel” from back-end tech and click “create my app” button. As shown in the below image.

After creating an app yow will redirect to the below screen. After that click on the “App settings” menu as pointed in below screen.

After clicking on “App Settings” you will redirect to the below screen. From there select “Enable client events” checkbox and click on the “Update” button.

Now click on the “App Keys” menu and you will get the following screen.

Copy the values and add those values in your .env file.

PUSHER_APP_ID - Your pusher app id PUSHER_APP_KEY - Your pusher app key PUSHER_APP_SECRET - Your pusher app secret PUSHER_APP_CLUSTER - Your pusher app cluster

Laravel Echo Server Configuration

Laravel Echo also works with Laravel Echo Server with Socket.io implementation. We have created a very good video that demonstrates step by step to use Laravel Echo Server into InfyChat. Check the video below.

One Signal Web Notifications

OneSignal provides a very easy way to set up push notifications.

Create Account

Go to the OneSignal website. Create an Account if you don't have and login.

Create Application

After login, you will able to see below screen, click on "Add Application"

Specify the name of your application and click the "Create" button

Select Platforms

After creating your app, it will redirect you to the dashboard and ask for "Edit Your App"

Select Web as like below screenshot and click the "Next" button

Choose Integration

Select Typical site in step 1 as below,

Site Setup

Give your Site Name, Site Domain, and add your site icon as below screenshot.

Permission Prompt Setup

This step is optional. If you want to set up a different prompt instead of the default, you can configure it here.

Permission Prompt Editor

This step is also optional. Modify the prompt type if you want to.

Welcome Notification

You can optionally create welcome notification which will be displayed when the user successfully subscribed to push notifications.

Save Settings

In the end, click the "Save" button.

Update .env

Once you save application configuration, it will provide you the code as per the following.

You need to copy application id from here and set it up in your .env file in ONE_SIGNAL_APP_ID variable.

After that, click on "Accounts and API Keys" in the top right corner.

You should be able to find your API key from REST API Keys section, copy it and replace into .env variable ONE_SIGNAL_API_KEY.

That's it. We are ready to go.

Google Social Authentication

To Set up Google Authentication, you will need client secret, client id, and redirect URL from Google.

You can find steps here to set up google auth.

You can watch video here.

NOTE: DO not forget that Authorized Redirect URI should be e.g YOUR_DOMAIN/login/google/callback, you just need to replace YOUR_DOMAIN by your domain name.

Once you have a Client ID, Client Secret and Redirect URI, replace it into appropriate .env variable.

GOOGLE_CLIENT_ID= GOOGLE_CLIENT_SECRET= GOOGLE_REDIRECT="YOUR_APP_URL/login/google/callback"

Facebook Social Authentication

To Set up Facebook Authentication, you will need app secret, app id, and redirect URL from Facebook.

You can find steps here to set up Facebook auth.

NOTE: DO not forget that Authorized Redirect URI should be e.g YOUR_DOMAIN/login/facebook/callback, you just need to replace YOUR_DOMAIN by your domain name.

Now you have App ID, App Secret and Redirect URI so replace its value into appropriate .env variable.

FACEBOOK_APP_ID= FACEBOOK_APP_SECRET= FACEBOOK_REDIRECT="YOUR_APP_URL/login/facebook/callback"

AWS S3 for Media Uploads

If you want to store your files on Amazon S3 bucket then you have to use the following .env variables. You need to change FILESYSTEM_DRIVER variable in your .env file to s3 when you are using AWS file storage. Also, configure the following variables with appropriate values into your .env file.

FILESYSTEM_DRIVER=s3 AWS_ACCESS_KEY_ID= AWS_SECRET_ACCESS_KEY= AWS_DEFAULT_REGION=us-east-1 AWS_BUCKET= AWS_ENDPOINT= AWS_URL=

Zoom Meeting Integration

Update Zoom Meeting Configuration:

• Click Here to configure your application

  ZOOM_API_URL="https://api.zoom.us/v2/" ZOOM_API_KEY="" ZOOM_API_SECRET="" ZOOM_REDIRECT_URL=${APP_URL}/zoom/callback"