| Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I3b00408d7550d7660fb33940ae2cd0806076f4d2
Reviewed-on: https://cl.fcuny.net/c/world/+/62
Reviewed-by: Franck Cuny <franck.cuny@gmail.com>
|
|
Change-Id: Idba41215b58e8cd77d8d4efa354a3acf52c6bc6d
Reviewed-on: https://cl.fcuny.net/c/world/+/61
Reviewed-by: Franck Cuny <franck.cuny@gmail.com>
|
|
cgit is a git web viewer, it will be hosted at git.fcuny.net to replace
gitea.
Change-Id: I16561776fa90a3561d6a13f8545bd2e8f67f409a
Reviewed-on: https://cl.fcuny.net/c/world/+/46
Reviewed-by: Franck Cuny <franck.cuny@gmail.com>
|
|
Change-Id: Ie217a14a20474b626a2c66116663b785193978c2
|
|
Change-Id: I94e28dc52d69c3c2ee4d59a0109c9ae32402fb2c
|
|
Change-Id: I3fadf8a3a9a81c7966b4c048ace1ae259f0e3668
|
|
Change-Id: I3e4a215b47a5a368210b268fa170aa2dddab721f
|
|
Change-Id: I449f9032e32911fa33c26ec41faadb4f8acc8b1f
|
|
|
|
The default configuration wants to run gerrit with a DynamicUser.
However, this prevent the server to generate the ssh keys needed by
gerrit. Instead, we can force the server to run with the 'git' user,
which already exists.
|
|
|
|
|
|
|
|
This identify the server (see
https://github.com/NixOS/nixpkgs/blob/634141959076a8ab69ca2cca0f266852256d79ee/nixos/modules/services/web-apps/gerrit.nix#L141).
|
|
|
|
Gerrit is a tool for doing code review for git. It will be running at
cl.fcuny.net and will be the main way to interact with my git
repositories.
|
|
Integrate properly the tool `dnsupdate` with flake.nix, by adding a
default.nix inside its directory.
Having all the tools under a directory named `tools` is easier to reason
about. I don't need a go.mod at the top level directory either, each
tool will have its own.
|
|
There's no need to have a flake.nix for the notes, we can use the same
mechanism as for the blog and resume.
Add a README so I remember how to use this in the future.
|
|
This is needed in order to replace the flake.nix with a default.nix,
like I did for the blog earlier.
|
|
Integrate the resume with the rest of the repository, as I did for the
blog in the previous commit.
Added a script to copy the resume in the static directory of the blog.
|
|
There's no need to have multiple `flake.nix` in the repository. Make the
blog part of the flake configuration at the root level of the
repository, delete the one in the blog, and update the documentation.
|
|
This is not going to work with the next change, so I'm just going to
drop it.
|
|
I can now have a readme.org with instructions on how to generate the
resume (because I'll obviously forget again).
|
|
|
|
In a monorepo setup, the CI configuration is not used at this level of
the tree, and the gitignore/envrc are not relevant.
|
|
In a monorepo setup, the CI configuration is not used at this level of
the tree, and the gitignore/envrc are not relevant.
|
|
In a monorepo setup, the CI configuration is not used at this level of
the tree, and the gitignore/envrc are not relevant.
|
|
|
|
Run sourcegraph ([0]) in a docker container. It's exposed as
cs.fcuny.xyz, and we backup some of the directories.
[0] https://docs.sourcegraph.com
|
|
This will be used for sourcegraph.
|
|
This script (`perf-flamegraph-process') takes a process as an argument,
and will run it with `perf' to capture the call graph, and will
generate the flamegraph from it. The SVG is saved under
`~/workspace/tmp/flamegraph'.
|
|
In order to write good commit message, having a reminder of how to write
them is useful. This template provides some guidance to categorize the
change and how to phrase the description.
|
|
|
|
|
|
|
|
If login, start sway. If tmux is not running, start it.
|
|
|
|
|
|
|
|
|
|
`zsh' is available everywhere and is compatible with bash. When using
`fish' I need to remember how to do things. While the completion style
is nicer, I don't care about the rest. I prefer to have a consistent
experience in the shell, no matter where am I.
This is an initial configuration, I might need to make a few changes as
I go.
|
|
|
|
|
|
|
|
|
|
The `documents` folder was not being synced.
|
|
|
|
|
|
There's already something on port 3000.
|
|
|
|
|
|
|
|
This is not needed anymore.
|
<