Even though we’re all under house arrest, work never stops!

However, because of all this excitement, I’ve had to switch about on machines and development environments a lot recently.

Previously, I’ve used my Known vagrant build to do development, but that started to prove a little bit heavy on a number of setups I’ve been using. So, since I’ve been playing with docker more recently, I thought it’d be nice to have a development container folks could use to quickly get up and running.

I’ve created a docker image that you can use in order to set up a quick development environment for your Known, and is installable via composer.

Installation

  • Download and install docker
  • Add this docker image to known using composer composer require mapkyca/mapkyca-known-docker --dev

This will create a docker environment in /vendor/mapkyca/mapkyca-known-docker/

Usage

  • cd /vendor/mapkyca/mapkyca-known-docker/
  • docker-compose up
  • Point your browser at localhost:8088 and install in the usual way

Data storage

Files you upload will be stored in your Known install’s “Uploads” directory.

Your database will be stored in /vendor/mapkyca/mapkyca-known-docker/db/run/.

IMPORTANT

This is designed to be used for temporary development, not production. I make no promises as to what happens to the database directory when doing composer updates.

If you care, back this up regularly!

» Visit the project on Github...

Another quick one before I head out for my government mandated single bit of exercise outside of my cell.

By popular demand, I’ve converted the Known sitemap.xml generator plugin I wrote some time ago to be installable via composer.

This means you no longer need to faff around with directories, and instead can install it simply with the following command:

composer require mapkyca/known-sitemap

Hopefully this will make it simpler for you!

» Visit the project on Github...

A heads up to those who are following Known GitHub HEAD!

I’ve just merged a change to Known core that makes a significant change to Known’s *sql core (mysql and Postgres). This change splits the metadata table into one metadata table per collection.

This simplifies the data model, which makes certain stuff easier going forward (import/export, GraphQL APIs etc). It also means we can leverage the DBMS in order to maintain data integrity.

This is a significant change, so it goes without saying that you need to BACK UP YOUR DATABASE BEFORE UPGRADING!