i1820 / backend.php Goto Github PK

Corrects packages informations

Users can define perimeter for their project as a polygon using the geojson and store them. This perimeter will be shown on the project management page and their things will be there too.

loraserver.io thing's names must not have any space so we cannot just pass the user entered name into loraserver.io

Send activation links to users with the notification system and generate links as singed URL. This article may help a lot about this.

Delete project and stop its container in pm service

Adds following parameters:

• AppSKey
• NetSKey
• DeviceAddr

Provide the maximum size in file uploads

Create a specific Dockerfile for using in production. I think this link could help us in this dark and scary way.

Return related error when the given thing or project is not available instead of crashing by 500.

There is no point in building an application for each project in loraserver.io.
This causes a heavy load on the backend and providing nothing.

Use queue and jobs to handle the time-consuming works like sending an email

There is a great performance degradation when the ThingController loop over all collected data so this phase must remove.

There is no usefulness in payment portals so let's drop them

LoRa Authentication sometimes fails and returns token expires error.

Add database migration for collection indexes. This could help.

Remove thing from its project then delete it. it is supported in the tm service.

Provide information about the thing last seen and more in thing show API and do not return them in thing listing to improve performance.

Use Notification to send emails for users. The current handmade method has lots of issues.