<feed xmlns='http://www.w3.org/2005/Atom'>
<title>scrott/srvs, branch v0.3</title>
<subtitle>The Secure Centralized Robust Online Ticketing Tool</subtitle>
<link rel='alternate' type='text/html' href='http://normalmode.org/malf/scrott/'/>
<entry>
<title>Fix bug in database schema</title>
<updated>2018-10-27T21:09:09+00:00</updated>
<author>
<name>Malf Furious</name>
<email>m@lfurio.us</email>
</author>
<published>2018-10-27T21:09:09+00:00</published>
<link rel='alternate' type='text/html' href='http://normalmode.org/malf/scrott/commit/?id=8ee07502cc84bb878efaf637947d543689eb38bf'/>
<id>8ee07502cc84bb878efaf637947d543689eb38bf</id>
<content type='text'>
These text fields need a default of NULL aparently.

Signed-off-by: Malf Furious &lt;m@lfurio.us&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
These text fields need a default of NULL aparently.

Signed-off-by: Malf Furious &lt;m@lfurio.us&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>issue:  Redesign schema</title>
<updated>2018-10-22T01:29:26+00:00</updated>
<author>
<name>Malf Furious</name>
<email>m@lfurio.us</email>
</author>
<published>2018-10-22T01:18:21+00:00</published>
<link rel='alternate' type='text/html' href='http://normalmode.org/malf/scrott/commit/?id=479fa31398d18f105616de83b5b5108278b75c59'/>
<id>479fa31398d18f105616de83b5b5108278b75c59</id>
<content type='text'>
I found myself complicating the data model of this class of objects and
wanted to take a clean approach to its design.  The key differences are
as follows:

        * We now reference a message object for the issue's OP, as
        opposed to directly containing the message data

        This affords the OP _all_ of the standard features of a Scrott
        message, including separately tracked authorship data, file
        attachments.

        * Multiple assignees is implemented in the design

        Finally.

        * Seen flag is removed

        This can be implicitly tracked via all sub-object messages and
        the views meta-table.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I found myself complicating the data model of this class of objects and
wanted to take a clean approach to its design.  The key differences are
as follows:

        * We now reference a message object for the issue's OP, as
        opposed to directly containing the message data

        This affords the OP _all_ of the standard features of a Scrott
        message, including separately tracked authorship data, file
        attachments.

        * Multiple assignees is implemented in the design

        Finally.

        * Seen flag is removed

        This can be implicitly tracked via all sub-object messages and
        the views meta-table.
</pre>
</div>
</content>
</entry>
<entry>
<title>issue:  Add assigned timestamp</title>
<updated>2018-10-21T01:49:32+00:00</updated>
<author>
<name>Malf Furious</name>
<email>m@lfurio.us</email>
</author>
<published>2018-10-21T01:49:32+00:00</published>
<link rel='alternate' type='text/html' href='http://normalmode.org/malf/scrott/commit/?id=b690505b0e1e255e5081adcf49c724186bb831c2'/>
<id>b690505b0e1e255e5081adcf49c724186bb831c2</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>issue:  Add open/close data</title>
<updated>2018-10-21T01:43:46+00:00</updated>
<author>
<name>Malf Furious</name>
<email>m@lfurio.us</email>
</author>
<published>2018-10-21T01:43:46+00:00</published>
<link rel='alternate' type='text/html' href='http://normalmode.org/malf/scrott/commit/?id=b093b3affe3ac6878e2242bff310dc466687a825'/>
<id>b093b3affe3ac6878e2242bff310dc466687a825</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>issue:  Add author and authored fields</title>
<updated>2018-10-21T01:24:01+00:00</updated>
<author>
<name>Malf Furious</name>
<email>m@lfurio.us</email>
</author>
<published>2018-10-21T01:24:01+00:00</published>
<link rel='alternate' type='text/html' href='http://normalmode.org/malf/scrott/commit/?id=9df5344050ec0a2b8bec03c7a89fff9d7d41ce2f'/>
<id>9df5344050ec0a2b8bec03c7a89fff9d7d41ce2f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>mysql:  Move schema file into srvs/</title>
<updated>2018-09-20T23:05:56+00:00</updated>
<author>
<name>Malf Furious</name>
<email>m@lfurio.us</email>
</author>
<published>2018-09-20T23:05:56+00:00</published>
<link rel='alternate' type='text/html' href='http://normalmode.org/malf/scrott/commit/?id=b9bdf474f838d1435dc0cba1f6ffa9e1e26520b6'/>
<id>b9bdf474f838d1435dc0cba1f6ffa9e1e26520b6</id>
<content type='text'>
This places all (both) of the service configuration files together and
cleans up the top-level directory.  The file is renamed to 'mysql.sql'
to indicate the particular service it corresponds to.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This places all (both) of the service configuration files together and
cleans up the top-level directory.  The file is renamed to 'mysql.sql'
to indicate the particular service it corresponds to.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add sample nginx configuration</title>
<updated>2018-02-06T07:40:27+00:00</updated>
<author>
<name>Malf Furious</name>
<email>m@lfurio.us</email>
</author>
<published>2018-02-06T07:40:27+00:00</published>
<link rel='alternate' type='text/html' href='http://normalmode.org/malf/scrott/commit/?id=5b50f0490b6f177cfabc5646c1786d1140598507'/>
<id>5b50f0490b6f177cfabc5646c1786d1140598507</id>
<content type='text'>
I've recently been fighting my dev server to actually work with PHP.  It
seems like everytime I hop a system, or install nginx from scratch,
something in my config is broken.  So, I'm finally committing a
'working' (TM) baseline config to work off of when working with servers
in the future.  The idea is to add an Apache one at some point, too.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I've recently been fighting my dev server to actually work with PHP.  It
seems like everytime I hop a system, or install nginx from scratch,
something in my config is broken.  So, I'm finally committing a
'working' (TM) baseline config to work off of when working with servers
in the future.  The idea is to add an Apache one at some point, too.
</pre>
</div>
</content>
</entry>
</feed>
