This simple app is a work-in-progress that allows visitors to see the various libre web services I currently run, filter them on a variety of properties like functional categories, similar proprietary apps, libre license used, instance status, which of my roles they're affiliated with, and on which host they reside...
-The source code for this project is available under an AGPL license.
-This app is built on a suite of technologies that are largely new to me, but that I wanted to try out, as I see great potential in them. The key technology is a Javascript 'framework' called SvelteKit, built with Svelte (a compiled language that generates pure Javascript) and ecosystem of extensions created by the community which provides useful components designed for reuse. +
+ This sites exists to provide an always-up-to-date, in-depth catalogue of the + libre software + web services I (Dave Lane) have set up and maintain.
++ This collection is as much for my benefit as it is for others, who might want to learn more about libre technologies they could use in their own organisations. My purpose here is to show the libre services I (or my colleagues and customers) have found compelling enough to warrant setting up instances either for testing or full production. The options are many, diverse, and often mature and highly functional. +
+ ++ 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. +
+ diff --git a/src/routes/project/+page.svelte b/src/routes/project/+page.svelte new file mode 100644 index 0000000..da8d888 --- /dev/null +++ b/src/routes/project/+page.svelte @@ -0,0 +1,42 @@ + ++ This simple app is a work-in-progress that allows visitors to see the various libre web services I currently run, filter them on a variety of properties like functional categories, similar proprietary apps, libre license used, instance status, which of my roles they're affiliated with, and on which host they reside... +
++ The source code for this project is available under an AGPL license. +
++ This app is built on a suite of technologies that are largely new to me, but that I wanted to try out, as I see great potential in them. The key technology is a Javascript 'framework' called SvelteKit, built with Svelte (a compiled language that generates pure Javascript) and ecosystem of extensions created by the community which provides useful components designed for reuse. +
++ In future, I'd like to enhance this app to: +
++ include an 'uptime' dashboard, showing the current status of each of the instances. +
++ make it possible to reference a given technology tile with unique web address (URL). +
++ allow users to page through the 'close up' view of technologies in their filtered list. +
++ support limiting technologies to those featuring instances set up for a subset of Affiliates, allowing an up-to-date list of available webservices for my specific affiliates like those I run for the OER Foundation (my employer), my various volunteer roles, my consulting customers, and for my personal edification and utility. +
++ provide a host-based map, which shows instances of technologies running on specific hosts (and shows their current status), which would help me diagnose problems, but also provide users of those services with a quick place to see where there might be problems affecting their access. +
+