mdebray/tvl-depot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
tvl-depot/blog/default.nix

22 lines
490 B
Nix
Raw Normal View History

Remove default values for Nix expression parameters I'm not sure if this commit breaks everything in my monorepo. I think it will. Why am I doing this? Perhaps it's a bad idea. I don't fully understand how readTree works. My ignorance is costing me hours of time spent debugging. In an effort to better understand readTree, I'm removing the default values for my Nix expression parameters, which I believe have preventing errors from surfacing.
2020-02-23 23:29:32 +01:00
{ pkgs, depot, briefcase, ... }:
Start working on a blog Attempting to write a blog where: - The server is Common Lisp. Why? I'd like to learn Common Lisp. - The blog posts can be written in Markdown. - The package is developed and deployed using Nix. Most of this is a learning exercise. The blog itself is something that I'd like to use instead of Medium and other forums.
2020-01-23 17:34:07 +01:00
Attempt to inject dependencies into blog/server - We need the markdown files, to be in the /nix/store and the server needs to be aware of there location. - Since we're dependending on `pandoc`, our server needs to know about it too. For both of these cases -- especially for the latter case -- I imagine there may be a more idiomatic way of doing this.
2020-01-23 19:25:10 +01:00
let
Remove default values for Nix expression parameters I'm not sure if this commit breaks everything in my monorepo. I think it will. Why am I doing this? Perhaps it's a bad idea. I don't fully understand how readTree works. My ignorance is costing me hours of time spent debugging. In an effort to better understand readTree, I'm removing the default values for my Nix expression parameters, which I believe have preventing errors from surfacing.
2020-02-23 23:29:32 +01:00
injections = pkgs.writeText "injections.lisp" ''
Attempt to inject dependencies into blog/server - We need the markdown files, to be in the /nix/store and the server needs to be aware of there location. - Since we're dependending on `pandoc`, our server needs to know about it too. For both of these cases -- especially for the latter case -- I imagine there may be a more idiomatic way of doing this.
2020-01-23 19:25:10 +01:00
(in-package #:server)
(setq *path-to-posts* "${./posts}")
Remove default values for Nix expression parameters I'm not sure if this commit breaks everything in my monorepo. I think it will. Why am I doing this? Perhaps it's a bad idea. I don't fully understand how readTree works. My ignorance is costing me hours of time spent debugging. In an effort to better understand readTree, I'm removing the default values for my Nix expression parameters, which I believe have preventing errors from surfacing.
2020-02-23 23:29:32 +01:00
(setq *pandoc-bin* "${pkgs.pandoc}/bin/pandoc")
Consolidate injected dependencies Move the three injected dependencies into one.
2020-01-31 17:30:25 +01:00
(setq *html-template* "${./src/index.html}")
Attempt to inject dependencies into blog/server - We need the markdown files, to be in the /nix/store and the server needs to be aware of there location. - Since we're dependending on `pandoc`, our server needs to know about it too. For both of these cases -- especially for the latter case -- I imagine there may be a more idiomatic way of doing this.
2020-01-23 19:25:10 +01:00
'';
in depot.nix.buildLisp.program {
Start working on a blog Attempting to write a blog where: - The server is Common Lisp. Why? I'd like to learn Common Lisp. - The blog posts can be written in Markdown. - The package is developed and deployed using Nix. Most of this is a learning exercise. The blog itself is something that I'd like to use instead of Medium and other forums.
2020-01-23 17:34:07 +01:00
name = "server";
Rename dotfiles -> briefcase Renaming my mono-repo briefcase. I first introduced this commit in master, but it introduced a bug where one of two things would happen: 1. Emacs wouldn't start and would crash X. 2. Emacs would start but my keyboard wouldn't work. I learned some valuable debugging skills in the process. Here are some of them: When my keyboard was broken, I wanted to control my computer using my laptop. Thankfully this is possible by using `x2x`, which forward X events from the SSH client to the SSH host. ```shell > # I'm unsure if this is the *exact* command > ssh -X desktop x2x -west :0.0 ``` Git commit-local bisecting. I didn't need to do a `git bisect` because I knew which commit introduced the bug; it was HEAD, master. But -- as you can see from the size of this commit -- there are many changes involved. I wanted to binary search through the changes, so I did the following workflow using `magit`: - git reset --soft HEAD^ - git stash 1/2 of the files changed - re-run `nix-env -f ~/briefcase/emacs -i` - restart X session - If the problem persists, the bug exists in the non-stashed files. Repeat the process until you find the bug. In my case, the bug was pretty benign. Calling `(exwm/switch "Dotfiles")` at the bottom of `window-manager.el` was failing because "Dotfiles" is the name of a non-existent workspace; it should've been `(exwm/switch "Briefcase")`. There may have been more problems. I changed a few other things along the way, including exposing the env vars BRIEFCASE to `wpcarros-emacs` inside of `emacs/default.nix`. The important part is that this was a valuable learning opportunity, and I'm glad that I'm walking away from the two days of "lost productivity" feeling actually productive.
2020-01-31 16:27:48 +01:00
deps = with depot.third_party.lisp; with briefcase.third_party.lisp; [
Start working on a blog Attempting to write a blog where: - The server is Common Lisp. Why? I'd like to learn Common Lisp. - The blog posts can be written in Markdown. - The package is developed and deployed using Nix. Most of this is a learning exercise. The blog itself is something that I'd like to use instead of Medium and other forums.
2020-01-23 17:34:07 +01:00
hunchentoot
Support proof-of-concept blog After some toil, I have a working proof-of-concept blog. The idea is simple: write blog posts in markdown and store the posts in the `./posts` directory. Then use the server and `pandoc` to convert these markdown files into HTML at request time. I'm using nix to package everything together. It's far from perfect, but it works at the moment, which is encouraging.
2020-01-23 22:58:31 +01:00
cl-arrows
Render pandoc output to index.html Using index.html allows us to use the Google AdSense script and extend the styling by adding a CSS stylesheet.
2020-01-31 17:13:22 +01:00
cl-ppcre
Start working on a blog Attempting to write a blog where: - The server is Common Lisp. Why? I'd like to learn Common Lisp. - The blog posts can be written in Markdown. - The package is developed and deployed using Nix. Most of this is a learning exercise. The blog itself is something that I'd like to use instead of Medium and other forums.
2020-01-23 17:34:07 +01:00
];
srcs = [
./src/server.lisp
Consolidate injected dependencies Move the three injected dependencies into one.
2020-01-31 17:30:25 +01:00
injections
Start working on a blog Attempting to write a blog where: - The server is Common Lisp. Why? I'd like to learn Common Lisp. - The blog posts can be written in Markdown. - The package is developed and deployed using Nix. Most of this is a learning exercise. The blog itself is something that I'd like to use instead of Medium and other forums.
2020-01-23 17:34:07 +01:00
];
}
Reference in a new issue Copy permalink