Architecture :-

JWT_AUTH https://www.golang.company/blog/jwt-authentication-in-golang-using-gin-web-framework

Queue The the user specific Que I am sending the message that the device recieves and shows the display. There are few global queues that has to be there for certain global feature. Discover Websocket :- Whenever this socket sends a message it contains two info - { Screen_Code, User_id }

So That now the screens becomes aware and starts listening to the user specific queue.

API

1. Create User - Returns User ID
2. Login User and get JWT Token
3. CRUD Images and Playlist

[OPTIONAL] In My domain ( digitalsignage.com/api/v1/configs ) will return the IP of the rabbit MQ and other server specific config option

Token Based Authentication (JWT Auth) is mandatory for communication

User Creation :- Whenever a user is created,

1. a new vhost ( multitenancy in rabbitmq ) will be ceated and
2. a new playlist collection of that specific user will be created
3. a new bucket in object store will be created specific to the user

Image Store :- Image will be stored in an Object Store ( minio or AWS S3) and the public link of the image will be used throughout the application

Block Type in Screen :- lets say the whole screen is identified as block B0, in a split screen scenario one screen is identified as B1 and the other as B2 for three splits it can be B1 and B2TOP and B2BOTTOM

User to Device Mapping :- Each client can have multiple devices connected. Each device will have a unique ID and each device can show different things

DataBases :- We need 3 tables

1. Content [DONE] It Stores the content. That is user can upload Images/Videos etc { type:-Image/Video/GIF Link :- Link to image/Video/GIF }

2. Contentlist [DONE] It stores the playlist created by the user. It includes the time and respective content. So the format is like { name :- Name_of_playlist images :- [ { type :- Image/Video/GIF image:- Content_id, display_time :- 10 sec }, { type :- Image/Video/GIF image:- Content_id, display_time :- 20 sec }, ...] }

3. Screen [Done] It store all the screen information. That is Screen Name, Screen Dimensions, Screen Locations, Is the Screen Active or not. { Name:- Name of Screen, Dimension :- Dimension of Screen Location :- Location of Screen display_block :- [ { block :- B0 # Block B0 means whole screen playlist_id :- id of playlist }, { block :- B1 # Block B0 means whole screen playlist_id :- id of playlist } ] }

4. Screen_to_user_mapping This code must be based on timestamp, so that its always unique and monotonic The screen shows a code. When the users adds a screen and gives the code, That particular screen Fetches the UserID from the database and get the name of the queue it should listen to

5. Messages [Done] The JSON Playload mentioned below will be stores here. It store the complete message that needs to be sent to the user. If the user clicks on update screen, then the screen ID is sent. From there we get the mapped collectionlistID and Collection ID and thus we create the message that needs to sent to the device. If the user clicks on update all. Then this function is called in a loop

6. Blocks Multi Screen name with varying dimensions.

Screen_Block_Type - It Stores block name ( B0,B1 etc ) and the aspect ratio of each block type . Users - To store user information ( along with a unique user ID) Images - A Database to store Image Metadata ( User Id, Image link, upload date and so on) Playlists :- A collection of collection ( one collection for each user )

• Each Collection stores Single Image or Image playlist that needs to be displayed for that particular User

Data Format to be stored in Messages NoSQL database :- For Storing Single Image ( Only one image will be displayed on the screen) { id :- Unique_ID device_id :- device_id (screen_id) display_block :- {[ block :- B0 # Block B0 means whole screen images :- [ { type :- Image/Video/GIF image:- Image_link, display_time :- -1 } ] ]} } For Storing Multiple Image ( TO store playlist of multiple images or multiple static image to be shown in differnt grid block on the screen or playlist to be shown on multiple grid blocks on the screen) This is for playlist to be shown on the whole screen

{ id :- unique_Id device_id :- device_id display_block :- {[ block :- B0 # Block B0 means whole screen images :- [ { type :- Image/Video/GIF image:- Image_link, display_time :- 10 sec }, { type :- Image/Video/GIF image:- Image_link, display_time :- 20 sec }, ... ] ]} }

This is for if the screen is sub divided into multiple blocks and each block will have a different image or playlist of images ( split_screen -> whole screen split into two halfs) This means B1 will have a playlist and B2 will have a static image { id :- unique_Id device_id :- device_id display_block :- { [ block :- B1, images :- [ { type :- Image/Video/GIF image:- Image_link, display_time :- 10 sec }, { type :- Image/Video/GIF image:- Image_link, display_time :- 20 sec }, ... ] ], [ block :- B2, images :- [ { type :- Image/Video/GIF image:- Image_link, display_time :- -1 } ] ] } }

To Deploy

• delete db and minio folder
• adjust the env file
• docker compose build
• docker stack rm dsignage
• docker compose up -d
• check all services available
• docker compose down
• docker stack deploy -c compose.yaml dsignage [ This doesn't take the .env values to compose.yaml] so to address this
• sudo apt install docker-config
• sudo su
• docker stack deploy -c <(docker-compose config) dsignage
• get the object store access key and update the env file
• docker compose build -t app . docker stack deploy -c <(docker-compose config) dsignage

while deploying if any issue with user credential is found delete minio/db folder and start again