about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorFilesLines
2020-08-31 Lint zle.elWilliam Carroll1-14/+15
- Prefer dash instead of forward-slash - Remove stale TODOs - Add Version, Package-Requires
2020-08-31 Path relative path to Elisp code for elisp-lintWilliam Carroll1-1/+1
CI is reporting a false negative because $@ is empty. This change should cause elisp-lint to run on all of the Elisp in the wpc/ directory.
2020-08-31 Drop support for wpc-javaWilliam Carroll2-43/+0
1. I don't use this. 2. This is breaking CI because google-java-format cannot be found.
2020-08-31 Prevent all-the-icons-install-fonts from running in CIWilliam Carroll1-2/+4
While I would like my CI build to closely resemble a non-CI build, supporting the `all-the-icons-install-fonts` call is a low priority with a medium amount of work required.
2020-08-31 Drop support for wpgtkWilliam Carroll3-591/+0
I'd like to stabilize on using solarized-light.
2020-08-31 Apply prefix arg to all-the-icons-install-fontsWilliam Carroll1-1/+1
This prevents the prompt, which blocks my CI build.
2020-08-31 Drop support for neotreeWilliam Carroll1-5/+0
I don't use neotree anymore.
2020-08-31 Remove keybinding logic from fonts.elWilliam Carroll1-16/+0
For two reasons: 1. I don't use these keybindings. 2. I'm trying to centralize all keybinding logic in keybindings.el.
2020-08-31 Define constants/ci?William Carroll1-0/+5
Create a top-level flag encoding whether or not Emacs is running in CI.
2020-08-31 Delete {themes,wallpaper}.elWilliam Carroll3-246/+4
After my CI build for Emacs failed because the .local/share/wallpaper directory was missing I had two options: A. include .local/share/wallpaper in default.nix, which is cumbersome B. drop support for managing system wallpaper from Emacs I chose option B.
2020-08-31 Add xset to Emacs PATHWilliam Carroll1-0/+1
My CI failed after a call to xset resulted in a "file-missing Searching for program" error.
2020-08-31 Prefer inherit pattern to import Nix dependenciesWilliam Carroll1-13/+13
I'm starting to prefer the `inherit (builtins) path` pattern in my Nix expressions. I know this is idiomatic, so even if I don't like it, I am trying to learn to like it.
2020-08-31 Delete unused Emacs packagesWilliam Carroll1-3/+0
Cleaning things up...
2020-08-31 Allow configurable BRIEFCASE env var for CIWilliam Carroll2-38/+55
These were hard-coded as $HOME/BRIEFCASE, which won't work in CI, since CI runs as the user buildkite-agent-socrates, whose $HOME directory doesn't exist.
2020-08-31 Attempting to avoid buildkite parse errorWilliam Carroll1-1/+1
For more information, see here: https://github.com/buildkite/agent/issues/584
2020-08-31 Set Emacs line-spacing to 0William Carroll1-2/+2
vterm.el has a bug because it uses `(window-body-height)` to compute the number of lines it can render, but it doesn't account for `line-spacing`.
2020-08-31 Surround subshell in 2x-quotesWilliam Carroll1-1/+3
This wasn't a bug; it's just good practice.
2020-08-28 Call readTree on all top-level, visible directories in briefcaseWilliam Carroll1-24/+25
Instead of manually maintaining the list of directories that I expose to readTree, I'm using `builtins.readDir` to get a list of all non-hidden top-level directories.
2020-08-28 Restore "l" as evil-forward-char in magit-status-mode-mapWilliam Carroll1-0/+10
Remap "l" -> "L"
2020-08-27 Add build, lint Emacs steps to post-receive pipelineWilliam Carroll3-1/+75
TL;DR: - Define runEmacsScript to emacs/default.nix for ci/pipelines/post-receive - Write script.el to call (load init.el) and catch any errors - Lint Elisp with gonewest818/elisp-lint Also nice how Buildkite supports :gnu: emojis!
2020-08-27 Clean up emacs/default.nixWilliam Carroll1-5/+2
- Prefer prepending wpcDir, vendorDir to EMACSLOADPATH instead of using the --directory flag - Remove --load ${wpcPackageEl} because init.el calls (require 'wpc-package) - Surround $@ in 2x-quotes
2020-08-27 Remove exported DEPOT env var from wpcarros-emacsWilliam Carroll1-3/+0
wpcarros-emacs no longer depends on this being set.
2020-08-27 Prefer builtins.pathWilliam Carroll2-6/+32
Following the advice of Domen's nix.dev anti-patterns, I'm preferring something like... ```nix builtins.path { path = /path/to/some.where; name = "some.where"; } ``` ...to ```nix /path/to/some/where ``` While the former is more verbose, it will fail to build when the path doesn't exist, which I prefer.
2020-08-26 Delete unused parts of bookmark.elWilliam Carroll1-44/+1
Trimming more fat.
2020-08-25 Remove bookmark for <depot>William Carroll1-3/+0
Since depot now support cs.tvl.fyi, I don't need this, and that is a *massive* upgrade.
2020-08-25 Replace calls to (getenv "BRIEFCASE") with constants/briefcaseWilliam Carroll4-10/+17
I would prefer to define constants/briefcase in terms of `(getenv "BRIEFCASE")` and assert that `(f-exists? (getenv "BRIEFCASE"))`, in one location: constants.el
2020-08-25 Prefer <leader>jb to <leader>jd for searching all of briefcaseWilliam Carroll1-1/+1
Feels more natural...
2020-08-25 Delete org-helpersWilliam Carroll4-35/+0
I'm trying to tidy things up, so I'm trying to apply some of the principles from "Essentialism" to my Emacs configuration.
2020-08-25 Remove unnecessary TODOWilliam Carroll1-2/+0
The Nix expression that builds `wpcarros-emacs` sets BRIEFCASE, so the .envrc isn't relied on.
2020-08-25 Remove unnecessary code from wpc-nix.elWilliam Carroll1-5/+2
TL;DR: - Prefer `(getenv "BRIEFCASE")` to `(f-expand "~/briefcase")`. I should audit my Emacs for references to ~/briefcase and replace those calls with `getenv`. - Remove calls setting <nixpkgs> and <depot> and rely exclusively on <briefcase> - Prefer ~/nixpkgs-channels to ~/nixpkgs. Notes: - I need a better way of calling `home-manager switch` that resides within my briefcase
2020-08-24 Prefer simpler, more idiomatic project-find-functionWilliam Carroll1-24/+5
This version avoids installed all of the custom `cl-defmethods` for a `'monorepo` type and instead uses the existing `'transient`.
2020-08-22 Abandon the pre-receive hookWilliam Carroll2-11/+6
I wanted Gitea to call Buildkite's pre-receive pipeline and either accept or reject the incoming code depending on the outcome. The problem is that I can only *create* builds from Gitea's pre-receive hook. Now I'm left with two options: 1. run the lint-secrets step in post-receive 2. run `/nix/store/<hash>/git-secrets --scan-history $REPO_PATH` in Gitea As far as I can tell, I cannot define Gitea hooks in Nix, which is unfortunate; otherwise, option 2 would appeal more. I'm doing option one for now.
2020-08-22 Define Buildkite pipelines corresponding to git server hooksWilliam Carroll3-19/+20
I think maintaining a 1:1 correspondence with the git server hook makes sense right now. Let's try it out!
2020-08-22 Ensure that the build step "depends on" the lint stepWilliam Carroll1-0/+3
This way, if the lint step fails, the build step doesn't run. Nice!
2020-08-22 Remove --add-provider step from briefcase lintWilliam Carroll2-18/+10
So it turns out that I was wrong and that .git/config is stateful. Multiple calls to --add-provider will append the same provider each time... Instead I'm defining secret-patterns.txt and version-controlling it. Then: - dev-side: I'm adding `providers = cat ci/secret-patterns.txt` to .git/config - ci-side: I'm adding `providers = cat ci/secret-patterns.txt` to .git/config Unfortunately this is ad-hoc configuration ci-side, which I would like to avoid. The good news is that my pre-commit hooks and failures from git-secrets should now align with my CI, since they're both reading from secret-patterns.txt. One step backwards... two steps forwards?
2020-08-22 Call --add-provider during lint stageWilliam Carroll1-3/+16
I'm also `cat .git/config` because I think the Buildkite destroys the .git/config file for each build, but I want to verify that. If it does, I prefer that because it seems to share the spirit of the "Destroy Your Darlings" essay.
2020-08-22 Log git information during briefcase's lint stageWilliam Carroll1-1/+5
I would like to find out what the state of the repo is during pre-receive hook.
2020-08-22 Replace build badgeWilliam Carroll1-1/+1
Changed pipelines = new badge.
2020-08-21 Prefer :nix: emojiWilliam Carroll2-2/+2
Buildkite support language extensions as emojis!
2020-08-21 Use emojis for build, lint stepsWilliam Carroll2-3/+3
Y'know... the important stuff
2020-08-21 Remove debugging informationWilliam Carroll1-6/+1
Problem: my dev machine returns a different value for `git config --get-all secrets.patterns` than my CI machine... I ran `git-secrets --register-aws` to get additional coverage, but it's still not the same. I created an issue on the git-secrets GH repo to get better troubleshooting advice, but I don't need the logging info. anymore, so I'm removing it.
2020-08-21 Debugging briefcase pipelineWilliam Carroll1-1/+6
Somehow `git-secrets --scan-history` is exiting non-zero, when I don't think it should. Logging some environment information to get a better idea of what's going on.
2020-08-21 Call --scan-historyWilliam Carroll1-1/+1
My current pipeline is succeeding with a false-positive. After this change, it should return a true-negative.
2020-08-21 Define BuildKite pipelines in NixWilliam Carroll6-18/+33
After a handful of failed attempts to run lint-secrets.sh due to a missing `git-secrets` executable on my git server, I decided that now was a good time to use Nix to define my BuildKite pipelines. TL;DR: - Delete ci/scripts directory - Define ci/pipelines/{briefcase,socrates}.nix Outside of this repository: - I logged into my admin account at git.wpcarro.dev and changed my Gitea post-receive hook to trigger the briefcase pipeline - I logged into my BuildKite account, deleted my build-briefcase pipeline, created a new briefcase pipeline that called: ```shell nix-build -A ci.pipelines.briefcase -o briefcase.yaml buildkite-agent pipeline upload briefcase.yaml ``` One day I will audit all of my ad-hoc, non-mono-repo activity (like the steps I listed above) and attempt to fit everything herein... one step at a time, though!
2020-08-20 Testing new CI lint-secrets stepWilliam Carroll1-0/+3
Adding a fake secret to test to the new CI build step. I'm not sure I expect this to fail the step because it relies on a pattern that I defined in .git/config... let's see!
2020-08-20 Call `git secret hide` whenever //secrets.json is savedWilliam Carroll1-0/+6
Having `git secret hide` as a pre-commit hook doesn't make much sense to me. I will detail why when/if I write a blog post on briefcase's secret mgt setup. The problem is, if I change secrets.json and then run `git status`, I won't see any pending changes. This is because secrets.json is gitignore'd. If I run `git secret hide` everytime I save secrets.json, I can rest assured that my `git status` will be consistent with any updates to secrets.json.
2020-08-20 Prefer reading secrets.json to using pass showWilliam Carroll5-8/+14
I'm attempting to maintain a top-level secrets.json that defines all of the sensitive data that I'd like to version-control without exposing everything in cleartext to the world. To that end, I'm using `git secret`, which will use `gpg` to encrypt secrets.json everytime I call `git secret hide` and decrypt everytime I call `git secret reveal`. I'm going to try this until I don't like it anymore... if that day comes... I should write a blog post about my setup to solicit useful feedback and share my ideas with others.
2020-08-20 Testing git-secretWilliam Carroll3-0/+2
Adding a dummy, top-level secrets.json file using `git-secret`. It might be nice to have a mono-secrets file in json because then I can use it with `jq` like: ```shell $ jq '.secret' --join-output < ~/briefcase/secrets.json ```
2020-08-20 Remove 2x-newlines from .gitignoreWilliam Carroll1-5/+0
I saw an issue on GitHub that claims that git-secret doesn't like 2x-newlines in .gitignore files. Let's see if that helps...
2020-08-20 Setup git-secretWilliam Carroll5-0/+2
This morning I'm attempting to secure my monorepo. How? - `git secret`: DONE: To version-control sensitive data - `git secrets`: TODO: Lint code for sensitive data I will probably update the CI to call `git secrets --scan` or some similar command to fail when that exists non-zero. I have much to learn, but doing is the best way to learn it.
generated by cgit-pink 1.4.1 (git 2.44.2) at 2024-10-30T11·29+0000