Here is the November report.
Improved tests, change management, puzzles on tests launched by github.
We will detail all this, and other things, in the rest of the report.
Several times a week, I continue to stream live coding from the project on my Twitch channel.
It’s always a pleasure to stream code development. This month it was quite abstract because centered on the backend.
In December, most of the work will be on the frontend, and especially during the Christmas holidays, so it will be more visual ^_^
Don’t hesitate to drop by to say hello!
The FusionSuite project will blow out its first candle on January 12th.
I talked about it in the previous report, but I confirm the information:
Our partner DCS EASYWARE has provided us with 5 servers to begin performance testing and possible configurations, namely:
For the last 2 points, it will be easy to set up once in production at home, because the backend has been designed and architected for a normal mode (1 server), but also for these modes, useful for larger environments.
I will tell you about it in a next report of the month ;)
A lot of time has been spent on improving the tests:
This represents tens of thousands of modified lines, but we have rather clean tests (2400 tests).
Lots of hours wasted (about 20 ;/ ) in solving github actions.
Github actions are the tests run when you commit to the repository to check that you haven’t broken anything.
In November, a new system image was released by Github (Ubuntu 22.04).
We used to run php-fpm tests in the
home folder and it is now protected in this new version.
After many tests, in the end the only solution is to move the backend files to
/var/www/ so that php-fpm can access the files.
In November, PHP 7.4 passed EOL.
This version has been removed from the backend, so PHP 8.0 and 8.1 are recommended (required actually).
Change management has been implemented, this is the history of changes. When you change the name of an item, its property…
These changes are only accessible by retrieving an item with its id.
When retrieving multiple items, the changes will not be in the data.
The historical data is:
After several days of reflection, during the final deletion, it was decided to put in old_value the list of all the fields of the item. This will allow an admin to be able to find the information that was there before deletion. I’ve had this several times, and it’s really helpful.
I don’t know yet if there will be an admin page specifically for this or if it will remain manual in the database.
Eloqent has been upgraded to version 9.x, the tests all pass so no side effects detected.
Efforts were made in November on the backend to stabilize and add the changes, so very few changes on the frontend.
Tickets have been coded quite a bit over the past few months.
I realize that the code is quite large, so it will be split into several parts, namely:
1/ setting up the conversation part in a specific component, because it is also used for the history (types, computers, etc.) 2/ property management code (+ history) 3/ type management code (+ history) 4/ code for importing templates (tickets…) 5/ ticket code
The project is going well, we will pass a stage in December by advancing on the frontend following the stabilization and management of changes in the backend.
David Durieux - FusionSuite project leader