diff --git a/feed.xml b/feed.xml index fc7aee7..5971d14 100644 --- a/feed.xml +++ b/feed.xml @@ -6,7 +6,7 @@ Emacs webfeeder.el https://dongdigua.github.io -六, 03 12月 2022 22:45:02 +0800 +日, 04 12月 2022 13:34:39 +0800 狗日的腾讯会议 @@ -99,62 +99,87 @@ 五, 02 12月 2022 08:00:00 +0800 - New Blog Architecture + New(and Newer) Blog Architecture + +
+

1. Branch

+

I've never fully learnt git before(only search for garbage when meeted with problem), so I recently read ProGit.

And I have some good ideas on my repo architecture: I should make use of branch, obviously.

+
-
-

1. Idea is:

-
+
+

1.1. Idea is:

+

seperate the source file(org) and the generated files(html, feed.xml)

so I can

-
-

1.1. clearly look at the diff

+
+

1.1.1. clearly look at the diff

-
-

1.2. delete the generated files if I want

-
+
+

1.1.2. delete the generated files if I want

+

because those static files are really unecessary and takes much space

-
-

2. So what

-
-
-

2.1. use filter-branch to remove the huge feed.xml in the full history

+

1.2. So what

+
-
-

2.2. ignore the generated files in the source repo

+
+

1.2.1. use filter-branch to remove the huge feed.xml in the full history

-
-

2.3. merge the source repo into site repo when I think it's ok

-
+
+

1.2.2. ignore the generated files in the source repo

+
+
+

1.2.3. merge the source repo into site repo when I think it's ok

+

don't remove the source(org) in the site repo,

if build in main and checkout to site, those html will be overwritten

+
+

1.2.4. and I will use the same stratagy on my YW sub-website if there's no problem

+
+

+I'm testing using CI on YW sub-site before deploying on this precious repo

+
+
+
+
-

2.4. and I will use the same stratagy on my YW sub-website if there's no problem

+

1.3. Need Advice

+
+

+ I'm really new to do this. If you have a better idea, or this is somehow useful to you,

contact me, please!

+
-

3. Need Advice

-
+

2. CI

+

-I'm really new to do this.

-If you have a better idea, or this is somehow useful to you,

contact me, please!

+I previously thought of using CI to deploy blog, but I thought it too difficult, so just keep status quo.

+But for many times I want to build a NixOS with wayland and lots of other big util(such as clang and metasploit),

+if I build it on my machine, it will take up too many spaces and make no use except for building iso.

+So it urged me to use a CI, after some trying, I found it not difficult and in fact, very useful!

+ +

+I can have my huge feed.xml(which contains each of my post) dynamically generated by CI, it will save lots of spaces!

+I will bundle my entire history mess and put it on release, like previous big change,

+then use the Nuclear Option filter-branch to delete those generated big files.

]]> @@ -770,82 +795,6 @@ var: plz-curl-default-args

https://dongdigua.github.io/matrix.html 四, 22 9月 2022 08:00:00 +0800 - - Build a Minimal NixOS LiveCD with swaywm - - - - -
-

1. problem & solution

-
-
-
-

1.1. unable to drop root

-
-

-donot run under root

-
-
-
-

1.2. in normal user, libseat permission deniened

-
-

-add user in video group

-login as user, not root

-
-
-
-

1.3. egl error

-
-

-enable 3D acceleration in VirtualBox

-
-
-
-

1.4. config files from outside

-
-

- irc-nixiso.png

-but it is copied using xoriso to /iso/

-so I need to write a systemd service to automagically sync it at boot

-
-
-
-

1.5. cleanup builds

-
-

- /nix/store/ takes too much space after build

-
- 
unlink result
-nix-store 
-
-
-

-and there're a few tools for visualising disk size:

https://nixos.wiki/wiki/Cleaning_the_nix_store

-
-
-
- -
-

2. reference

-
-
-
-

2.1. nixos without systemd?

-
-
-

2.2. an example config

-
-
-

2.3. Xe: Super Bootable 64

-
-
-
]]> - https://dongdigua.github.io/nixos.html - https://dongdigua.github.io/nixos.html - 六, 17 9月 2022 08:00:00 +0800 - 庄主其人 @@ -1913,7 +1862,7 @@ CPU, IC, ARM

-

linus-on-TED.png

+

linus-on-TED.png

diff --git a/gmi/gopher_collections.gmi b/gmi/gopher_collections.gmi index 8741bae..30224b3 100644 --- a/gmi/gopher_collections.gmi +++ b/gmi/gopher_collections.gmi @@ -42,3 +42,4 @@ Gemcast, Esperanto => gemini://gemini.cyberbot.space/ + cyberbot undergoes frequent maintenance => gemini://gemini.cyberbot.space/smolzine/ ++ smolzine +=> gemini://tilde.team/~kiedtl/k1ss/ + Kiss Linux mirror diff --git a/internet_collections.html b/internet_collections.html index 2b1e784..49d9f6c 100644 --- a/internet_collections.html +++ b/internet_collections.html @@ -3,7 +3,7 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - + Internet Collections @@ -430,7 +430,7 @@ CPU, IC, ARM
-

linus-on-TED.png
+

linus-on-TED.png

@@ -1404,7 +1404,7 @@ worth reading

Author: dongdigua

Date: 2022-06-05 日 00:00

-

Build: 2022-12-03 六 22:45

+

Build: 2022-12-04 日 13:34

LICENCE: CC BY-NC-SA

If you have any idea, please contact me! I may add your comment

diff --git a/new_blog_arch.html b/new_blog_arch.html index 98575b2..14f7afb 100644 --- a/new_blog_arch.html +++ b/new_blog_arch.html @@ -3,10 +3,10 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - + -New Blog Architecture +New(and Newer) Blog Architecture @@ -202,48 +202,58 @@ | HOME
-

New Blog Architecture

+

New(and Newer) Blog Architecture

+ +
+

1. Branch

+

I've never fully learnt git before(only search for garbage when meeted with problem), so I recently read ProGit.
And I have some good ideas on my repo architecture: I should make use of branch, obviously.

+
-
-

1. Idea is:

-
+
+

1.1. Idea is:

+

seperate the source file(org) and the generated files(html, feed.xml)
so I can

-
-

1.1. clearly look at the diff

+
+

1.1.1. clearly look at the diff

-
-

1.2. delete the generated files if I want

-
+
+

1.1.2. delete the generated files if I want

+

because those static files are really unecessary and takes much space

@@ -251,37 +261,60 @@ because those static files are really unecessary and takes much space
-
-

2. So what

-
-
-

2.1. use filter-branch to remove the huge feed.xml in the full history

+

1.2. So what

+
-
-

2.2. ignore the generated files in the source repo

+
+

1.2.1. use filter-branch to remove the huge feed.xml in the full history

-
-

2.3. merge the source repo into site repo when I think it's ok

-
+
+

1.2.2. ignore the generated files in the source repo

+
+
+

1.2.3. merge the source repo into site repo when I think it's ok

+

don't remove the source(org) in the site repo,
if build in main and checkout to site, those html will be overwritten

+
+

1.2.4. and I will use the same stratagy on my YW sub-website if there's no problem

+
+

+I'm testing using CI on YW sub-site before deploying on this precious repo
+

+
+
+
+
-

2.4. and I will use the same stratagy on my YW sub-website if there's no problem

+

1.3. Need Advice

+
+

+I'm really new to do this. If you have a better idea, or this is somehow useful to you,
+contact me, please!
+

+
-

3. Need Advice

-
+

2. CI

+

-I'm really new to do this.
-If you have a better idea, or this is somehow useful to you,
-contact me, please!
+I previously thought of using CI to deploy blog, but I thought it too difficult, so just keep status quo.
+But for many times I want to build a NixOS with wayland and lots of other big util(such as clang and metasploit),
+if I build it on my machine, it will take up too many spaces and make no use except for building iso.
+So it urged me to use a CI, after some trying, I found it not difficult and in fact, very useful!
+

+ +

+I can have my huge feed.xml(which contains each of my post) dynamically generated by CI, it will save lots of spaces!
+I will bundle my entire history mess and put it on release, like previous big change,
+then use the Nuclear Option filter-branch to delete those generated big files.

@@ -290,7 +323,7 @@ If you have a better idea, or this is somehow useful to you,

Author: dongdigua

Date: 2022-11-20 日 00:00

-

Build: 2022-12-03 六 12:02

+

Build: 2022-12-04 日 13:34

LICENCE: CC BY-NC-SA

If you have any idea, please contact me! I may add your comment

diff --git a/org/Makefile b/org/Makefile index 49b3163..375189a 100644 --- a/org/Makefile +++ b/org/Makefile @@ -11,6 +11,6 @@ html: @echo "DONE" clean: - rm ~/.org-timestamps/org-pages.cache + - rm ~/.org-timestamps/org-pages.cache $(TARGET) | xargs -I {} rm {} rm ../feed.xml* diff --git a/org/internet_collections.org b/org/internet_collections.org index 1968381..c3be5ad 100644 --- a/org/internet_collections.org +++ b/org/internet_collections.org @@ -77,7 +77,7 @@ CPU, IC, ARM 出国 *** [[http://jujuba.me/posts/program-analysis-via-llvm-pass.html][LLVM Pass来实现简化版taint analysis]] *** [[http://jujuba.me/posts/taste-of-code.html][代码的taste]] -#+ATTR_HTML: :width 256px +#+ATTR_HTML: :width 400px [[http://jujuba.me/imgs/linus-on-TED.png]] ** [[https://cireu.github.io/2019/09/17/lisp-setf/][NIL: setf 中「f」的本意]] ** [[https://www.cnblogs.com/zjjws/p/13346020.html][第 N 个质数]] :c:algorithm: diff --git a/org/new_blog_arch.org b/org/new_blog_arch.org index 59b11a1..95c54d5 100644 --- a/org/new_blog_arch.org +++ b/org/new_blog_arch.org @@ -1,26 +1,37 @@ -#+TITLE: New Blog Architecture +#+TITLE: New(and Newer) Blog Architecture #+DESCRIPTION: It's time #+DATE: <2022-11-20 Sun> +* Branch I've never fully learnt git before(only search for garbage when meeted with problem), so I recently read [[https://git-scm.com/book][ProGit]]. And I have some good ideas on my repo architecture: I should make use of branch, obviously. -* Idea is: +** Idea is: seperate the source file(org) and the generated files(html, feed.xml) so I can -** clearly look at the diff -** delete the generated files if I want +*** clearly look at the diff +*** delete the generated files if I want because those static files are really unecessary and takes much space -* So what -** use =filter-branch= to remove the huge =feed.xml= in the full history -** ignore the generated files in the source repo -** merge the source repo into site repo when I think it's ok +** So what +*** use =filter-branch= to remove the huge =feed.xml= in the full history +*** ignore the generated files in the source repo +*** merge the source repo into site repo when I think it's ok don't remove the source(org) in the site repo, if build in main and checkout to site, those html will be overwritten -** and I will use the same stratagy on my YW sub-website if there's no problem +*** +and I will use the same stratagy on my YW sub-website if there's no problem+ +I'm testing using CI on YW sub-site before deploying on this precious repo -* Need Advice -I'm really new to do this. -If you have a better idea, or this is somehow useful to you, -*contact me, please!* +** Need Advice ++I'm really new to do this. If you have a better idea, or this is somehow useful to you,+ ++*contact me, please!*+ + +* CI +I previously thought of using CI to deploy blog, but I /thought/ it too difficult, so just keep status quo. +But for many times I want to build a [[https://github.com/dongdigua/configs/blob/main/configuration.nix][NixOS]] with [[https://donngdigua.github.io/wayland][wayland]] and lots of other big util(such as clang and metasploit), +if I build it on my machine, it will take up too many spaces and make no use except for building iso. +So it urged me to use a CI, after some [[https://t.bilibili.com/735422465675624481][trying]], I found it not difficult and in fact, very useful! + +I can have my huge feed.xml(which contains each of my post) dynamically generated by CI, it will save lots of spaces! +I will [[https://git-scm.com/book/en/v2/Git-Tools-Bundling][bundle]] my entire history mess and put it on release, like previous big change, +then use the Nuclear Option =filter-branch= to delete those generated big files. diff --git a/posts.md b/posts.md index 535d3d1..b83991f 100644 --- a/posts.md +++ b/posts.md @@ -2,8 +2,8 @@ ### Posts (sorted by time) - [狗日的腾讯会议](damn_tencent_meeting)
上网课有感而发 -- [New Blog Repo Architecture](new_blog_arch)
-please contct me if you have a better idea +- [New Blog Architecture](new_blog_arch)
+mess -> branch -> CI - [记一次帮老师修U盘](recover_udisk)
- [Clear Kernel Compile Error? Fix It](clear_kernel_compile_fix)
- [Gentoo LLVM\_TARGETS not Working?](gentoo_llvm_targets)