{technology.description}{#if technology.extended_description}{technology.extended_description}{/if} +
+Project website: {technology.website}
+ {#if technology.repository}Source code repository: {technology.repository}
{/if} + {#if technology.wikipedia}Wikipedia entry: {technology.wikipedia}
{/if} +{pluraliser('Category', + 'Categories', technology.categories.length)}: {toOxfordCommaString(technology.categories)}
{/if} + {#if technology.analogues}Alternative to {toOxfordCommaString(technology.analogues)}
{/if} + {#if technology.license}License: {technology.license}
{/if} +Instances of {technology.name}:
+{instance.domain} hosted on '{instance.host}' by {instance.affiliation}". +
+This sites exists to provide an 'always-up-to-date', in-depth description of the +
+ This sites exists to provide an 'always-up-to-date', in-depth description of the libre software web services I (Dave Lane) have set up and maintain. + title="What do I mean by 'libre' software?">libre software + web services I (Dave Lane) have set up and maintain.
-These services are run primarily on commodity Linux Virtual Private Servers, aka 'hosts', which I also maintain. Some systems are also run on real physical hosts either in my home hosting facility or in commercial hosting facilities. These hosts are based in Aotearoa NZ, Singapore, the US, and in Germany. Almost all run an LTS (Long Term Support) version of Ubuntu Linux although a few hosts run Debian Linux.
-Almost all the hosts are configured in a particular way which allows multiple services to run harmoniously on the same host. I use a set of somewhere between one and twenty-one Docker containers (which I run via Docker Compose) for each service, to keep different services, each of which has different software dependencies, from interfering with one another. Each service is made available to the Internet via a 'reverse proxy' (for which I use Nginx) and user interactions with them are secured (encrypted) with Let's Encrypt SSL certificates (which renew automatically). +
+ These services are run primarily on commodity Linux Virtual Private Servers, aka 'hosts', + which I also maintain. Some systems are also run on real physical hosts either in my home + hosting facility or in commercial hosting facilities. These hosts are based in Aotearoa NZ, + Singapore, the US, and in Germany. Almost all run an LTS (Long Term Support) version of Ubuntu + Linux although a few hosts run Debian Linux. +
++ Almost all the hosts are configured in a particular way which allows multiple services to run harmoniously on the same host. I use a set of somewhere + between one and twenty-one Docker containers (which I run via Docker Compose) for each service, + to keep different services, each of which has different software dependencies, from interfering + with one another. Each service is made available to the Internet via a 'reverse proxy' (for which + I use Nginx) and user interactions with them are secured (encrypted) with Let's Encrypt SSL certificates (which renew automatically). +
++ To manage the servers and keep them up-to-date, I use SSH to establish secure encrypted + connections to them (via key-based authentication). I run updates of the hosts manually, and + update individual services when required (urgently if updates are security-related). Some of + the Docker containers I run I have built myself, in other cases I use those supplied by the + communities developing the service. +
++ One huge advantage of the Docker Compose pattern is that I can rapidly move services between + different hosts, or even replicate services very rapidly for development or staging purposes. + Using them has revolutionised my hosting processes.
-To manage the servers and keep them up-to-date, I use SSH to establish secure encrypted connections to them (via key-based authentication). I run updates of the hosts manually, and update individual services when required (urgently if updates are security-related). Some of the Docker containers I run I have built myself, in other cases I use those supplied by the communities developing the service.
-One huge advantage of the Docker Compose pattern is that I can rapidly move services between different hosts, or even replicate services very rapidly for development or staging purposes. Using them has revolutionised my hosting processes.
+ You can filter the software services listed below by the following filtering dimensions. + Click a tag to remove or re-add it or select all or none, or invert your selection if it's + more useful. +
+ You can These are general categories of software which help you understand the + sort of software you're looking at, as well as identifying functionally similar + software for comparison. +
+ Because all the software listed here is 'libre', I've included the names of functionally similar but heavily marketed + proprietary software that is therefore + better known to the general population, also for the purposes of understanding the + use of the software shown and to what it can be compared. +
+ These are the various 'open source' and 'copyleft' licenses that apply to the + software listed. You can chose +
Showing {filteredTechnologies.length} technology tiles.
+Current URL: {$page.url}...