Mobile App Setup for Your Environment

The mobile app can be used for free for demo and testing purposes. However, for production use, licensing is required.

Prerequisites for Enabling the Mobile App

To set up the mobile app for your environment, ensure the following two conditions are met:

1. Enable the Mobile App in Configuration
   Navigate to your configuration settings and enable the mobile app: Your TAS Domain Configuration
2. Configure Firebase for Push Notifications
   To send push notifications, Firebase must be properly configured. You can request this setup as follows:
   • Internal Users (DEVOPS or Consultants): Request configuration directly.
   • Partners: If you haven't received your Firebase credentials yet, submit a request to partners@teamassistant.app.

Downloading & Activating the App

Once the app is set up, users can download it from the store and follow the activation instructions in this video: Watch Activation Guide

Adding Firebase to Configuration (For Partners)

After receiving Firebase configuration details, add the following configuration block to the local.js file:

firebase: {
    auth: {
        projectId: 'tas-partner-instance',
        privateKey: '-----BEGIN PRIVATE KEY-----\nMIIEvQIBADAN...\n-----END PRIVATE KEY-----',
        clientEmail: 'firebase-adminsdk-dmrfh@tas-partner-instance.iam.gserviceaccount.com',
        androidAppId: '1:698634540901:android:f613debeab37450103b38c',
        androidApiKey: 'AzaSyBI9vyi8f2BcldDe8p2L_11jrWSnPzTi0XU',
        iosAppId: '1:698634540901:ios:f8b73dd028a99d7403b38c',
        iosApiKey: 'AzaSyB9c7QIAhvjP4CoctuzXX1fBc5V-dujdobk',
        senderId: '698634540901',
    },
},

This configuration block should be placed at the same level as other settings within local.js, for example:

module.exports = {
    port: process.env.PORT || 8001,
    // Other configurations...

    firebase: {
        auth: {
            // Firebase configuration...
        },
    },
    
    redis: {
        host: "redis",
        port: 6379,
    },

    // Additional configurations...
};

Security Recommendations

Sensitive data such as privateKey and apiKey should not be stored directly in configuration files. For better security, use Docker Swarm Secrets or other secure storage methods. More details can be found in the installation manual.