dongdigua/mirror.dongdigua.github.io
1
0
Fork 0
mirror of https://github.com/dongdigua/dongdigua.github.io synced 2024-11-24 04:03:11 +08:00
Code Issues Packages Projects Releases Wiki Activity
327b34da80
mirror.dongdigua.github.io/org/new_blog_arch.org
dongdigua 3ca77af7d7 damn_tm a few change, collections 
wayland: fix env variable with shell wrapper
collect:
- add fun tag
- [RM] coder.rs
too many article not unuseful to me
- [RM] Light & Truth
- [YT/RM] leagacy Rust AES
- [EXPAND] Alynx Zhou
- [EXPAND] 写代码的西瓜
- explain X11
2022-12-03 09:54:24 +08:00

1.0 KiB
Raw Blame History

New Blog Architecture

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.

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

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

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

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!