Journal

First version that actually “feels” complete, obviously is far from it but no more incomplete features or weird bugs.

The endpoint view was completely improved with autosave for all the fields in the responses, added headers and code hightlighting to the content box.

Also added dark mode.

Here is the [ repo ].

Yesterday I tagged and release mochapi v0.4.0 I think this is the first verision that feels complete, no weird bugs for the moment and everything feels smooth.

Today I just deployed it to use it at my job and then another case that is not currently solvable showed up. So I will spend some times the next days working on that.

Overall the project is going good.

Not sure how many times I’m leaving and returning to this project, truth is I don’t know why I can’t commit to finish some stuff.

This time is to polish a feature that I’m needing for work, maybe that is the push I need. A deadline, even tho this is not really a deadline, more of, I really need this feature to use it on my job for real, so the sooner the better.

And as always when I return there is a lot of stuff that I forgot but also I learn better how some stuff works. I hope to finish my project I planned for this year, including mochapi being in a good form.

This release marks the first attempt to actually use the tool in a real environment.

Added multiple responses per endpoint as well as conditions for them. Dropped the custom path handling in favor of URI standards from RFC.

Updated and fixed installer, as well as adding instructions to install the application image only with an existing MySql server instance.

Here is the [ repo ].

Haven’t write anything lately, been having trouble finding time to focus on my projects. I need to find the time, organize my time better, so I have more chunks of time to put some deep work.

Today I am finishing the next minor version for mochapi. Officially making the tool usable for the first use case. Right now we have to test and fix some of the appearance.

Then again this weekend I found some time to work on Mochapi, this time I added the options to add and delete the responses and fixed some stuff that was not working.

Next stuff is going to be fun I think, that is implementing the expression model as conditions for the different responses. The challenge will be to handle all the different options for the expression values. That’s why I’m going to start with a simple use case using just the path variables.

This week is supposed to be very productive in mochapi, I’m happy to report that today it was very productive, even if I would have like to do more, I think I did plenty today.

The reason I think today was productive was because yesterday I sit and think a lot about design decisions and wrote it down, so today I didn’t have to think twice before implementing some stuff.

I don’t remember if I did write this before, probably, but this week I will start working into mochapi, last week I did very little for my side projects. Just having other stuff in mind.

There is a holiday this week, so I will take advantage of the extra time to have some quality work time in mochapi.

Today I was looking at my starred repositories, and somehow one of the first ones I ever starred caught my eye. It was a ruby gem called Addressable, that is used to parse URIs and provides functionality to use URI templates.

This is basically what I need for mochapi, instead of my very rudimentary parser I’ve been using. Apart from that it uses RFC specifications, so I don’t have to reinvent the wheel and just use a stardard way of doing URI templates.

It was just testing so, I hope to start the implementation tomorrow.

Well yesterday was busy, I did work a little bit in my pihole installation. Basically fixing weird errors in Ubuntu.

Today I started fixing the latest mochapi installer, which I messed up. And also started to work on a github action to deploy this site automatically using FTP in my hosting platform.