updated
- create a centralized server
- integrated Auth Api in it
- created a gui for login change pass in the trayicon
[!IMPORTANT] Create centralized server with integrated Auth API and GUI for login and password change in tray icon.
- Centralized Server:
- Created a centralized server to manage application functionalities.
- Auth API Integration:
- Integrated authentication API into the centralized server for user management.
- GUI Enhancements:
- Added GUI for login and password change in the tray icon.
- Submodule Updates:
- Updated submodules
aw-client,aw-core,aw-notify,aw-qt, andaw-serverto latest commits.This description was created by
for f88b8f26a42eaf4bc6b5f9b69e8a5b56e36883b6. It will automatically update as commits are pushed.
why i dont have acess ?
What are you trying to do here?
i have created a centralized server separately and integrate in client then give options in the tray icon like login, rejister etc when ever the user login it will push data to the centralized server and when logout it will stop pushing
Interesting! I can't see the changes you've made in the submodules because you have not pushed them.
the centralized server is not pushed but i just pushed the activity watch with integration i will deploy the Centralized server on aws, see the changes in trayicon.
- when user login scheduler start and start hitting the submit endpoint of centralized server
- and when logout schedular stops
the centralized server is not pushed
Please note the following license terms stipulated by the MPL2.0 license:
You must publish changes you make to the source code (if you intend to distribute it) https://docs.activitywatch.net/en/latest/forking.html
This applies to changes in the ActivityWatch source files, not extra files you've written. But if you don't intend to distribute it, you have no such obligation.
i just pushed the activity watch with integration i will deploy the Centralized server on aws, see the changes in trayicon
This PR makes no sense if you don't also push the modules. Not saying we would merge it, but would be interesting to read.
Thank you so much for your guide i will make changes in my fork as early as possible
@JM-JamalMustafa Does that mean, that you are storing the data of activity watch inside of AWS S3 instead of locally? Or is it just about the login process and each user has access to different data sources (which are local)? Thx
I was thinking of building something similar, so this would be very helpful!