| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
Change-Id: I0911c07d5ab0e17a09e587ba4507d0202f6c7ff3
Reviewed-on: https://cl.fcuny.net/c/world/+/364
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
In a monorepo setup, the CI configuration is not used at this level of
the tree, and the gitignore/envrc are not relevant.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Delete the workflow for GitHub actions.
|
| |
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
| |
It's already in the footer.
|
| |
|
|
|
|
| |
They are at https://notes.fcuny.net now.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
Using Firefox' accessibility tool as a guide.
|
| |
|
|
|
|
| |
These elements are unique on each page.
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
The div 'main' is not needed, we are creating an element named 'named'
in the main block.
|
| |
|
|
|
|
| |
Use a light blue.
|
|
|
|
|
| |
Otherwise it's the name of the site, which is not what I'm looking for
here.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Specify the weight so that the items in the menu are listed in the order
I want.
|
|
|
|
|
| |
Generate correctly the content of the RSS feed. I only want the blog
articles, not the notes.
|
| |
|
|
|
|
| |
Add a "contact" header with my information under it.
|
| |
|
|
|
|
| |
After a successful deploy, push all the branches / tags to origin.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
If we're not explicit, we're trying to run the image tagged `latest',
but there's no image with that tag.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|