about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorFilesLines
2019-06-29 r/4 feat(build): Add top-level package index fileVincent Ambo1-0/+17
2019-06-29 r/3 feat(tazblog): Add Nix build configurationVincent Ambo2-0/+29
2019-06-29 r/2 merge(tazblog): Integrate blog into monorepoVincent Ambo18-0/+1101
2019-06-29 chore(tazblog): Remove files from ye olde timesVincent Ambo11-227/+0
2019-06-28 chore: Keep project root under MIT licenseVincent Ambo1-1/+1
To comply with Google's open-source patching rules :)
2019-06-28 refactor: Move tazblog into monorepo structureVincent Ambo30-1/+0
It's happening!
2019-06-28 r/1 chore: Initialize tazj.in monorepoVincent Ambo0-0/+0
2018-05-03 chore(dns): Update Github pages IP addressesVincent Ambo1-4/+8
2018-01-03 fix(nix): Fix Gogs SSH accessVincent Ambo1-0/+4
The Gogs developers got it into their head that trying to write things to some relative path from the binary location is a sensible thing to do (spoiler: it's not). Due to their weird "GOGS_CUSTOM" directory which seems to only sometimes be configurable by environment variables, the command used to handle SSH requests failed because it attempted to write logs into the Nix store. This works around the issue by hardcoding the log file root path in the Gogs configuration.
2018-01-03 feat(nix): Add Gemma example deploymentVincent Ambo3-0/+99
2018-01-03 chore: Clean up old Kubernetes configurationVincent Ambo21-519/+0
2018-01-03 feat(tazj.in): Add gemma.tazj.in hostVincent Ambo1-1/+2
2018-01-03 feat(build): Configurable output locationVincent Ambo2-5/+5
For easier Nix builds!
2018-01-03 refactor(build): Use ASDF facility for output namingVincent Ambo2-5/+4
Turns out there is an easy-to-use :build-pathname parameter to set the output binary name. This kills the hack!
2018-01-03 fix(tazj.in): Set A-record TTLs back to 300 secondsVincent Ambo1-3/+3
2018-01-03 feat(nix): Configure oslo.pub redirect correctlyVincent Ambo1-0/+7
2018-01-03 feat(dns): Import oslo-pub zone to gitVincent Ambo1-0/+8
2018-01-02 fix(nix): Correctly configure required kernel modules & VMWare guestVincent Ambo1-0/+10
2018-01-02 refactor(nix): Use disk labels instead of disk UUIDsVincent Ambo2-6/+6
Makes configuration portable between VM instances.
2018-01-02 feat(nix): Configure Gogs setupVincent Ambo2-3/+23
2018-01-02 feat(dns): Move tazblog over to GleSYS machineVincent Ambo1-9/+6
2018-01-02 feat(nix): Configure reverse-proxy for tazblogVincent Ambo2-9/+25
2018-01-01 feat(nix): Add initial Tazblog Nix deployment configurationVincent Ambo6-0/+3655
2018-01-01 feat(dns): Add Runbox SPF & renew Keybase verificationVincent Ambo1-1/+3
2017-12-31 feat(nix): Add Docker building configurationVincent Ambo1-0/+19
2017-12-31 fix(elm): Use relative URL to access APIVincent Ambo1-2/+2
Now that Hunchentoot is serving the Elm frontend, Elm needs to connect to Gemma at a relative path. Side note: It would be useful if the frontend displayed errors that happened :sun:
2017-12-31 feat(lisp): Correctly set location for static assets in Nix buildsVincent Ambo2-9/+12
In order to let Hunchentoot serve the static assets from the correct location, the *static-file-location* parameter is set before image dumping based on the $out-envvar which is present during the build process. This can easily be set manually in the config file if required by a user.
2017-12-29 feat(build): Add initial Nix-based build processVincent Ambo3-0/+91
Adds a build script using ASDF's program-op to build an executable out of the Gemma source code. In addition a Nix derivation is provided that will both compile the Elm source and place it in a folder, as well as create the executable. Currently static file serving does not function as intended.
2017-12-26 feat(build): Configure ASDF program-op with entrypointVincent Ambo2-2/+18
2017-12-26 docs(README): Update docs with a note about configurationVincent Ambo1-3/+8
2017-12-26 docs: Add example configuration fileVincent Ambo2-20/+22
2017-12-26 feat(lisp): Implement configuration loadingVincent Ambo1-18/+33
Adds configuration loading from a file located at either "/etc/gemma/config.lisp" or a path determined via the `GEMMA_CONFIG` environment variable. The configuration file can contain any number of deftask forms and a single config form which determines the location at which Gemma stores its data and also the port on which it should listen.
2017-12-24 fix(lisp): Don't intern symbols for unregistered tasksVincent Ambo1-1/+1
2017-12-22 Bump to LTS 9.20Vincent Ambo1-1/+1
2017-12-22 Bump to LTS 9.11Vincent Ambo1-13/+5
2017-12-21 feat(lisp): Make server port configurableVincent Ambo1-1/+5
2017-12-21 refactor(lisp): Use imported symbols with local qualificationVincent Ambo1-14/+12
... except hunchentoot, I like using that fully-qualified because it's a great word.
2017-12-21 fix(lisp): Automatically snapshot after task completionsVincent Ambo1-1/+2
2017-12-21 feat(lisp): Implement persistent storage via cl-prevalenceVincent Ambo2-19/+45
Uses the cl-prevalence system to store tasks on disk. The storage location is either relative to the working directory in which the system is started or determined (with priority) by the environment variable `GEMMA_DATA_DIR`.
2017-12-20 docs: Add README with project explanation and backgroundVincent Ambo1-0/+91
2017-12-20 chore: Add code of conduct to projectVincent Ambo1-0/+20
2017-12-20 chore: License under GPLv3Vincent Ambo4-5/+700
2017-12-20 feat(elm): Automatically poll every 15 secondsVincent Ambo1-1/+13
15 seconds is potentially a bit aggressive considering that Gemma (currently) tracks expiry times in *days*.
2017-12-20 feat(elm): Add real button to task cardsVincent Ambo1-8/+14
2017-12-20 feat(elm): Add nice little texts to display time remainingVincent Ambo1-5/+16
2017-12-20 feat(elm): Implement task completion handlingVincent Ambo1-11/+39
Adds a clickable area to the cards that will inform the backend of a task being completed. This of course still looks completely terrible because I don't really know how frontend works.
2017-12-20 feat(elm): Add initial (broken) MDL layout for tasksVincent Ambo2-21/+75
The idea is that every task should be shown as an MDL "card" and have some sort of associated action (probably more than just a click, but that I'll look at ...). Tasks are coloured based on their current "urgency".
2017-12-20 feat(lisp): Add Hunchentoot handler for task completionVincent Ambo1-5/+18
2017-12-20 fix(lisp): Sort tasks in DESCENDING orderVincent Ambo1-1/+1
2017-12-20 feat(elm): Add initial logic for Gemma's Elm frontendVincent Ambo2-0/+117