16 lines
1.1 KiB
HTML
16 lines
1.1 KiB
HTML
---
|
|
layout: post
|
|
title: Linspector Rewrite
|
|
metasub: news
|
|
---
|
|
|
|
<p>I am working on a Linspector rewrite because of:</p>
|
|
|
|
<ul>
|
|
<li>Big design fails in the configuration parser.</li>
|
|
<li>The new APScheduler works quite different and job scheduling needs to be rewritten anyway.</li>
|
|
<li>I have designed a completely new shell interface to Linspector which is not compatible with the actual code base.</li>
|
|
<li>I want to change the license from AGPL to some BSD or MIT style license and since some code was not written by myself I do not want to replace parts so a rewrite is the best solution.</li>
|
|
</ul>
|
|
|
|
<p>Keep in mind, that it is possible to create a fully working monitoring solution with the current code base but with some limitations. That is why I do not update the current code anymore. A lot of features are missinf but could easily be implemented. For me this makes no sense because the next generation of Linspector could not adopt code because a new design. The interface to services and tasks will not change in this rewrite so these parts could be reused.</p>
|