SQL Builder that is currently in use has gone into maintenance mode. While this is not a problem given Go's commitment to backwards compatibility. Eventually the database support may go stale and it would probably be good to migrate to Bob which offers better documentation and a similar feature set.

In combination to this migration, we could move the database from Postgres onto sqlite that Bob supports. As the site database requirements are simple using only a single table, the transition should be okay.

Using SQLite via rqlite or another package would allow for the following.

• 1. Remove the need for containerization with Docker.
• 2. Remove the complexity of maintaining Postgres including web UIs.
• 3. Allow the database to be frozen, distributed and even embedded into the single binary application, meaning less configuration for non-server user.
• 4. Would allow the preservation of the database as it is stored as a single file.
• 5. Possibility of creating a secondary distribution that includes all database functionality, as well as all image assets such as thumbnails to be embedded and served from the single binary, again allowing for better preservation of the web application.