Please ignore this post, it's all computer stuff.
I've been putting a lot of time into the license-generation web site. Finally got docker working on the backend. I'm really interested in this technology, as it provides what's effectively a lightweight, deployable VM for each for your micro-applications. You can also compose them into a single flow, using docker-compose, and I have the middle and backend layers already composed.
Also, I got the many-to-many relationship to work strictly through object modeling with JPA in Spring-boot. The key trick there was to pass the entities as DTOs to the front end. This is something I wasn't even thinking about until I ran into a recursion issue from the framework having to do with each two objects containing sets of referencing each other. Then it was like, well, yeah, I've known you should use DTOs since about 2001, but I was working off an example. It just makes sense.
By the time the weekends out, I need to be generating actual licenses, which is after all the whole point of the system. Once I create a single license with that, I can say it's a production system.
On the list for the weekend
1 - complete the DTO change for edits and deletes.
2 - Incorporate the license generation
3 - Understand if the data is part of the container or local system
4 - Understand how to change 3 if desired
5 - Add the front end to the Docker compose
So I have a couple of new buzzwords I can add to my resume should it come to that, i.e. Docker, Docker-compose and React. I've added some credible unit testing and beefed up my Spring Boot and AWS chops as well. The other things I want to potentially add are API testing and Jenkins, which is automatic deployment. But that's a stretch goal.
1 and 2 are the key, though. 1 is effectively a bug at this point, and 2 is where I get to say it's in production.