I made the final README. I finished the frontend devlog meaning that everything is done and I can finally ship Devlogs+!!!

I created the README for the backend repo. It includes details on the file structure, what is was made in, and how to use docker to test it.

I created the README for the backend api docs. The README tells you about the structure of the requests and the organization of the request files.

Since last devlog I have been working on getting ready for shipping. I made GitHub actions for the backend and frontend to generate docker packages, and a GitHub action to publish the docker compose file. I also made the README for the main repo, though I still need the readmes for the backend repo, frontend repo, and backend api docs repo.

I decided to move the http requests from postman to .http files. I made this change because even though postmans ui is good, it is starting to get filled with ai stuff I don’t need. Plus, for those who dont want to use postman, it is way easier to read the requests.

I fully added docker support for both the backend and frontend. Both repos have dockerfiles and the main repo has a docker-compose file and env files for both in the parent repo. Since i am going to use this from now it helps me replicate what is on the server side.

When creating a devlog it now automatically adds time spent since the last devlog/project creation. It shows the time spent as soon as you select a project in the devlog creation menu. Also, in the project page it shows time spent.

There is now a full system (on the backend) to add time to a devlog. The wakatime part was way easier to implement as you could just use oauth to get time spent, but hackatime your had to get both the user id and api key just to get the time spent. That being said, there are also new routes to get the time since the last devlog (or since 1900 if there is not one).

I have added full wakatime/hackatime support to the website. Once your Hackatime/Wakatime accounts are connected you can connect time project to Devlog+ projects. Once those are connected you can view all time logged for projects. This was one of the hardest parts to setup as when I updated what the api expected on the backend, i kept forgetting to update what the frontend was sending.

I have made it so you can link your hackatime and wakatime account. There are buttons on your profile that redirect to oauth pages for their respective platforms. Once connected the button will change to disconnect hackatime/wakatime

I have unified the time tracking and added the ability to add time spent to both projects and devlogs. By unifying the time spent It is way easier to get time spent and other factors. I will soon implement all of the stuff I have worked on to the frontend.

I have added support for wakatime. Just like the hackatime integration it only has the api routes right now.

I have added hackatime support (kinda) I have only added it to the backend so if you somehow call the backend (i have CORS) you can link your hackatime account and view your projects

I have updated the nav bar to be more stylish. I found that react router has a NavLink component which is designed for navigation panels.

I have made it easier to add a collaborator for a project. Instead of entering the user id, you now enter the users email. This is in both the add and remove collaborator forms.

I have made some changes to the collaborator pages. Instead of user ids, it now displays their display name. I also added back buttons to most form.

I have added a small QoL update to the unpublished devlogs page, before the devlogs publish and edit button were not part of the devlog card and you had a hard time knowing what devlog it was for, now the devlog info, publish and edit button are all grouped together.

I added a small improvement to the create a devlog page. Instead of inputting a devlog id, you can now click on a dropdown that shows all the projects you own/collaborate on. Even though this is quite small, I think it will be a big QoL update.

You can now view the projects a user has made! Below the users info on their page there is a section with all their projects. The backend is essentially just the get projects route but instead of /projects it is /projects/user/user_id