about summary refs log tree commit diff
path: root/users (follow)
Commit message (Collapse)AuthorAgeFilesLines
* ref(users/fcuny): and just like that ...Franck Cuny2022-10-2725-797/+0
|
* ref(fcuny/exp): delete containerd-to-vmFranck Cuny2022-10-057-1510/+0
| | | | The code is in https://github.com/fcuny/containerd-to-vm
* ref(fcuny/notes): delete notesFranck Cuny2022-10-0524-1608/+0
| | | | The notes are at https://github.com/fcuny/notes.fcuny.net
* ref(fcuny/blog): delete the blogFranck Cuny2022-10-0529-1007/+0
| | | | The blog moved back to https://github.com/fcuny/fcuny.net
* fix(user/blog): update list of ssh keysFranck Cuny2022-09-241-2/+2
|
* ref(flake): tools and users packages are managed the same wayFranck Cuny2022-08-061-0/+9
| | | | | | | | | | Configure the way we import these packages the same way, that way it's consistent and easy to use. Change-Id: I0e218f8fe9dd4cd2045bfee11c80de84ff769fe1 Reviewed-on: https://cl.fcuny.net/c/world/+/703 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
* fix(new-lines): add or remove new lines where neededFranck Cuny2022-07-025-5/+1
| | | | | | | | | | | The pre-commit hook for new lines reported and correct a number of issues, so let's commit them now and after that we ca enable the hook for the repository. Change-Id: I5bb882d3c2cca870ef94301303f029acfb308740 Reviewed-on: https://cl.fcuny.net/c/world/+/592 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
* delete reference to namespacesFranck Cuny2022-06-136-27/+21
| | | | | | We don't need namespaces, a better abstraction is to use different buckets, as this provides a better abstraction to manage quotas and permissions.
* github: don't install libpcapFranck Cuny2022-06-131-3/+0
| | | | There's no need to install the libpcap-dev package for this repo.
* github: fix workflow configurationFranck Cuny2022-06-131-1/+1
| | | | There's no `cmd` directory in this repo.
* github: add workflow configurationFranck Cuny2022-06-131-0/+38
| | | | | Let's ensure we test and build a binary when pushing to main and when we create a pull-request.
* add stub commands for buckitFranck Cuny2022-06-138-0/+130
| | | | | | | | | Add the stub commands for the binary. Each command will be in its own file (with the exception of delete/un-delete). This will make it easier to navigate the code. We use `github/urfave/cli` for generating the sub commands, as the module is well documented and easy to use.
* git: ignore the generated binary buckitFranck Cuny2022-06-131-0/+1
|
* initial documentationFranck Cuny2022-06-132-1/+63
| | | | This is a high level description of what buckit is and how it works.
* Add README.md, LICENSE.txtFranck Cuny2022-06-132-0/+21
|
* fix(notes): correct the URL to containerd-to-vm codeFranck Cuny2022-06-111-1/+1
| | | | | | | Change-Id: Ifcd265c515b0fc5e1999eed0d7594475e84a346a Reviewed-on: https://cl.fcuny.net/c/world/+/413 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
* repo(containerd-to-vm): remove unneeded filesFranck Cuny2022-06-112-40/+0
| | | | | | | Change-Id: I4d229d0f4a9142e3bd427a8e63733426f5ca5bd9 Reviewed-on: https://cl.fcuny.net/c/world/+/412 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
* publish firecracker metrics in a FIFOFranck Cuny2022-06-111-2/+4
| | | | | We add a new argument to the CLI to collect the path where we want to publish the firecracker metrics.
* Makefile: install binaries and configsFranck Cuny2022-06-111-6/+23
| | | | | | | To help working on this project in the future, let's try to install dependencies and configurations with `make`. For now we know that we need the firecracker binary, the CNI configuration and the CNI plugin for TAP.
* rename the variable for the linux kernelFranck Cuny2022-06-111-7/+7
|
* c2vm: fix kernel boot optionsFranck Cuny2022-06-111-1/+1
| | | | | | | By specifying these options we can speed up the boot process from 0.9 second to 0.15 seconds. Without these options, the linux kernel spends a few milliseconds probing the device, which is useless in our context (see https://github.com/firecracker-microvm/firecracker/blob/main/docs/api_requests/actions.md#intel-and-amd-only-sendctrlaltdel)
* readme: update instructionsFranck Cuny2022-06-111-0/+16
|
* boot the VMFranck Cuny2022-06-113-4/+256
| | | | | | | | | The binary needs a few more arguments: the path to the firecracker binary, the path to a linux kernel. Using the image that was generated, we can now boot the VM with firecracker. This will rely on a CNI configuration to create the network, and will use the provided kernel to boot.
* hack: firecracker binary and CNI configurationFranck Cuny2022-06-113-0/+35
| | | | | | | | | Add a target to the Makefile to download a version of firecracker and extract it under the repository hack/firecracker. We will then use this binary for running the VM. Add a CNI configuration under hack/cni. This configuration will need to be copied to `/etc/cni/conf.d`.
* git: ignore binaryFranck Cuny2022-06-111-0/+1
|
* add MakefileFranck Cuny2022-06-111-0/+3
|
* check for errorFranck Cuny2022-06-111-0/+3
| | | | | When reading the configuration for the container, if there's an error we return the error to the caller.
* github: add workflowsFranck Cuny2022-06-111-0/+35
| | | | Add a workflows to perform some validation when pushing new commits.
* inject a script for initFranck Cuny2022-06-111-0/+43
| | | | | | | | | Once we will be ready to boot our VM, we will need an init script in place. For this, we create a simple shell script which we populate using the environment variables and command extracted from the container. The init script is stored in /init.sh within the new image, and we will configure the boot parameter to find it there.
* extract layers to a mounted loop deviceFranck Cuny2022-06-113-1/+128
| | | | | | | | | | | | | We create a loop device by pre-allocating space to a file on disk. This file is then converted to an ext4 partition, which we mount to a temporary path on the host. Once this is done, we extract all the layers from the given container on that mounted path. We also add a few extra files to the image (`/etc/hosts` and `/etc/resolv.conf`). When we're done extracting and writing, we run resize2fs in order to resize the image to a more reasonable size.
* add a lease to the Go contextFranck Cuny2022-06-111-0/+6
| | | | | | | | | | | | This will ensure that our container will not be deleted while we work on it. In addition, a default expiry of 24 hours will be set on it once the lease is released (once the program is completed). See [1] for more details. [1] https://github.com/containerd/containerd/blob/261c107ffc4ff681bc73988f64e3f60c32233b37/docs/garbage-collection.md Signed-off-by: Franck Cuny <franck@fcuny.net>
* pull a container into a namespaceFranck Cuny2022-06-114-0/+975
| | | | | | | | | | | | | | | | | | | | Pull an image provided as an argument to the program. We're only interested in images for Linux/amd64 at the moment. We setup a default namespace for containerd named `c2vm`. Images that will be pulled by containerd will be stored inside that namespace. Once the program is build it can be run like this: ``` ; sudo ./c2vm -container docker.io/library/redis:latest pulled docker.io/library/redis:latest (38667897 bytes) ``` And the image is indeed in the namespace: ``` ; sudo ctr -n c2vm images ls -q docker.io/library/redis:latest ```
* doc: update READMEFranck Cuny2022-06-112-1/+15
|
* Add README.md, LICENSE.txtFranck Cuny2022-06-112-0/+21
|
* fix(scripts): no need to create tags when deploying to fly.ioFranck Cuny2022-06-102-16/+4
| | | | | | | | | | | | | I don't need tags in this repository. There's no need to create them after a deploy. Before stopping the fly.io agent, checks that we're in the CI environment. Change-Id: I6208b70023c6ae74d58e535e24b44221956dbe63 Reviewed-on: https://cl.fcuny.net/c/world/+/408 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
* fix(blog): set the correct URL to my git serverFranck Cuny2022-06-091-1/+1
| | | | | | | Change-Id: I0911c07d5ab0e17a09e587ba4507d0202f6c7ff3 Reviewed-on: https://cl.fcuny.net/c/world/+/364 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
* fix(fcuny/monkey): remove unneeded filesFranck Cuny2022-05-292-21/+0
| | | | Change-Id: If26166f29f9b519b87e288b514d2c603ca9b4413
* Merge remote-tracking branch 'monkey/master'Franck Cuny2022-05-2910-0/+421
|\ | | | | | | Change-Id: I790690b0877ae309d1d5feb5150f136085e78206
| * readme: convert to org-modeFranck Cuny2021-05-102-1/+3
| |
| * lint: fix a few issuesFranck Cuny2021-05-103-1/+4
| |
| * git: ignore binary for the REPLFranck Cuny2021-05-101-0/+1
| |
| * repl: support a simple REPL for some early testingfranck cuny2020-01-112-0/+41
| | | | | | | | | | | | The REPL reads the input, send it to the lexer, and prints the token to STDOUT. For now nothing else is done since we still don't parse the tokens.
| * lexer: support tokens for equal and not equal.franck cuny2020-01-112-2/+39
| | | | | | | | | | | | | | | | | | The tokens for equal (`==`) and not equal (`!=`) are composed of two characters. We introduce a new helper (`peekChar`) that we use when we encounter the token `=` or `!` to see if this is a token composed of two characters. Add some tests to ensure they are parsed correctly.
| * token: add tokens for equal and not equal.franck cuny2020-01-111-0/+3
| |
| * lexer: test the new keywords are parsed correctly.franck cuny2020-01-111-3/+25
| | | | | | | | | | Ensure that the new keywords added (`if`, `else`, `true`, `false`, `return`) are parsed correctly.
| * token: support more keywordsfranck cuny2020-01-111-2/+13
| | | | | | | | | | | | | | Add support for a few more keywords (`true`, `false`, `if`, `else`, `return`). All keywords are grouped together in the constant declaration.
| * token: rewrite documentation for `LookupIdent`.franck cuny2020-01-111-3/+4
| |
| * lexer: delete redundant test.franck cuny2020-01-111-32/+1
| | | | | | | | | | | | | | The test `TestNextTokenBasic` was not testing anything that `TestNextTokenMonkey` was not already testing. Rename `TestNextTokenMonkey` to `TestNextToken` for clarity.
| * Makefile: add a Makefilefranck cuny2020-01-111-0/+4
| | | | | | | | For now, automate running the tests.
| * lexer: support more operator tokens.franck cuny2020-01-112-1/+31
| | | | | | | | | | Support the operator tokens that were added to our tokenizer. This also add a few more tests to ensure we handle them correctly.
| * token: support more operator tokensfranck cuny2020-01-111-3/+10
| | | | | | | | | | | | Support additional tokens for operators (`-`, `*`, etc). This change only adds the tokens to the list of constants, and group all the tokens related to operators together.
| * lexer: initial lexerfranck cuny2020-01-112-0/+218
| | | | | | | | | | | | | | | | | | The initial lexer for the monkey language. We only support a small subset at this stage. We have some simple tests to ensure that we can parse some small snippet, and that the minimum number of tokens we need are also all supported correctly.
| * token: initial tokenizer.franck cuny2020-01-111-0/+48
| | | | | | | | | | | | | | | | | | | | | | This is the initial tokenizer for the monkey language. For now we recognize a limited number of tokens. We only have two keywords at this stage: `fn` and `let`. `fn` is used to create function, while `let` is used for assigning variables. The other tokens are mostly to parse the source code, and recognize things like brackets, parentheses, etc.
| * go.mod: create the module 'monkey'franck cuny2020-01-111-0/+3
| | | | | | | | | | | | The project is named monkey, we add a mod file to ensure that the tooling / dependencies are set up correctly when we import various modules in this project.
| * Add README.md, LICENSE.txtfranck cuny2019-12-292-0/+21
|
* ref(notes): drop flake.nixFranck Cuny2022-05-255-88/+46
| | | | | | | 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.
* ref(notes): don't rely on git for modified dateFranck Cuny2022-05-251-1/+0
| | | | | This is needed in order to replace the flake.nix with a default.nix, like I did for the blog earlier.
* ref(resume): remove flake.nixFranck Cuny2022-05-254-71/+35
| | | | | | | 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.
* ref(blog): drop the flake configurationFranck Cuny2022-05-255-89/+39
| | | | | | 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.
* ref(blog): drop the `enableGitInfo` optionFranck Cuny2022-05-251-1/+0
| | | | | This is not going to work with the next change, so I'm just going to drop it.
* feat(resume): rename readme.org to resume.orgFranck Cuny2022-05-233-40/+44
| | | | | I can now have a readme.org with instructions on how to generate the resume (because I'll obviously forget again).
* feat(resume): set the version using the dateFranck Cuny2022-05-231-1/+2
|
* ref(resume): remove unneeded files for my resumeFranck Cuny2022-05-233-12/+0
| | | | | In a monorepo setup, the CI configuration is not used at this level of the tree, and the gitignore/envrc are not relevant.
* Merge remote-tracking branch 'resume/main'Franck Cuny2022-05-237-0/+193
|\
| * remove unused tex styleFranck Cuny2022-05-131-106/+0
| |
| * simplify the buildFranck Cuny2022-05-084-16/+41
| | | | | | | | | | | | | | Running `nix build` is enough to generate the file `resume.html`. It will be created in the `result` directory automatically. The configuration for the build is also updated to run `nix build`
| * drone: add configurationFranck Cuny2022-05-072-0/+9
| |
| * initial commitFranck Cuny2022-05-017-0/+265
|
* ref(notes): remove unneeded files for my notesFranck Cuny2022-05-233-21/+0
| | | | | In a monorepo setup, the CI configuration is not used at this level of the tree, and the gitignore/envrc are not relevant.
* Merge remote-tracking branch 'notes/main'Franck Cuny2022-05-2326-0/+1677
|\
| * delete MakefileFranck Cuny2022-05-111-27/+0
| | | | | | | | This is not needed anymore.
| * nix: add more contentFranck Cuny2022-05-111-0/+4
| |
| * add drone configurationFranck Cuny2022-05-111-0/+18
| |
| * add flake supportFranck Cuny2022-05-113-0/+89
| |
| * add a script to deploy the siteFranck Cuny2022-05-112-8/+15
| | | | | | | | | | Instead of using the Makefile, move the content to a script. This will be executed by drone later.
| * remove GitHub action workflowFranck Cuny2022-05-111-18/+0
| |
| * remove atom from the list of outputsFranck Cuny2022-05-111-9/+1
| |
| * update gitignoreFranck Cuny2022-05-101-0/+1
| |
| * nix: add tagsFranck Cuny2022-05-101-0/+1
| |
| * go: replace lsp-mode with eglotFranck Cuny2022-05-101-66/+15
| |
| * nix: start documenting what I'm learningFranck Cuny2022-05-101-0/+21
| |
| * content: update PCIe docFranck Cuny2022-04-031-1/+4
| |
| * site: remove unnecessary elementsFranck Cuny2022-04-038-116/+40
| |
| * delete some contentFranck Cuny2022-03-287-238/+0
| |
| * convert blog to notesFranck Cuny2022-03-2811-116/+117
| | | | | | | | Separating the two sites so I can customize them differently.
| * note: update list of chipset for alder lakeFranck Cuny2022-01-301-2/+11
| |
| * build: use more recent version of hugoFranck Cuny2022-01-231-1/+1
| |
| * notes: remove some columns for the various CPUsFranck Cuny2022-01-231-20/+22
| |
| * CSS: improve readabilityFranck Cuny2022-01-231-6/+9
| | | | | | | | Using Firefox' accessibility tool as a guide.
| * CSS: adjust some font sizesFranck Cuny2022-01-231-2/+2
| |
| * CSS: switch from class to idFranck Cuny2022-01-232-14/+14
| | | | | | | | These elements are unique on each page.
| * layout: no need for a class to element 'article'Franck Cuny2022-01-233-3/+3
| |
| * css: TOC location based on display's sizeFranck Cuny2022-01-231-19/+82
| | | | | | | | | | Depending on the size of the display, display the TOC either before the article or on the right of the article and let's make it sticky.
| * layout: proper TOCFranck Cuny2022-01-231-4/+13
| | | | | | | | | | | | | | | | | | | | | | | | There's a need for two TOCs in the layout: one for when the page is on mobile; one for non mobile. When we are on mobile, we display the first TOC, before the article. When we're not on mobile, we hide that TOC and display one after the document. We restructure a bit the layout so that's it's a bit more readable too, and close tags properly.
| * layout: wrap content in an "article" tagFranck Cuny2022-01-232-0/+8
| |
| * layout: drop the div 'main'Franck Cuny2022-01-231-6/+4
| | | | | | | | | | The div 'main' is not needed, we are creating an element named 'named' in the main block.
| * css: change style for tablesFranck Cuny2022-01-231-4/+8
| |
| * css: update color for the linksFranck Cuny2022-01-231-3/+3
| | | | | | | | Use a light blue.
| * nav: use 'fcuny.net' instead of template variableFranck Cuny2022-01-211-1/+1
| | | | | | | | | | Otherwise it's the name of the site, which is not what I'm looking for here.
| * css: major cleanupFranck Cuny2022-01-211-76/+84
| |
| * nav: align the menu items to the rightFranck Cuny2022-01-211-2/+7
| |
| * post: change formatting for the dateFranck Cuny2022-01-211-4/+4
| |
| * nav: drop one item from the menuFranck Cuny2022-01-211-7/+0
| |
| * blog: leaving twitterFranck Cuny2022-01-151-0/+10
| |
| * css: more tweakingFranck Cuny2022-01-131-29/+21
| |
| * index: rephraseFranck Cuny2022-01-101-1/+1
| |
| * index: update current jobFranck Cuny2022-01-081-1/+1
| |
| * blog: add content about PCIeFranck Cuny2022-01-081-0/+196
| |
| * blog: notes about AMD and Intel CPUsFranck Cuny2021-12-291-0/+120
| |
| * css: change colors for some sectionsFranck Cuny2021-12-291-7/+13
| |
| * css: adjust line heightFranck Cuny2021-12-291-4/+1
| |
| * css: highlight links with a background colorFranck Cuny2021-12-291-2/+13
| |
| * blog: article on how to use tailscale + traefikFranck Cuny2021-12-291-0/+121
| |
| * config: add author informationFranck Cuny2021-12-291-0/+4
| |
| * layout: add a link to the RSS feed in the menuFranck Cuny2021-12-291-1/+10
| | | | | | | | | | Specify the weight so that the items in the menu are listed in the order I want.
| * RSS: fix the templateFranck Cuny2021-12-291-3/+5
| | | | | | | | | | Generate correctly the content of the RSS feed. I only want the blog articles, not the notes.
| * css: improve the color and fontsFranck Cuny2021-12-201-116/+47
| |
| * index: re-organize the main pageFranck Cuny2021-12-201-9/+11
| | | | | | | | Add a "contact" header with my information under it.
| * menu: simplify the menuFranck Cuny2021-12-202-9/+10
| |
| * build: push git branches / tags after deployFranck Cuny2021-12-061-0/+2
| | | | | | | | After a successful deploy, push all the branches / tags to origin.
| * CSS: drop custom fonts + colorsFranck Cuny2021-12-061-19/+22
| |
| * resume: updateFranck Cuny2021-11-121-0/+0
| |
| * static: add my resumeFranck Cuny2021-11-121-0/+0
| |
| * build: be explicit about the image to useFranck Cuny2021-10-211-1/+1
| | | | | | | | | | If we're not explicit, we're trying to run the image tagged `latest', but there's no image with that tag.
| * static: add ssh-key from desktopFranck Cuny2021-10-021-0/+1
| |
| * build: get the proper version for taggingFranck Cuny2021-09-091-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | We were evaluating the version of the app when the rule was evaluated, while we need to get the version after we run `flyctl deploy`. Since we're tagging a release, let's also annotate the tag. Remove the `--build-arg` argument to `flyct deploy` since it's being ignored (same with `docker build`). Closes #1.
| * blog: update elisp for git/sourcegraphFranck Cuny2021-09-091-3/+12
| |
| * static: add profile pictureFranck Cuny2021-08-261-0/+0
| |
| * blog: git-link and sourcegraphFranck Cuny2021-08-241-0/+40
| |
| * blog: sort pages in reverse orderFranck Cuny2021-08-241-1/+1
| |
| * build: sleep before taggingFranck Cuny2021-08-241-0/+1
| | | | | | | | | | | | | | The last deploy was tagged v13, while the version deployed was 14. It's possible that running `fly info` too quickly after a deploy returns the incorrect version. Adding a `sleep 5` before running the command for git tag.
| * CSS: various small fixesFranck Cuny2021-08-231-2/+2
| |
| * index: drop the main headerFranck Cuny2021-08-231-2/+0
| | | | | | | | It's ugly.
| * CSS: use decoration on headers only for articlesFranck Cuny2021-08-232-6/+10
| | | | | | | | | | | | | | | | | | | | Add an element "article" to the single page template, and change the CSS to use the decoration for headers only for that kind of content. Having decoration for all headers is distracting, it's more suited for actual content. We also don't need decoration for h1, only smaller headers.
| * CSS: rename the class for the tagsFranck Cuny2021-08-231-4/+6
| |
| * CSS: makes the menu more readableFranck Cuny2021-08-232-23/+39
| | | | | | | | Move the title to the left and the menu items to the right.
| * build: tag the repo after a deployFranck Cuny2021-08-151-2/+7
| | | | | | | | | | | | | | | | If the deployment is successful, tag the repository with the version being deployed on fly.io. Don't deploy unless the repository is clean (this is done with the target `worktree-clean`).
| * blog: working with go - initial contentFranck Cuny2021-08-151-0/+264
| | | | | | | | This note captures things that are useful when working with go for me.
| * blog: add tags to firecracker notesFranck Cuny2021-08-151-1/+2
| |
| * layout: don't use header tag in listFranck Cuny2021-08-151-1/+1
| |
| * CSS: make the content more readableFranck Cuny2021-08-151-15/+24
| | | | | | | | | | | | | | | | | | | | The Roboto Slab font is hard to read (at least for me). Switch to Droid Sans and make the text a bit smaller. Change the background of the page to white (again), and change the background color for the code snippets. Add text decoration for headlines (similar to org-bullet).
| * CSS: support table of contentFranck Cuny2021-08-152-0/+19
| | | | | | | | | | If an entry has the parameter `#+toc` set to `t`, we will enable the table of content in the page.
| * CSS: use a class for the menuFranck Cuny2021-08-152-8/+7
| | | | | | | | | | We will have more use of the tag `nav` and we will need different styles for it.
| * blog: replace github with git.fcuny.netFranck Cuny2021-08-141-1/+1
| |
| * blog: add link for containerd-to-vm codeFranck Cuny2021-08-141-1/+1
| |
| * css: reduce the size of the fontFranck Cuny2021-08-141-1/+1
| |
| * css: bigger font and highlight colorsFranck Cuny2021-08-052-6/+18
| | | | | | | | | | Increase the font size and change some of the colors used for highlighting code.
| * blog: update descriptionFranck Cuny2021-08-051-1/+1
| |
| * blog: add SSH public keysFranck Cuny2021-08-052-0/+2
| |
| * blog: add humans.txtFranck Cuny2021-08-052-0/+11
| | | | | | | | See humanstxt.org for more information.
| * hugo: enable git information againFranck Cuny2021-08-051-1/+1
| | | | | | | | | | Now that we're using a more recent version of the Docker image for hugo that comes with git, we can enable again git information.
| * build: add a MakefileFranck Cuny2021-08-051-0/+29
| | | | | | | | | | Add a Makefile to take care of most common operations (build, deploy, etc).
| * build: add DockerfileFranck Cuny2021-08-051-0/+7
| | | | | | | | | | | | | | | | The Dockerfile used by fly is relying on an older version of hugo ([1]). We can use a newer version and provide our own setup, and configure with the flags we want (e.g. promote to HTTS automatically). [1] https://github.com/superfly/flyctl/blob/3eb204909fbecd5fd2b1ba4517cdbce2abd9f74a/internal/build/imgsrc/builtins/defaultbuiltins.go#L89
| * hugo: TLS by defaultFranck Cuny2021-07-191-1/+1
| |
| * github: deploy to fly.io instead of GH pagesFranck Cuny2021-06-201-17/+5
| |
| * hugo: don't enable git infoFranck Cuny2021-06-201-1/+1
| | | | | | | | | | | | | | The docker image used by fly.io to deploy a static website with hugo does not come with git, which prevents us to use the option `enableGitInfo`. This is not critical for now, so let's disable it so we can deploy.
| * fly: add configuration for fly.ioFranck Cuny2021-06-201-0/+40
| |
| * blog: update to containerd articleFranck Cuny2021-05-191-1/+1
| | | | | | | | Fix boot options
| * css: add a scroll bar if the content overflowsFranck Cuny2021-05-181-1/+1
| |
| * blog: containerd to firecrackerFranck Cuny2021-05-171-0/+567
| |
| * layout: add a navbarFranck Cuny2021-04-229-38/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | I want to differentiate blog's entries from more general notes. For this, we create two menu entries, and add a navbar at the top. The nav bar let us select between the two kind of articles: blogs or notes. For now we have a single blog entry, and no notes. The page to list entries is simplified: we use the same layout for all lists (tags, notes, blogs). The CSS is updated to support the new nav bar.
| * toml: re-configure markupFranck Cuny2021-04-131-1/+18
| |
| * css: switch to sans-serif; add tables; other tweaksFranck Cuny2021-04-131-5/+28
| |
| * css: remove extra white spaceFranck Cuny2021-04-111-1/+1
| |
| * blog: google doc failureFranck Cuny2021-04-111-0/+56
| |
| * css: change font to roboto slabFranck Cuny2021-04-111-5/+5
| |
| * taxonomy: add pages for tagsFranck Cuny2021-04-113-20/+48
| | | | | | | | | | | | | | We want to have pages that list all the articles related to a given tag. Update the configuration to add support for tags and the permalink structure.
| * layout: add date and tags to single pagesFranck Cuny2021-04-062-1/+42
| | | | | | | | | | | | | | We want to show the tags and the published/updated date for the articles. Add to the CSS the classes for these new elements.
| * css: update style for links and headersFranck Cuny2021-04-061-4/+8
| | | | | | | | Indent properly the CSS
| * css: set background color for code blockFranck Cuny2021-04-061-5/+9
| | | | | | | | Indent properly the CSS for the `pre` tag.
| * css: change the default fontFranck Cuny2021-04-061-5/+5
| |
| * layout: fix format for the dateFranck Cuny2021-04-061-1/+1
| |
| * layout: clean up empty spaceFranck Cuny2021-04-061-1/+1
| |
| * add action to publish to GH pagesFranck Cuny2021-03-071-0/+30
| | | | | | | | | | | | Add a workflow configuration to publish to GitHub pages. This is using the standard configuration from https://gohugo.io/hosting-and-deployment/hosting-on-github/
| * initial site with hugoFranck Cuny2021-03-0711-0/+180
| | | | | | | | | Start my website from scratch once more, using hugo to generate it. For now the layout is pretty simple: - an index page that will list future notes - notes should be created under the "content" directory The theme is custom and I'll try to keep this simple.
* ref(blog): remove unneeded files for the blogFranck Cuny2022-05-234-28/+1
| | | | | In a monorepo setup, the CI configuration is not used at this level of the tree, and the gitignore/envrc are not relevant.
* sign the drone configurationFranck Cuny2022-05-111-0/+6
|
* deploy: stop the flyctl agent at the endFranck Cuny2022-05-101-0/+2
| | | | | | | | | | | I ran into the following issue: ``` The agent failed to start with the following error log: 162022/05/11 02:38:11.375368 srv another instance of the agent is already running ``` I'm not sure this is the right approach, but it's a start.
* delete MakefileFranck Cuny2022-05-101-19/+0
| | | | | This is not needed anymore, I'm not running it in a container, and the build is done remotely by fly when I do a build.
* who knowsFranck Cuny2022-05-101-1/+1
|
* i don't think it will workFranck Cuny2022-05-102-9/+11
|
* another tryFranck Cuny2022-05-101-0/+21
|
* one more timeFranck Cuny2022-05-102-3/+2
|
* maybe this timeFranck Cuny2022-05-101-1/+1
|
* I'll get it right at some pointFranck Cuny2022-05-101-1/+1
|
* fix name of the branch for doneFranck Cuny2022-05-102-19/+1
| | | | Delete the workflow for GitHub actions.
* add a basic READMEFranck Cuny2022-05-101-0/+8
|
* add drone configuration and cleanup nixFranck Cuny2022-05-104-14/+54
| | | | | | | | Add a drone configuration to run the deploy on a push to the main branch. Cleanup the nix configuration to only keep support for `nix run` (which will run the hugo server).
* static: add my resume as a static pageFranck Cuny2022-05-011-0/+209
|
* config: remove the link to the feedFranck Cuny2022-05-011-8/+1
| | | | It's already in the footer.
* scripts: actually deploy to flyFranck Cuny2022-05-011-0/+2
|
* content: remove some notesFranck Cuny2022-05-014-1159/+0
| | | | They are at https://notes.fcuny.net now.
* build: slowly moving to nixFranck Cuny2022-05-015-16/+57
| | | | | | | | Add a `flake.nix' configuration to pull the required dependencies and run the server. Remove a few targets from the Makefile and move the deployment part to a script.
* layout: improve readability and remove /notesFranck Cuny2022-02-166-96/+110
| | | | | | | | | | The notes will be moved to a different site/repository, with their own style. Update the index page to make it more readable. Make the header more visible with fewer links. Add a footer, with links using SVG icons.
* note: update list of chipset for alder lakeFranck Cuny2022-01-301-2/+11
|
* build: use more recent version of hugoFranck Cuny2022-01-231-1/+1
|
* notes: remove some columns for the various CPUsFranck Cuny2022-01-231-20/+22
|
* CSS: improve readabilityFranck Cuny2022-01-231-6/+9
| | | | Using Firefox' accessibility tool as a guide.
* CSS: adjust some font sizesFranck Cuny2022-01-231-2/+2
|
* CSS: switch from class to idFranck Cuny2022-01-232-14/+14
| | | | These elements are unique on each page.
* layout: no need for a class to element 'article'Franck Cuny2022-01-233-3/+3
|
* css: TOC location based on display's sizeFranck Cuny2022-01-231-19/+82
| | | | | Depending on the size of the display, display the TOC either before the article or on the right of the article and let's make it sticky.
* layout: proper TOCFranck Cuny2022-01-231-4/+13
| | | | | | | | | | | | There's a need for two TOCs in the layout: one for when the page is on mobile; one for non mobile. When we are on mobile, we display the first TOC, before the article. When we're not on mobile, we hide that TOC and display one after the document. We restructure a bit the layout so that's it's a bit more readable too, and close tags properly.
* layout: wrap content in an "article" tagFranck Cuny2022-01-232-0/+8
|
* layout: drop the div 'main'Franck Cuny2022-01-231-6/+4
| | | | | The div 'main' is not needed, we are creating an element named 'named' in the main block.
* css: change style for tablesFranck Cuny2022-01-231-4/+8
|
* css: update color for the linksFranck Cuny2022-01-231-3/+3
| | | | Use a light blue.
* nav: use 'fcuny.net' instead of template variableFranck Cuny2022-01-211-1/+1
| | | | | Otherwise it's the name of the site, which is not what I'm looking for here.
* css: major cleanupFranck Cuny2022-01-211-76/+84
|
* nav: align the menu items to the rightFranck Cuny2022-01-211-2/+7
|
* post: change formatting for the dateFranck Cuny2022-01-211-4/+4
|
* nav: drop one item from the menuFranck Cuny2022-01-211-7/+0
|
* blog: leaving twitterFranck Cuny2022-01-151-0/+10
|
* css: more tweakingFranck Cuny2022-01-131-29/+21
|
* index: rephraseFranck Cuny2022-01-101-1/+1
|
* index: update current jobFranck Cuny2022-01-081-1/+1
|
* blog: add content about PCIeFranck Cuny2022-01-081-0/+196
|
* blog: notes about AMD and Intel CPUsFranck Cuny2021-12-291-0/+120
|
* css: change colors for some sectionsFranck Cuny2021-12-291-7/+13
|
* css: adjust line heightFranck Cuny2021-12-291-4/+1
|
* css: highlight links with a background colorFranck Cuny2021-12-291-2/+13
|
* blog: article on how to use tailscale + traefikFranck Cuny2021-12-291-0/+121
|
* config: add author informationFranck Cuny2021-12-291-0/+4
|
* layout: add a link to the RSS feed in the menuFranck Cuny2021-12-291-1/+10
| | | | | Specify the weight so that the items in the menu are listed in the order I want.
* RSS: fix the templateFranck Cuny2021-12-291-3/+5
| | | | | Generate correctly the content of the RSS feed. I only want the blog articles, not the notes.
* css: improve the color and fontsFranck Cuny2021-12-201-116/+47
|
* index: re-organize the main pageFranck Cuny2021-12-201-9/+11
| | | | Add a "contact" header with my information under it.
* menu: simplify the menuFranck Cuny2021-12-202-9/+10
|
* build: push git branches / tags after deployFranck Cuny2021-12-061-0/+2
| | | | After a successful deploy, push all the branches / tags to origin.
* CSS: drop custom fonts + colorsFranck Cuny2021-12-061-19/+22
|
* resume: updateFranck Cuny2021-11-121-0/+0
|
* static: add my resumeFranck Cuny2021-11-121-0/+0
|
* build: be explicit about the image to useFranck Cuny2021-10-211-1/+1
| | | | | If we're not explicit, we're trying to run the image tagged `latest', but there's no image with that tag.
* static: add ssh-key from desktopFranck Cuny2021-10-021-0/+1
|
* build: get the proper version for taggingFranck Cuny2021-09-091-5/+2
| | | | | | | | | | | | We were evaluating the version of the app when the rule was evaluated, while we need to get the version after we run `flyctl deploy`. Since we're tagging a release, let's also annotate the tag. Remove the `--build-arg` argument to `flyct deploy` since it's being ignored (same with `docker build`). Closes #1.
* blog: update elisp for git/sourcegraphFranck Cuny2021-09-091-3/+12
|
* static: add profile pictureFranck Cuny2021-08-261-0/+0
|
* blog: git-link and sourcegraphFranck Cuny2021-08-241-0/+40
|
* blog: sort pages in reverse orderFranck Cuny2021-08-241-1/+1
|
* build: sleep before taggingFranck Cuny2021-08-241-0/+1
| | | | | | | The last deploy was tagged v13, while the version deployed was 14. It's possible that running `fly info` too quickly after a deploy returns the incorrect version. Adding a `sleep 5` before running the command for git tag.
* CSS: various small fixesFranck Cuny2021-08-231-2/+2
|
* index: drop the main headerFranck Cuny2021-08-231-2/+0
| | | | It's ugly.
* CSS: use decoration on headers only for articlesFranck Cuny2021-08-232-6/+10
| | | | | | | | | | Add an element "article" to the single page template, and change the CSS to use the decoration for headers only for that kind of content. Having decoration for all headers is distracting, it's more suited for actual content. We also don't need decoration for h1, only smaller headers.
* CSS: rename the class for the tagsFranck Cuny2021-08-231-4/+6
|
* CSS: makes the menu more readableFranck Cuny2021-08-232-23/+39
| | | | Move the title to the left and the menu items to the right.
* build: tag the repo after a deployFranck Cuny2021-08-151-2/+7
| | | | | | | | If the deployment is successful, tag the repository with the version being deployed on fly.io. Don't deploy unless the repository is clean (this is done with the target `worktree-clean`).
* blog: working with go - initial contentFranck Cuny2021-08-151-0/+264
| | | | This note captures things that are useful when working with go for me.
* blog: add tags to firecracker notesFranck Cuny2021-08-151-1/+2
|
* layout: don't use header tag in listFranck Cuny2021-08-151-1/+1
|
* CSS: make the content more readableFranck Cuny2021-08-151-15/+24
| | | | | | | | | | The Roboto Slab font is hard to read (at least for me). Switch to Droid Sans and make the text a bit smaller. Change the background of the page to white (again), and change the background color for the code snippets. Add text decoration for headlines (similar to org-bullet).
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-12-24 03:42:07 +0000