| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
It's ugly.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Move the title to the left and the menu items to the right.
|
|
|
|
|
|
|
|
| |
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`).
|
|
|
|
| |
This note captures things that are useful when working with go for me.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
| |
If an entry has the parameter `#+toc` set to `t`, we will enable the
table of content in the page.
|
|
|
|
|
| |
We will have more use of the tag `nav` and we will need different styles
for it.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Increase the font size and change some of the colors used for
highlighting code.
|
| |
|
| |
|
|
|
|
| |
See humanstxt.org for more information.
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Add a Makefile to take care of most common operations (build, deploy,
etc).
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Fix boot options
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
We want to show the tags and the published/updated date for the
articles.
Add to the CSS the classes for these new elements.
|
|
|
|
| |
Indent properly the CSS
|
|
|
|
| |
Indent properly the CSS for the `pre` tag.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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/
|
|
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.
|