<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.9.2">Jekyll</generator><link href="https://asks0luti0ns.github.io/Wastebug/feed.xml" rel="self" type="application/atom+xml" /><link href="https://asks0luti0ns.github.io/Wastebug/" rel="alternate" type="text/html" /><updated>2022-05-26T19:32:49+00:00</updated><id>https://asks0luti0ns.github.io/Wastebug/feed.xml</id><title type="html">Wastebug</title><subtitle>Simple web-based bug-tracking tool</subtitle><entry><title type="html">Still here (luckily)</title><link href="https://asks0luti0ns.github.io/Wastebug/github/update/2022/05/26/still-here.html" rel="alternate" type="text/html" title="Still here (luckily)" /><published>2022-05-26T19:24:06+00:00</published><updated>2022-05-26T19:24:06+00:00</updated><id>https://asks0luti0ns.github.io/Wastebug/github/update/2022/05/26/still-here</id><content type="html" xml:base="https://asks0luti0ns.github.io/Wastebug/github/update/2022/05/26/still-here.html">&lt;p&gt;I’m still here, luckily; both with and without a pun. Shortly after the last update, not more than a few days, I was not feeling well. Things deteriorated quite quickly and I tested positive for COVID19. Now, more than nine weeks later, I’m still recovering.&lt;/p&gt;

&lt;p&gt;Even while being very careful from early February 2020 up until now. I’ve been very careful indeed. The knowledge that I’ve never reacted well to illnesses is a good motivator. As soon as the first vaccinations became available, I realized how dangerous the world could become. I predicted risky behavior under the vaccinated. Having had multiple adverse reactions to vaccinations before I could not take the risk to get vaccinated myself. And I was right and wrong. The risky behavior came true, both by the vaccinated and by people just having enough of all the COVID measures.&lt;/p&gt;

&lt;p&gt;I probably got infected with the Omicron strand at the supermarket. About a short week before I fell ill, a woman was coughing in the faces of people and over the groceries.&lt;/p&gt;

&lt;p&gt;I’m still exhausted and still in pain.. The upcoming week I’ve got an appointment at the hospital to have a hypopharyngeal echography taken. I’m very lucky. Both heatwise, but also having a great team supporting me.&lt;/p&gt;</content><author><name></name></author><category term="github" /><category term="update" /><summary type="html">I’m still here, luckily; both with and without a pun. Shortly after the last update, not more than a few days, I was not feeling well. Things deteriorated quite quickly and I tested positive for COVID19. Now, more than nine weeks later, I’m still recovering. Even while being very careful from early February 2020 up until now. I’ve been very careful indeed. The knowledge that I’ve never reacted well to illnesses is a good motivator. As soon as the first vaccinations became available, I realized how dangerous the world could become. I predicted risky behavior under the vaccinated. Having had multiple adverse reactions to vaccinations before I could not take the risk to get vaccinated myself. And I was right and wrong. The risky behavior came true, both by the vaccinated and by people just having enough of all the COVID measures. I probably got infected with the Omicron strand at the supermarket. About a short week before I fell ill, a woman was coughing in the faces of people and over the groceries. I’m still exhausted and still in pain.. The upcoming week I’ve got an appointment at the hospital to have a hypopharyngeal echography taken. I’m very lucky. Both heatwise, but also having a great team supporting me.</summary></entry><entry><title type="html">First real commits and PostgreSQL</title><link href="https://asks0luti0ns.github.io/Wastebug/github/code/update/2022/03/17/first-real-commits-and-postgresql.html" rel="alternate" type="text/html" title="First real commits and PostgreSQL" /><published>2022-03-17T16:45:06+00:00</published><updated>2022-03-17T16:45:06+00:00</updated><id>https://asks0luti0ns.github.io/Wastebug/github/code/update/2022/03/17/first-real-commits-and-postgresql</id><content type="html" xml:base="https://asks0luti0ns.github.io/Wastebug/github/code/update/2022/03/17/first-real-commits-and-postgresql.html">&lt;p&gt;First fruits of my labor from the last few weeks are here! In between all my other projects and administrative tasks, I’ve managed to get to a point that I can commit the first new code to GitHub. This is the result of about a dozen commits to our CVS server, running diffs, merging changes and reviewing the code.&lt;/p&gt;

&lt;p&gt;In the meanwhile I’ve been setting up a PostgreSQL test server. We’ve got multiple database servers, but they are all MariaDB 10.3 and 5.5. The last time I did something with PostgreSQL was about 15 years ago and I’ve never installed and configured one. I can say, the design is strange and out of the box it poses a huge security risk if a single server (or cluster as they call it) is used for multiple (web)applications. It’s good practice to use different credentials for different databases. This way data stored in for instance Wastebug cannot be exposed through a co-installed Magento install.&lt;/p&gt;

&lt;p&gt;PostgreSQL uses roles that per default are mapped to Unix user accounts (peer and ident authentication). This is great at the CLI as an administrator or developer. With MySQL and MariaDB each time you want to do something in the database you must supply a username and password. With PostgreSQL this is only done once, by logging in to the host machine. For traditional applications this is not a problem. You can run your calendar server under a different unix account than your network monitoring server. But with more modern applications, who are often web based, they run all side by side in different virtual hosts on a single Apache, LiteSpeed or NGINX instance. And thus all use the same unix account such as the Apache user and group.&lt;/p&gt;

&lt;p&gt;After some reading, testing, failing, retrying and setting up the local firewall, I’ve got a working PosteSQL server, sorry cluster. Depending on connecting through a Unix domain socket, the loopback interface or to the machines IP address, either peer, ident or md5 authentication is used. Enabling this server to be used for testing most real life scenarios.&lt;/p&gt;</content><author><name></name></author><category term="github" /><category term="code" /><category term="update" /><summary type="html">First fruits of my labor from the last few weeks are here! In between all my other projects and administrative tasks, I’ve managed to get to a point that I can commit the first new code to GitHub. This is the result of about a dozen commits to our CVS server, running diffs, merging changes and reviewing the code. In the meanwhile I’ve been setting up a PostgreSQL test server. We’ve got multiple database servers, but they are all MariaDB 10.3 and 5.5. The last time I did something with PostgreSQL was about 15 years ago and I’ve never installed and configured one. I can say, the design is strange and out of the box it poses a huge security risk if a single server (or cluster as they call it) is used for multiple (web)applications. It’s good practice to use different credentials for different databases. This way data stored in for instance Wastebug cannot be exposed through a co-installed Magento install. PostgreSQL uses roles that per default are mapped to Unix user accounts (peer and ident authentication). This is great at the CLI as an administrator or developer. With MySQL and MariaDB each time you want to do something in the database you must supply a username and password. With PostgreSQL this is only done once, by logging in to the host machine. For traditional applications this is not a problem. You can run your calendar server under a different unix account than your network monitoring server. But with more modern applications, who are often web based, they run all side by side in different virtual hosts on a single Apache, LiteSpeed or NGINX instance. And thus all use the same unix account such as the Apache user and group. After some reading, testing, failing, retrying and setting up the local firewall, I’ve got a working PosteSQL server, sorry cluster. Depending on connecting through a Unix domain socket, the loopback interface or to the machines IP address, either peer, ident or md5 authentication is used. Enabling this server to be used for testing most real life scenarios.</summary></entry><entry><title type="html">The hard work of unforking</title><link href="https://asks0luti0ns.github.io/Wastebug/github/code/update/2022/03/09/the-hard-work-of-unforking.html" rel="alternate" type="text/html" title="The hard work of unforking" /><published>2022-03-09T17:47:06+00:00</published><updated>2022-03-09T17:47:06+00:00</updated><id>https://asks0luti0ns.github.io/Wastebug/github/code/update/2022/03/09/the-hard-work-of-unforking</id><content type="html" xml:base="https://asks0luti0ns.github.io/Wastebug/github/code/update/2022/03/09/the-hard-work-of-unforking.html">&lt;p&gt;There were two reasons to revive Wastebug: 1) being in need of a good&lt;sup id=&quot;fnref:1&quot; role=&quot;doc-noteref&quot;&gt;&lt;a href=&quot;#fn:1&quot; class=&quot;footnote&quot; rel=&quot;footnote&quot;&gt;1&lt;/a&gt;&lt;/sup&gt; tool, 2) having used a good tool for many years, but having lost some of the code. So far I’ve augmented all the code and have a working version of Litterbug running on an internal server. I’ve ported over nearly 300 bugs, feature requests and tasks from a Libre Office Calc spreadsheet. Slowly I’m working out all the kinks, trying to avoid the temptation of working on full integration with our current ERP solution. And also avoiding the temptation of re-implementing previous features of which the code has been lost but are still in my head.&lt;/p&gt;

&lt;p&gt;I’m nearing a point that I can start the process of unforking all the changes back into Wastebug 0.9.1 and release 0.9.2, the first public release in 18 years!&lt;/p&gt;

&lt;div class=&quot;footnotes&quot; role=&quot;doc-endnotes&quot;&gt;
  &lt;ol&gt;
    &lt;li id=&quot;fn:1&quot; role=&quot;doc-endnote&quot;&gt;
      &lt;p&gt;A good tool as in a tool that:&lt;/p&gt;
      &lt;ul&gt;
        &lt;li&gt;tracks the things to do,&lt;/li&gt;
        &lt;li&gt;supports multiple users,&lt;/li&gt;
        &lt;li&gt;handles many cases for many projects,&lt;/li&gt;
        &lt;li&gt;does not force micromanagement to your workflow,&lt;/li&gt;
        &lt;li&gt;has a simple and quick to use (may have a steep learning curve) interface,&lt;/li&gt;
        &lt;li&gt;is easily modified and extended.&lt;/li&gt;
      &lt;/ul&gt;
      &lt;p&gt;&lt;a href=&quot;#fnref:1&quot; class=&quot;reversefootnote&quot; role=&quot;doc-backlink&quot;&gt;&amp;#8617;&lt;/a&gt;&lt;/p&gt;
    &lt;/li&gt;
  &lt;/ol&gt;
&lt;/div&gt;</content><author><name></name></author><category term="github" /><category term="code" /><category term="update" /><summary type="html">There were two reasons to revive Wastebug: 1) being in need of a good1 tool, 2) having used a good tool for many years, but having lost some of the code. So far I’ve augmented all the code and have a working version of Litterbug running on an internal server. I’ve ported over nearly 300 bugs, feature requests and tasks from a Libre Office Calc spreadsheet. Slowly I’m working out all the kinks, trying to avoid the temptation of working on full integration with our current ERP solution. And also avoiding the temptation of re-implementing previous features of which the code has been lost but are still in my head. I’m nearing a point that I can start the process of unforking all the changes back into Wastebug 0.9.1 and release 0.9.2, the first public release in 18 years! A good tool as in a tool that: tracks the things to do, supports multiple users, handles many cases for many projects, does not force micromanagement to your workflow, has a simple and quick to use (may have a steep learning curve) interface, is easily modified and extended. &amp;#8617;</summary></entry><entry><title type="html">Welcome to GitHub Pages!</title><link href="https://asks0luti0ns.github.io/Wastebug/github/documentation/update/2022/03/03/welcome-to-github-pages.html" rel="alternate" type="text/html" title="Welcome to GitHub Pages!" /><published>2022-03-03T19:23:06+00:00</published><updated>2022-03-03T19:23:06+00:00</updated><id>https://asks0luti0ns.github.io/Wastebug/github/documentation/update/2022/03/03/welcome-to-github-pages</id><content type="html" xml:base="https://asks0luti0ns.github.io/Wastebug/github/documentation/update/2022/03/03/welcome-to-github-pages.html">&lt;p&gt;I’ve been struggling for about a week, for what to do with the documentation for the Wastebug project. Should I just stick to a README.md and INSTALL.md? Go for a Wiki on GitHub? Setup a dedicated website? Or add a section to the &lt;a href=&quot;https://www.ask-solutions.org/&quot;&gt;ASK-Solutions website&lt;/a&gt;? I’ve decided upon GitHub Pages.&lt;/p&gt;

&lt;p&gt;The decision boils down to:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;GitHub is iffy about their wikis and search engines.&lt;/li&gt;
  &lt;li&gt;I generally dislike wiki’s.&lt;/li&gt;
  &lt;li&gt;Me wanting more experience with Jekyll.&lt;/li&gt;
  &lt;li&gt;I don’t regard Wastebug a project or product of &lt;a href=&quot;https://www.ask-solutions.org/&quot;&gt;ASK-Solutions&lt;/a&gt; as we’ve always been more of a user of the project.&lt;/li&gt;
&lt;/ul&gt;</content><author><name></name></author><category term="github" /><category term="documentation" /><category term="update" /><summary type="html">I’ve been struggling for about a week, for what to do with the documentation for the Wastebug project. Should I just stick to a README.md and INSTALL.md? Go for a Wiki on GitHub? Setup a dedicated website? Or add a section to the ASK-Solutions website? I’ve decided upon GitHub Pages. The decision boils down to: GitHub is iffy about their wikis and search engines. I generally dislike wiki’s. Me wanting more experience with Jekyll. I don’t regard Wastebug a project or product of ASK-Solutions as we’ve always been more of a user of the project.</summary></entry></feed>