aboutsummaryrefslogtreecommitdiffstats
path: root/docs/internals.rst
diff options
context:
space:
mode:
authorLibravatarUnit 193 <unit193@unit193.net>2021-04-22 20:23:51 -0400
committerLibravatarUnit 193 <unit193@unit193.net>2021-04-22 20:23:51 -0400
commit5fe4d85d8450575556385f20c46d67887009e245 (patch)
treee07d531240670225499657eff04a16105eb4bb5f /docs/internals.rst
parent501ee1930f5424ac00be29a7537a74e30c5d901f (diff)
parent8eeed31eb2f86ac982fa4b26f93b15828289c56d (diff)
Update upstream source from tag 'upstream/8.1.3'
Update to upstream version '8.1.3' with Debian dir ff84f28157b98ab52cbb563f4853d749beb4be60
Diffstat (limited to 'docs/internals.rst')
-rw-r--r--docs/internals.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/internals.rst b/docs/internals.rst
index 12df2b0..6b49e92 100644
--- a/docs/internals.rst
+++ b/docs/internals.rst
@@ -44,7 +44,7 @@ The Build Command
Nikola's goal is similar, deep at heart, to a Makefile. Take sources, compile them
into something, in this case a website. Instead of a Makefile, Nikola uses
-`doit <http://pydoit.org>`_
+`doit <https://pydoit.org>`_
Doit has the concept of "tasks". The 1 minute summary of tasks is that they have:
@@ -64,7 +64,7 @@ basename:name
.. sidebar:: More about tasks
If you ever want to do your own tasks, you really should read the doit
- `documentation on tasks <http://pydoit.org/tasks.html>`_
+ `documentation on tasks <https://pydoit.org/tasks.html>`_
So, what Nikola does, when you use the build command, is to read the
configuration ``conf.py`` from the current folder, instantiate