-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.xml
50 lines (42 loc) · 2.83 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Dennis's Grocery</title>
<link>https://dennisxie.github.io/</link>
<description>Recent content on Dennis's Grocery</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Fri, 08 Jul 2022 13:01:16 +0800</lastBuildDate><atom:link href="https://dennisxie.github.io/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Create Python Bindings with Cython</title>
<link>https://dennisxie.github.io/post/tech/python/python_bindings_with_cython/</link>
<pubDate>Fri, 08 Jul 2022 13:01:16 +0800</pubDate>
<guid>https://dennisxie.github.io/post/tech/python/python_bindings_with_cython/</guid>
<description>The basic usages of Cython to create Python bindings</description>
</item>
<item>
<title>Multi-Stage Builds of Docker</title>
<link>https://dennisxie.github.io/post/tech/docker/multi_stage_build/</link>
<pubDate>Tue, 21 Jun 2022 16:32:52 +0800</pubDate>
<guid>https://dennisxie.github.io/post/tech/docker/multi_stage_build/</guid>
<description>Background What can we do if we should merge several Docker images to a single Docker image for some reason?
Solution We can use multi-stage builds of Docker.
Multi-stage builds Problem solved by multi-stage builds It&rsquo;s very common to have different images for building, testing, and production. Different images contain different tools. Building images may contain building tools such as GCC, Gradle, and so on. Testing images may contain perf tools, analysis tools, and so on.</description>
</item>
<item>
<title>Hugo Integrity Problem</title>
<link>https://dennisxie.github.io/post/problems/hugo_integrity_problem/</link>
<pubDate>Thu, 09 Jun 2022 12:39:44 +0800</pubDate>
<guid>https://dennisxie.github.io/post/problems/hugo_integrity_problem/</guid>
<description>The problem of integrity When you maintain your Hugo project both on Windows and Linux/macOS, you may get this error. The problem is caused by the default EOL character. The different EOL characters in the file will produce different SHA-256 hash codes. So what needs to do is to force the files to have LF or CRLF at the end of the line.
Solution We can use git to ensure this.</description>
</item>
<item>
<title>Testpage</title>
<link>https://dennisxie.github.io/post/testpage/</link>
<pubDate>Wed, 08 Jun 2022 17:40:14 +0800</pubDate>
<guid>https://dennisxie.github.io/post/testpage/</guid>
<description>First Test Blog This is my first test blog page</description>
</item>
</channel>
</rss>