change themes to nederburg
This commit is contained in:
1
public/post/page/1/index.xml/index.html
Normal file
1
public/post/page/1/index.xml/index.html
Normal file
@@ -0,0 +1 @@
|
||||
<!DOCTYPE html><html><head><title>https://h.cowbay.org/post/</title><link rel="canonical" href="https://h.cowbay.org/post/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=https://h.cowbay.org/post/" /></head></html>
|
||||
File diff suppressed because it is too large
Load Diff
170
public/post/page/2/index.xml
Normal file
170
public/post/page/2/index.xml
Normal file
@@ -0,0 +1,170 @@
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Posts - MCの飄狂山莊㊣</title>
|
||||
<link>https://h.cowbay.org/post/</link>
|
||||
<description>Recent content in Posts on MCの飄狂山莊㊣</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<lastBuildDate>Fri, 04 Oct 2019 14:12:15 +0800</lastBuildDate>
|
||||
|
||||
<atom:link href="https://h.cowbay.org/post/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
<item>
|
||||
<title>[筆記] 在edgerouter上用wireguard 建立site to site VPN / Site to Site Vpn Using Wireguard in Two Edgerouters</title>
|
||||
<link>https://h.cowbay.org/post/site-to-site-vpn-using-wireguard-in-two-edgerouters/</link>
|
||||
<pubDate>Tue, 06 Aug 2019 17:14:17 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/site-to-site-vpn-using-wireguard-in-two-edgerouters/</guid>
|
||||
<description><p>之前總部和分公司之間 是用buffalo 的小AP 灌 openwrt</p>
|
||||
|
||||
<p>然後用strongswan 來打 IPSEC site to site VPN</p>
|
||||
|
||||
<p>config 看起來不是很難 (只是看起來)</p>
|
||||
|
||||
<p>但是實際上已經找不到當初的文件</p>
|
||||
|
||||
<p>所以要維護很困難(光那些RSA KEY 就不知道為何、如何產生)</p>
|
||||
|
||||
<p>後來採購了兩台edgerouter X 做測試</p>
|
||||
|
||||
<p>也用openvpn 成功的建立了 site to site VPN</p>
|
||||
|
||||
<p>本來想說 openvpn 已經夠簡單了</p>
|
||||
|
||||
<p>今天看到文章說用wireguard 可以更簡單</p>
|
||||
|
||||
<p>於是研究了一下，發現還真的很簡單！</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 為了保存log 用script 指令執行ansible / Another Way to Keep Ansible Log using script command</title>
|
||||
<link>https://h.cowbay.org/post/another-way-to-keep-ansible-log/</link>
|
||||
<pubDate>Mon, 05 Aug 2019 16:24:40 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/another-way-to-keep-ansible-log/</guid>
|
||||
<description><p>之前為了能夠在執行完 ansible playbook 後，能有個log 可以看</p>
|
||||
|
||||
<p>所以在每次執行的時候，都要加入 tee 的指令</p>
|
||||
|
||||
<p>像是</p>
|
||||
|
||||
<pre><code>ANSIBLE_CONFIG=/home/D/ansiblecontrol/ansible.cfg /usr/local/bin/ansible-playbook /home/D/ansiblecontrol/playbook.user_client.yml --vault-password-file=/home/D/ansiblecontrol/vault.passwd -i /home/D/ansiblecontrol/inventory/production -f1 --limit tyuserclients |tee /tmp/tyuserclients.log
|
||||
</code></pre>
|
||||
|
||||
<p>一直都是放在crontab 裡面執行，也就沒有去管他</p>
|
||||
|
||||
<p>反正也沒有人關心結果怎樣 (攤手</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 用pxe 安裝系統，完成後送出郵件通知 / send mail notification after pxe install</title>
|
||||
<link>https://h.cowbay.org/post/send-mail-to-notify-after-pxe-install/</link>
|
||||
<pubDate>Wed, 31 Jul 2019 11:06:33 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/send-mail-to-notify-after-pxe-install/</guid>
|
||||
<description><p>最近有個任務，需要大量安裝client</p>
|
||||
|
||||
<p>想用PXE來處理，只要user開機按F12(acer 桌機) 選擇PXE Boot</p>
|
||||
|
||||
<p>然後選擇OS版本，就可以自動進行安裝</p>
|
||||
|
||||
<p>安裝完成後，會自動重新開機，接著就用ansible來做user環境設定</p>
|
||||
|
||||
<p>PXE的部份本來是沒有什麼問題，自動安裝系統的部份都做好了</p>
|
||||
|
||||
<p>可是因為這次的量比較多，想說讓每一台在完成PXE安裝後的第一次重開機</p>
|
||||
|
||||
<p>就送出一封郵件來通知我，說已經完成安裝，可以執行ansible 了</p>
|
||||
|
||||
<p>看似很簡單的一件事情，卻搞了我兩天&hellip;.</p></description>
|
||||
</item><item>
|
||||
<title>[ansible] 用 ip 位置判斷是否要執行task /ansible run task depends on ipaddr</title>
|
||||
<link>https://h.cowbay.org/post/ansible-run-task-depends-on-ipaddr/</link>
|
||||
<pubDate>Tue, 23 Jul 2019 15:06:37 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/ansible-run-task-depends-on-ipaddr/</guid>
|
||||
<description><p>因為工作上的需要，要修改client端的 /etc/environment 檔案</p>
|
||||
|
||||
<p>在有權限使用proxy 服務的user的環境中，加入proxy 的設定</p>
|
||||
|
||||
<p>原本的清單中，有host/user/ip 這幾個值可以拿來判斷</p>
|
||||
|
||||
<p>proxy server 那邊是採用ip 來控制，所以這邊也跟著用 ip 來判斷要不要修改 /etc/environment</p></description>
|
||||
</item><item>
|
||||
<title>[ansible] 引用事先定義好的yaml檔裡面的變數 - Ansible Selectattr From List in Dictionary file</title>
|
||||
<link>https://h.cowbay.org/post/ansible-selectattr-from-list-in-dictionary/</link>
|
||||
<pubDate>Mon, 01 Jul 2019 09:06:12 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/ansible-selectattr-from-list-in-dictionary/</guid>
|
||||
<description><p>在ansible中，關於如何引用自定義的變數，一直讓我很頭疼</p>
|
||||
|
||||
<p>尤其是有牽涉到從外部導入yaml檔案時，更是常常讓我不知道到底該怎麼抓出想要的變數</p>
|
||||
|
||||
<p>這次還是用selectattr 來處理，希望下次能夠記得&hellip;</p></description>
|
||||
</item><item>
|
||||
<title>linux底下遠端遙控&管理的好用系統 Meshcentral / Remote Management & control system Meshcentral</title>
|
||||
<link>https://h.cowbay.org/post/remote-management-system-meshcentral/</link>
|
||||
<pubDate>Thu, 20 Jun 2019 11:03:12 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/remote-management-system-meshcentral/</guid>
|
||||
<description><p>之前在LAN/windows環境下，一直都是用ultravnc/winvnc/tigervnc之類的VNC軟體</p>
|
||||
|
||||
<p>但是如果要過 internet ，就會碰到各種開port的問題</p>
|
||||
|
||||
<p>在這種環境下，就有了當時 teamviewer 的橫空出世</p>
|
||||
|
||||
<p>解決了開PORT的問題，讓被控端(通常是資訊技術相對弱勢，需要接受幫助的一方)不需要懂太多</p>
|
||||
|
||||
<p>只要下載teamviewer被控端，開啟後報ID 給協助者就好了</p></description>
|
||||
</item><item>
|
||||
<title>Install Asus 10G NIC XG-C100C in Proxmox</title>
|
||||
<link>https://h.cowbay.org/post/install-asus-10g-nic-in-proxmox/</link>
|
||||
<pubDate>Mon, 17 Jun 2019 13:20:57 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/install-asus-10g-nic-in-proxmox/</guid>
|
||||
<description><p>前幾天接的一個case</p>
|
||||
|
||||
<p>因為費用的關係，所以沒有考慮用傳統定義上的伺服器(DELL R640)</p>
|
||||
|
||||
<p>改採用比較高階一點的洋垃圾，規格大概是 Intel E5-2680V2 x2 + 64G RAM + 128G SSD x2 (OS) + 960G SSD x4 (raid 10 , zfs)</p>
|
||||
|
||||
<p>storage 選擇QNAP NAS TS-932X + 960G SSD x 4 (raid 10 , NFS) + QNAP 10G Switch QSW-1280C-8C</p>
|
||||
|
||||
<p>既然storage這邊選用了10G的機種，伺服器上當然也要增加10G網卡</p>
|
||||
|
||||
<p>一樣，成本考量，就不用INTEL 了，買了這張 ASUS 10G 網卡</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 修改 docker 容器內的時區 - Change Timezone in Docker</title>
|
||||
<link>https://h.cowbay.org/post/change-timezone-in-docker/</link>
|
||||
<pubDate>Tue, 21 May 2019 17:25:15 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/change-timezone-in-docker/</guid>
|
||||
<description><p>最近一直在玩一些docker，不過老是會碰到歪果扔寫的東西，時區都不一致</p>
|
||||
|
||||
<p>有的用 UTC，有的用localtime，就是沒碰到用 Asia/Taipei 的&hellip;.</p></description>
|
||||
</item><item>
|
||||
<title>Transfer File Content Using Xclip in Terminal</title>
|
||||
<link>https://h.cowbay.org/post/transfer-file-content-using-xclip-in-terminal/</link>
|
||||
<pubDate>Fri, 17 May 2019 12:18:54 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/transfer-file-content-using-xclip-in-terminal/</guid>
|
||||
<description><p>工作上常會需要用ssh登入遠端主機檢查LOG，有必要的時候，還要把log複製回本機來處理。</p>
|
||||
|
||||
<p>以前都是傻傻的用 scp 傳檔案</p>
|
||||
|
||||
<p>之前就記得有這個xclip/xsel 可以用，但是一直沒有弄清楚怎麼執行</p>
|
||||
|
||||
<p>早上研究了一下，順便做個筆記。</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] inxi 蒐集詳盡的硬體資訊 / inxi Collect Detail Hardware Info</title>
|
||||
<link>https://h.cowbay.org/post/inx-collect-detail-hardware-info/</link>
|
||||
<pubDate>Tue, 23 Apr 2019 15:28:56 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/inx-collect-detail-hardware-info/</guid>
|
||||
<description><p>最近因為一直碰到硬碟故障的問題，算起來那一批同時購買的5X顆 seagate 2T硬碟，已經有一半以上故障返修了&hellip;.</p>
|
||||
|
||||
<p>然後又因為一直沒有添購新的硬碟，只能用這些快過保/已過保的撐著</p>
|
||||
|
||||
<p>所以最近不斷的在更換機器內的硬碟，而且還沒有熱插拔！</p>
|
||||
|
||||
<p>也導致原本負責處理盤點資產的同事困擾，因為跟手邊的紀錄已經對不起來了</p>
|
||||
|
||||
<p>然後就變成要對資產的時候，需要一台一台登入，然後去下不同的指令，取得想要的硬體資訊，超級麻煩的！</p></description>
|
||||
</item>
|
||||
</channel>
|
||||
</rss>
|
||||
File diff suppressed because it is too large
Load Diff
131
public/post/page/3/index.xml
Normal file
131
public/post/page/3/index.xml
Normal file
@@ -0,0 +1,131 @@
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Posts - MCの飄狂山莊㊣</title>
|
||||
<link>https://h.cowbay.org/post/</link>
|
||||
<description>Recent content in Posts on MCの飄狂山莊㊣</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<lastBuildDate>Fri, 04 Oct 2019 14:12:15 +0800</lastBuildDate>
|
||||
|
||||
<atom:link href="https://h.cowbay.org/post/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
<item>
|
||||
<title>[筆記] 紀錄所有下過的指令、時間 / Log All commands with timestamp</title>
|
||||
<link>https://h.cowbay.org/post/log-all-bash-commands/</link>
|
||||
<pubDate>Tue, 23 Apr 2019 15:08:36 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/log-all-bash-commands/</guid>
|
||||
<description><p>今天發生一件有點詭異的事情，本來應該要經過某個指令才會產生的檔案</p>
|
||||
|
||||
<p>居然不知為何自己產生了，在我記憶中沒有去執行過那個指令</p>
|
||||
|
||||
<p>翻了一下 bash_history ，裡面也只有下過哪些指令，沒有紀錄時間，完全沒有參考價值(攤手)</p>
|
||||
|
||||
<p>所以翻了一下網路，至少把這兩台主要跑ansible的機器的log功能補上紀錄所有指令以及時間的部份</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 解決無法建立zpool 的錯誤 / Fix Zpool Device Busy Using dmsetup</title>
|
||||
<link>https://h.cowbay.org/post/fix-zpool-device-busy-using-dmsetup/</link>
|
||||
<pubDate>Mon, 01 Apr 2019 15:56:27 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/fix-zpool-device-busy-using-dmsetup/</guid>
|
||||
<description><p>今天把其中一台proxmox 加上10G 光纖網卡，準備和另一台proxmox 組成10G 環境進行測試</p>
|
||||
|
||||
<p>想說把本機的zpool 拆掉，重新建立一個raid0 的空間來做clone/migrate</p>
|
||||
|
||||
<p>可是一直出現device busy的錯誤訊息</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 用rsync 移轉 centos 6.2的老機器 Transfer Cent6.2 using rsync</title>
|
||||
<link>https://h.cowbay.org/post/transfer-cent62-using-rsync/</link>
|
||||
<pubDate>Wed, 27 Mar 2019 17:44:49 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/transfer-cent62-using-rsync/</guid>
|
||||
<description><p>公司的一台老伺服器空間不足了，要執行指令都會中斷，所以想要擴充空間。</p>
|
||||
|
||||
<p>看起來不難搞，事實上&hellip;..</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 測試mail server 的SSL憑證的指令 Command to test mailserver SSL</title>
|
||||
<link>https://h.cowbay.org/post/command_to_test_main_ssl/</link>
|
||||
<pubDate>Wed, 20 Mar 2019 11:42:47 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/command_to_test_main_ssl/</guid>
|
||||
<description><p>今天老闆出國，發slack說手機不能寄信，看了一下，似乎是因為用GMAIL的APP來收信</p>
|
||||
|
||||
<p>然後google 不知道跟人家改了什麼，結果不接受原本的認證了&hellip; WTF &hellip;.</p>
|
||||
|
||||
<p>然後，這問題應該很久了，結果現在才在講 &hellip;.</p></description>
|
||||
</item><item>
|
||||
<title>Install Timeshift on Ubuntu1804</title>
|
||||
<link>https://h.cowbay.org/post/install-timeshift-on-ubuntu1804/</link>
|
||||
<pubDate>Mon, 11 Mar 2019 14:02:30 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/install-timeshift-on-ubuntu1804/</guid>
|
||||
<description><p>最近要開始測試client安裝 ubuntu 18.04 的 ansible playbook</p>
|
||||
|
||||
<p>因為要不斷的修正，所以想到一直有在自己電腦上執行的timeshift這個軟體</p>
|
||||
|
||||
<p>可以很簡單快速的備份、恢復系統狀態</p>
|
||||
|
||||
<p>可是不知道為什麼，在ubuntu 18.04 上安裝就是會發生錯誤&hellip;.</p></description>
|
||||
</item><item>
|
||||
<title>用DELL 6 i/R 建立RAID，並在上面安裝ubuntu 18.04 </title>
|
||||
<link>https://h.cowbay.org/post/install-ubuntu1804-on-dell-6ir-raid-controller/</link>
|
||||
<pubDate>Wed, 16 Jan 2019 16:17:05 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/install-ubuntu1804-on-dell-6ir-raid-controller/</guid>
|
||||
<description><p>買了一張 DELL 6/iR 低階的raid 卡</p>
|
||||
|
||||
<p>來測試把系統裝在硬體做的RAID上，結果沒想到居然不能開機&hellip;</p></description>
|
||||
</item><item>
|
||||
<title>Ubuntu 1804 Install Root on Raid</title>
|
||||
<link>https://h.cowbay.org/post/ubuntu-1804-install-root-on-raid/</link>
|
||||
<pubDate>Wed, 16 Jan 2019 09:58:50 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/ubuntu-1804-install-root-on-raid/</guid>
|
||||
<description><p>最近在弄一台機器，想要把ubuntu 18.04 安裝在software raid上</p>
|
||||
|
||||
<p>因為新開的機器大部分都是在proxmox上，所以很少碰實體機器了</p>
|
||||
|
||||
<p>結果在安裝過程中，做raid碰到一些問題，來紀錄一下</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] Freenas Smartd 啟動失敗 Smartd Failed to Start in Freenas</title>
|
||||
<link>https://h.cowbay.org/post/smartd-failed-to-start-in-freenas/</link>
|
||||
<pubDate>Thu, 13 Dec 2018 17:40:20 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/smartd-failed-to-start-in-freenas/</guid>
|
||||
<description><p>這兩天在弄兩台Freenas ，準備當作Proxmox 的Storage &amp; Server Backup</p>
|
||||
|
||||
<p>因為伺服器的限制，只能接六個SATA，我接了六個2T的硬碟做raid10</p>
|
||||
|
||||
<p>然後把Freenas 安裝在隨身碟上</p>
|
||||
|
||||
<p>不過會一直出現Smartd failed to start 的錯誤訊息</p></description>
|
||||
</item><item>
|
||||
<title>[碎念] mdadm 超級慢的rebuild 速度 Incredibly Slow mdadm Rebuild</title>
|
||||
<link>https://h.cowbay.org/post/incredibly-slow-mdadm-rebuild/</link>
|
||||
<pubDate>Wed, 12 Dec 2018 11:10:22 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/incredibly-slow-mdadm-rebuild/</guid>
|
||||
<description><p>最近在做一台老機器的P2V</p>
|
||||
|
||||
<p>偏偏user說不能關機，所以我用dd + ssh 做線上移轉</p>
|
||||
|
||||
<p>這部份有空再來寫</p>
|
||||
|
||||
<p>只是因為原來的設定有用mdadm 做raid1</p>
|
||||
|
||||
<p>這部份導致移轉過去proxmox 後，會出現raid degrade 導致無法正常開機</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 建立一個帶著走的 VIM 環境 Creating portable Vim environment</title>
|
||||
<link>https://h.cowbay.org/post/create-portable-vim-environment/</link>
|
||||
<pubDate>Fri, 07 Dec 2018 15:19:47 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/create-portable-vim-environment/</guid>
|
||||
<description><p>因為工作的關係，現在很多時間都花在VIM的操作上</p>
|
||||
|
||||
<p>所以之前花了滿多時間，調整出一個適合自己的VIM環境</p>
|
||||
|
||||
<p>原本的作法是把這個設定好的環境，丟到自己建立的gitea 上面</p>
|
||||
|
||||
<p>然後每到一台新的機器，就要去clone 下來</p></description>
|
||||
</item>
|
||||
</channel>
|
||||
</rss>
|
||||
File diff suppressed because it is too large
Load Diff
218
public/post/page/4/index.xml
Normal file
218
public/post/page/4/index.xml
Normal file
@@ -0,0 +1,218 @@
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Posts - MCの飄狂山莊㊣</title>
|
||||
<link>https://h.cowbay.org/post/</link>
|
||||
<description>Recent content in Posts on MCの飄狂山莊㊣</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<lastBuildDate>Fri, 04 Oct 2019 14:12:15 +0800</lastBuildDate>
|
||||
|
||||
<atom:link href="https://h.cowbay.org/post/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
<item>
|
||||
<title>[雜念] 群暉 Synology NAS DS 415+ 誇張的維修費用</title>
|
||||
<link>https://h.cowbay.org/post/synology-ds415-repair-cost/</link>
|
||||
<pubDate>Tue, 04 Dec 2018 10:25:19 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/synology-ds415-repair-cost/</guid>
|
||||
<description><p>前幾天公司的一台 Synology DS 415+ 發生異常</p>
|
||||
|
||||
<p>注意到的時候，四顆硬碟燈號都不斷的在閃爍</p>
|
||||
|
||||
<p>但是已經無法登入系統</p>
|
||||
|
||||
<p>重開機之後更慘，四顆硬碟燈號全部橘燈恆亮</p>
|
||||
|
||||
<p>底下的電源藍燈不斷的在閃爍</p>
|
||||
|
||||
<p>雖然我一再表示不希望送修了</p>
|
||||
|
||||
<p>一來是已經過保，二來是DS415+ 本身就有intel bug，三來是因為對synology的NAS 實在沒有愛&hellip;</p>
|
||||
|
||||
<p>不過主管還是希望能夠先問群暉維修的費用多少</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 用 proxmox & Mellanox SFP 網卡土炮 10G LAB </title>
|
||||
<link>https://h.cowbay.org/post/10g-lab-using-proxmox-and-mellanox/</link>
|
||||
<pubDate>Fri, 30 Nov 2018 16:05:14 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/10g-lab-using-proxmox-and-mellanox/</guid>
|
||||
<description><p>想做一個 10G 的 LAB 環境出來已經很久了。</p>
|
||||
|
||||
<p>只是礙於10G RJ45的卡太貴了，然後光纖的種類又太複雜</p>
|
||||
|
||||
<p>如果直接在淘寶購買，很怕會買錯(什麼LC/FC LC/LC 多模單模 單芯雙芯 SFP/SFP+ 又是什麼光模塊的一大堆規格)</p>
|
||||
|
||||
<p>所以一直沒有付諸行動。</p>
|
||||
|
||||
<p>硬體的工作很久沒碰了，剛好在蝦皮看到有個賣家在賣 mellanox 的X2網卡，以在台灣的價格來說，算很便宜的 (550)</p>
|
||||
|
||||
<p>聊了一下，跟他請教了關於線材、光纖模塊的問題，回答也都很快很到位</p>
|
||||
|
||||
<p>就直接下訂了兩張網卡、兩個光纖模塊、一條LC/LC 光纖線</p>
|
||||
|
||||
<p>就是到貨有點久，等了兩個禮拜左右，一直到昨天東西才寄到</p>
|
||||
|
||||
<p>今天就花了點時間測試一下</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 還是 Ansible Selectattr </title>
|
||||
<link>https://h.cowbay.org/post/ansible-selectattr-filter/</link>
|
||||
<pubDate>Thu, 29 Nov 2018 11:22:28 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/ansible-selectattr-filter/</guid>
|
||||
<description><p>在上一篇 <a href="https://h.cowbay.org/post/ansible-selectattr/">Ansible how to use &lsquo;list&rsquo; in yaml file </a></p>
|
||||
|
||||
<p>有提到怎麼用 with_items / set_fact 來取得在yaml 檔案中的清單</p>
|
||||
|
||||
<p>不過就是有點醜</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] Ansible how to use 'list' in yaml file </title>
|
||||
<link>https://h.cowbay.org/post/ansible-selectattr/</link>
|
||||
<pubDate>Tue, 27 Nov 2018 16:50:53 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/ansible-selectattr/</guid>
|
||||
<description><p>這幾天在玩ansible 時，碰到一個問題</p>
|
||||
|
||||
<p>假如我有個yaml檔作為資料來源，檔名是 abc.yml</p>
|
||||
|
||||
<p>大概長這樣</p>
|
||||
|
||||
<pre><code> &quot;teams&quot;: [
|
||||
{
|
||||
&quot;chinese_name&quot;: &quot;TEAM1&quot;,
|
||||
&quot;description&quot;: &quot;TEAM1&quot;,
|
||||
&quot;gid&quot;: 10125,
|
||||
&quot;location&quot;: [
|
||||
&quot;hq&quot;
|
||||
],
|
||||
&quot;name&quot;: &quot;aa&quot;,
|
||||
&quot;users&quot;: [
|
||||
&quot;chen&quot;,
|
||||
&quot;chou&quot;,
|
||||
&quot;huani&quot;,
|
||||
&quot;yey&quot;,
|
||||
&quot;wa&quot;
|
||||
]
|
||||
},
|
||||
{
|
||||
&quot;chinese_name&quot;: &quot;TEAM2&quot;,
|
||||
&quot;description&quot;: &quot;TEAM2&quot;,
|
||||
&quot;gid&quot;: 10126,
|
||||
&quot;location&quot;: [
|
||||
&quot;hq&quot;
|
||||
],
|
||||
&quot;name&quot;: &quot;bb&quot;,
|
||||
&quot;users&quot;: [
|
||||
&quot;chhiao&quot;,
|
||||
&quot;chgc&quot;,
|
||||
&quot;chy&quot;,
|
||||
&quot;hsi&quot;,
|
||||
&quot;li&quot;,
|
||||
&quot;li&quot;,
|
||||
&quot;chgchi&quot;
|
||||
]
|
||||
}
|
||||
]
|
||||
|
||||
</code></pre></description>
|
||||
</item><item>
|
||||
<title>[筆記] 為了metabase 修改 firefox 開啟網頁時使用的預設語言 change the preferred language in firefox for metabase</title>
|
||||
<link>https://h.cowbay.org/post/change-preferred-language-in-firefox/</link>
|
||||
<pubDate>Thu, 15 Nov 2018 11:06:28 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/change-preferred-language-in-firefox/</guid>
|
||||
<description><p>最近在測試metabase，記得幾個月前就有測試過</p>
|
||||
|
||||
<p>但是當時的界面和現在的樣子差很多，看樣子改版還滿勤勞的</p>
|
||||
|
||||
<p>所以這次改用docker來建立，根本五分鐘不到就建好了(挖鼻孔)</p>
|
||||
|
||||
<p>不過呢，很討厭的是，一進去就發現語系採用的是簡體中文</p></description>
|
||||
</item><item>
|
||||
<title>PostgreSQL 直接從已經存在的使用者複製權限到另一個使用者</title>
|
||||
<link>https://h.cowbay.org/post/copy_role_in_pgsql/</link>
|
||||
<pubDate>Mon, 12 Nov 2018 09:48:12 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/copy_role_in_pgsql/</guid>
|
||||
<description><p>因為工作上的需求，有個資料庫需要開放給不同team的人去存取</p>
|
||||
|
||||
<p>雖然都是在同一台機器上的同一個資料庫</p>
|
||||
|
||||
<p>但是希望能夠不同team的人用不同的資料庫使用者</p>
|
||||
|
||||
<p>這樣萬一出事，會比較好抓兇手？？</p></description>
|
||||
</item><item>
|
||||
<title>[筆記] 詭異的client&server間連線的問題，或許跟KVM有關係？</title>
|
||||
<link>https://h.cowbay.org/post/weird-client-server-connection/</link>
|
||||
<pubDate>Thu, 08 Nov 2018 18:01:23 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/weird-client-server-connection/</guid>
|
||||
<description><p>這是發生在一個夜黑風高的寂寥深夜&hellip;.. ( What The FXXX &hellip; )</p>
|
||||
|
||||
<p>來到這個環境之後，有一個很詭異的狀況一直困擾著我</p>
|
||||
|
||||
<p>在每個分公司，都會有一台伺服器作為KVM Host</p>
|
||||
|
||||
<p>上面跑兩台VM，一台作為ansible controller (目前沒作用)</p>
|
||||
|
||||
<p>另一台作為這邊所謂的 &ldquo;Build Server&rdquo;</p>
|
||||
|
||||
<p>用途包含了DHCP Server / Proxy Server (squid3) / APT Proxy (squid-deb-proxy)</p>
|
||||
|
||||
<p>問題就發生在這台 Build Server 上&hellip;</p></description>
|
||||
</item><item>
|
||||
<title>Nice Du Report Tool Durep</title>
|
||||
<link>https://h.cowbay.org/post/nice-du-report-tool-durep/</link>
|
||||
<pubDate>Tue, 06 Nov 2018 15:24:29 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/nice-du-report-tool-durep/</guid>
|
||||
<description><p>最近在重新規劃前人留下的backup爛攤子
|
||||
各個伺服器統一備份到一台backup storage
|
||||
想說如果每天能夠看到backup storage的磁碟用量的話
|
||||
就可以抓出備份空間成長速度、推估需要多大的磁碟空間
|
||||
找了一些工具，結果發現 durep 這個 ubuntu 內建的工具
|
||||
基本上可以滿足我的需求</p></description>
|
||||
</item><item>
|
||||
<title>Bookstack Docker</title>
|
||||
<link>https://h.cowbay.org/post/bookstack-docker/</link>
|
||||
<pubDate>Tue, 06 Nov 2018 14:57:14 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/bookstack-docker/</guid>
|
||||
<description><p>Bookstack 是一套非常好用的線上&rdquo;筆記&rdquo;系統</p>
|
||||
|
||||
<p>他用圖書館/書本的概念，讓使用者可以建立自己的&rdquo;圖書館&rdquo;</p>
|
||||
|
||||
<p>同時在圖書館內建立不同的&rdquo;書籍&rdquo;</p>
|
||||
|
||||
<p>而且支援 Markdown 語法</p>
|
||||
|
||||
<p>其他的方式像是在nextcloud上編輯 md檔案(字體太小)</p>
|
||||
|
||||
<p>或者是boostnote(只能在本機)</p>
|
||||
|
||||
<p>都或多或少有點小缺點</p>
|
||||
|
||||
<p>Bookstack則是沒有這些問題，不過就是系統「大」了點&hellip;</p>
|
||||
|
||||
<p>不過還好有人做成docker的方式來啟動，大大的降低了建置的難度(其實也沒有很難啦，只是要裝個PHP、弄個DB而已)</p></description>
|
||||
</item><item>
|
||||
<title>筆記- 啟用群暉NAS (Synology NAS)的SSH Server 透過Publickey 認證免密碼登入</title>
|
||||
<link>https://h.cowbay.org/post/enable-synology-public-ssh/</link>
|
||||
<pubDate>Mon, 05 Nov 2018 14:16:54 +0800</pubDate>
|
||||
|
||||
<guid>https://h.cowbay.org/post/enable-synology-public-ssh/</guid>
|
||||
<description><p>公司內有幾台NAS，其中有一台用來放開發人員的postgresql dump file
|
||||
之前都是主要的開發人員上傳到google drive，分享出來 ，然後其他人去抓回來</p>
|
||||
|
||||
<p>這樣子有個問題是，當server要存取這些檔案時，就沒辦法了，除非透過一些 3rd party的軟體
|
||||
像是這篇</p>
|
||||
|
||||
<p><a href="https://www.omgubuntu.co.uk/2017/04/mount-google-drive-ocamlfuse-linux">https://www.omgubuntu.co.uk/2017/04/mount-google-drive-ocamlfuse-linux</a></p>
|
||||
|
||||
<p>或者是這篇</p>
|
||||
|
||||
<p><a href="https://www.maketecheasier.com/mount-google-drive-ubuntu/">https://www.maketecheasier.com/mount-google-drive-ubuntu/</a></p>
|
||||
|
||||
<p>但是手邊的伺服器，原則上除非有必要，不然都沒有開放internet
|
||||
所以導致明明檔案就在那邊，但是要取得就是很麻煩</p></description>
|
||||
</item>
|
||||
</channel>
|
||||
</rss>
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user