Skip to content

Home

從Sublime Text切換到Atom

Atom文本編輯器剛剛發布了其1.0版本。有很多理由從Sublime Text切換過來。也許你熱愛開源的概念,或者你是GitHub社區的一員。雖然Atom有著不同的外觀和感覺,但安裝以下的包可以快速提高你的生產力。

1. 安裝Monokai語法主題

有很多酷炫的主題,但我習慣於Sublime的默認色彩方案。通過訪問以下頁面,安裝Monokai語法主題:

https://atom.io/themes/monokai

2. 將標籤轉換為空格

通過前往以下網址安裝"tabs-to-spaces"包:

https://atom.io/packages/tabs-to-spaces

然後在您的設定 cson 文件中添加這行代碼:

'tabs-to-spaces': 'onSave': 'untabify'

3. 軟標籤

默認情況下,堅硬的標籤為4個字符長,這可能導致由於過多的縮進而使代碼難以閱讀。我建議在用戶設定中啟用"Soft Tabs"選項,這將用空格替換標籤。

4. 顯示空白位

在設定中,勾選"Show Invisibles"。這將在代碼中加入小點來顯示縮進空格。

5. 在保存時修剪尾隨的空白位

這個功能會在保存編輯器時去掉尾隨的空格並添加一個尾隨的換行。

https://atom.io/packages/whitespace

6. 括號高亮

"Bracket-matcher"是一個必需的包,用於高亮各種括號:() [] {} "" '' <>。

https://github.com/atom/bracket-matcher

7. Emmet

Emmet對網頁開發者來說是必不可少的工具包。它可以用快捷方式節省大量時間。例如,輸入以下的代碼然後按Tab鍵:

div#container>ul>li.item

這將輸出相應的HTML標籤。

另一個例子:開始輸入lorem,它會自動輸出整個"Lorem Ipsum"文本。

https://github.com/emmetio/emmet-atom

8. Git Plus

此包允許您在Atom Editor內進行Git操作,無需打開終端,節省了您的工作流程的一些時間:

https://atom.io/packages/git-plus

9. Git Diff

此功能在編輯器的邊界標識出自上次提交以來被添加、編輯或刪除的行:

https://github.com/atom/git-diff

10. Linter和JSHint

要檢查您的代碼,請訪問:

https://atom.io/packages/linter

對於JSHint,請前往:

https://atom.io/packages/linter-jshint

11. Alignment

此包提供了一個簡單的鍵綁定,用於對齊多行、多光標和多選擇。例如,使用快捷鍵ctrl+cmd+a的前後對比:

Before:

var a = b;
var ab = c;
var abcd = d;
var ddddd = d;

After:

var a     = b;
var ab    = c;
var abcd  = d;
var ddddd = d;

https://atom.io/packages/atom-alignment

12. 將Atom設定為Git的預設編輯器

如果你不習慣使用Vim撰寫Git提交,可以通過執行以下命令將Atom設為預設編輯器:

git config --global core.editor "atom --wait"

包提供了開發人員提高生產力和工作流程的工具。你安裝了哪些包?告訴我你的最愛是什麼。

How to Upgrade Your Ghost Blog via Command Line

Step 1: Navigate to Your Ghost Blog Directory

First, change the directory to the path where your Ghost blog is installed. For example, in my case, it's located at:

cd /var/www

Step 2: Download the Latest Version with wget

Use wget to download the latest version of Ghost:

wget https://ghost.org/zip/ghost-X.X.X.zip

Note: You can find the current version on the official website: https://ghost.org/download/

Step 3: Remove the Old Core Code

Delete the old core directory:

rm -rf ghost/core

Step 4: Unzip the Downloaded File

Unzip the file you downloaded into the ghost directory:

unzip -uo ghost-0.6.4.zip -d ghost

Step 5: Change Ownership and Permissions

Update the ownership and permissions for the Ghost files:

chown -R ghost:ghost ghost/

Step 6: Install New Dependencies

Navigate back to your Ghost directory and install new dependencies:

cd /var/www/ghost
npm install

Step 7: Restart Ghost

Finally, restart your Ghost blog:

pm2 restart ghost

Note: If you're not using pm2, you can use the following command instead:

service ghost start

Your Ghost blog should now be successfully upgraded!


How to Upgrade Your Ghost Blog via Command Line

Welcome to "Continuous Improvement," the podcast where we explore tips, tricks, and strategies for improving and optimizing various aspects of our lives. I'm your host, Victor, and in today's episode, we're going to discuss how to upgrade your Ghost blog to the latest version. So if you're a Ghost blog owner and want to make sure you have all the latest features and bug fixes, this episode is for you.

Before we dive into the steps, make sure you have access to your Ghost blog directory. This is where all your Ghost files are stored. Once you're ready, let's get started!

Step 1 is to navigate to your Ghost blog directory. In your terminal, change the directory to the path where your Ghost blog is installed. For example, if your blog is located at /var/www, you can use the command:

cd /var/www

Great! Now that we're in the right directory, step 2 is to download the latest version of Ghost using the wget command. You can find the current version on the official Ghost website at https://ghost.org/download/. Once you have the download link, use wget followed by the link to download the latest version.

Awesome! Now that we have the latest version of Ghost downloaded, let's move on to step 3. In this step, we need to remove the old core code. Use the following command to delete the old core directory:

rm -rf ghost/core

We're making progress! Step 4 is all about unzipping the downloaded file into the Ghost directory. Use the command unzip -uo ghost-X.X.X.zip -d ghost, where X.X.X represents the version number you downloaded. This will extract the files and overwrite any existing ones.

Moving on to step 5, we need to update the ownership and permissions for the newly added Ghost files. This helps ensure everything works smoothly. Use the command chown -R ghost:ghost ghost/ to update the ownership.

Step 6 is an important one. We need to install new dependencies for the upgraded Ghost version. Navigate back to your Ghost directory using cd /var/www/ghost and run npm install to install the new dependencies.

Fantastic! We're almost there. In step 7, it's time to restart your Ghost blog to complete the upgrade process. Use the command pm2 restart ghost if you're using pm2. If not, you can try service ghost start instead.

And there you have it! Your Ghost blog should now be successfully upgraded to the latest version. Remember, keeping your blog up to date ensures you have access to all the latest features and bug fixes.

That brings us to the end of this episode of "Continuous Improvement." I hope you found these steps helpful in upgrading your Ghost blog. If you have any questions or suggestions for future episodes, feel free to reach out to me. Until next time, keep improving and optimizing!

如何透過命令行升級您的Ghost博客

步驟1:導航至您的Ghost博客目錄

首先,將目錄更改為您的Ghost博客安裝的路徑。例如,在我的情況下,它位於:

cd /var/www

步驟2:使用wget下載最新版本

使用wget下載Ghost的最新版本:

wget https://ghost.org/zip/ghost-X.X.X.zip

注意:您可以在官方網站上找到當前的版本:https://ghost.org/download/

步驟3:移除舊的核心代碼

刪除舊的核心目錄:

rm -rf ghost/core

步驟4:解壓下載的文件

將您下載的文件解壓縮到ghost目錄:

unzip -uo ghost-0.6.4.zip -d ghost

步驟5:變更所有權和權限

更新Ghost文件的所有權和權限:

chown -R ghost:ghost ghost/

步驟6:安裝新的依賴關係

返回到您的Ghost目錄並安裝新的依賴關係:

cd /var/www/ghost
npm install

步驟7:重新啟動Ghost

最後,重新啟動您的Ghost博客:

pm2 restart ghost

注意:如果您不使用pm2,則可以使用以下命令:

service ghost start

您的Ghost博客現在應該已成功升級!


SSH: How to Fix the 'Unprotected Private Key' Error

The Problem

When I downloaded the .pem file to SSH into my AWS instance, I encountered the following error:

WARNING: UNPROTECTED PRIVATE KEY FILE!

Permissions 0640 for 'blog.pem' are too open. It is required that your private key files are NOT accessible by others. This private key will be ignored. Bad permissions: ignore key: blog.pem Permission denied (publickey).

The Solution

To resolve this issue, run the following command in your terminal:

ssh -i xxx.pem root@52.74.3.53

Replace xxx.pem with the name of your .pem file.

This command will modify the permissions on the keys, making them readable only by you.

SSH: How to Fix the 'Unprotected Private Key' Error

The Problem

Hello, and welcome to "Continuous Improvement," the podcast where we explore tips, tricks, and solutions for everyday problems. I'm your host, Victor. In today's episode, we'll be discussing a common issue encountered when attempting to SSH into an AWS instance. We'll explore the error message and provide step-by-step instructions to resolve it. So let's dive right in!

Have you ever come across the following error message when trying to SSH into your AWS instance?

"WARNING: UNPROTECTED PRIVATE KEY FILE! Permissions 0640 for 'blog.pem' are too open. It is required that your private key files are NOT accessible by others. This private key will be ignored. Bad permissions: ignore key: blog.pem Permission denied (publickey)."

This error message may seem complex at first, but fear not! I have a simple solution for you. By following a few steps, we can quickly resolve this issue.

Step one, open your terminal, and navigate to the location of your .pem file.

Step two, once you're in the correct directory, run the following command:

"ssh -i xxx.pem root@52.74.3.53"

Make sure to replace xxx.pem with the name of your specific .pem file.

This command will modify the permissions on the keys, making them readable only by you. Once you've done that, you should be able to SSH into your AWS instance without any issues.

And just like that, you've successfully resolved the pesky permissions error that was preventing you from accessing your AWS instance. Remember, continuous improvement is all about finding solutions to everyday problems and making our lives easier.

I hope you found this episode helpful. If you have any questions or suggestions for future episodes, feel free to reach out. Thank you for tuning in to "Continuous Improvement." I'm your host, Victor, and until next time, keep learning, keep improving. Goodbye!

SSH:如何修復「未保護的私鑰」錯誤

問題

當我下載了 .pem 檔案以便 SSH 連線到我的 AWS 實例時,我遇到了以下的錯誤:

警告:未保護的私鑰檔案!

'blog.pem' 的權限 0640 過於開放。要求您的私鑰檔案不能被其他人訪問。將忽略此私鑰。壞的權限:忽略鑰匙:blog.pem 權限被拒絕 (publickey)。

解決方案

為了解決此問題,在你的終端機執行下列的指令:

ssh -i xxx.pem root@52.74.3.53

xxx.pem 換成你的 .pem 檔案的名稱。

此指令會修改鑰匙的權限,使其僅能被你閱讀。

How to Fix Ruby Gems Permission Error on Mac OS X Yosemite

The Problem

While trying to install a gem on Mac OS X Yosemite, I encountered the following error:

ERROR: While executing gem … (Gem::FilePermissionError) You don’t have write permissions for the /Library/Ruby/Gems/2.0.0 directory.

The Solution

Step 1: Install Rbenv

To start, you'll need to install Rbenv and Ruby-build:

brew install rbenv ruby-build

Next, add Rbenv to ~/.zshrc so it starts automatically:

echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.zshrc
echo 'eval "$(rbenv init -)"' >> ~/.zshrc

Note: If you are not using Zsh, modify your ~/.bash_profile instead of ~/.zshrc.

Step 2: Restart Your Shell

Close your terminal and reopen it to apply the changes.

Step 3: Install Ruby, Set Global Version, and Rehash

Now, install Ruby and set it as your global Ruby version:

rbenv install 2.0.0-p247
rbenv global 2.0.0-p247
rbenv rehash
Step 4: Install Gems as Usual

You can now proceed to install gems without encountering permission issues.

gem install [gem-name]

Your gem should now install successfully!


How to Fix Ruby Gems Permission Error on Mac OS X Yosemite

The Problem

Hello and welcome back to Continuous Improvement, the podcast where we explore solutions to common problems faced by developers. I'm your host, Victor, and in today's episode, we'll be discussing how to resolve a permission error when trying to install a gem on Mac OS X Yosemite.

So, you're trying to install a gem, but you come across the following error message: "ERROR: While executing gem … (Gem::FilePermissionError) You don’t have write permissions for the /Library/Ruby/Gems/2.0.0 directory." What can you do to fix this issue?

The solution involves a few steps, but don't worry, I'll guide you through them. Let's get started.

Step 1 is to install Rbenv and Ruby-build. Open your terminal and enter the following command: "brew install rbenv ruby-build". This will install the necessary tools.

Now, we need to add Rbenv to your configuration file so that it starts automatically. If you're using the Zsh shell, enter the following commands: "echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.zshrc" and "echo 'eval "$(rbenv init -)"' >> ~/.zshrc".

If you are using a different shell, such as Bash, modify your ~/.bash_profile with the same commands.

Step 2 requires you to restart your shell. Close your terminal completely and reopen it to apply the changes we made.

In Step 3, we'll install Ruby, set it as your global version, and rehash. Enter the following commands in your terminal: "rbenv install 2.0.0-p247" to install Ruby, "rbenv global 2.0.0-p247" to set it as the global version, and "rbenv rehash" to update the Ruby environment.

Great! Now we're ready for Step 4. You can now proceed to install gems without encountering any permission issues. Simply use the command "gem install [gem-name]" to install your desired gem.

And there you have it folks, a step-by-step guide to overcome the permission error when installing a gem on Mac OS X Yosemite. With these instructions, you'll be able to install gems hassle-free.

Well, that's all for today's episode of Continuous Improvement. I hope you found this information helpful. If you have any questions or suggestions for future episodes, feel free to reach out to me. Thank you for tuning in, and until next time, happy coding!

如何修復Mac OS X Yosemite上的Ruby Gems權限錯誤

問題

當我嘗試在Mac OS X Yosemite上安裝一個gem時,我遇到了以下錯誤:

錯誤:在執行gem時...(Gem::FilePermissionError)您沒有/Library/Ruby/Gems/2.0.0目錄的寫入權限。

解決方案

步驟1:安裝Rbenv

首先,您需要安裝Rbenv和Ruby-build:

brew install rbenv ruby-build

接下來,將Rbenv添加到~/.zshrc中,使其自動啟動:

echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.zshrc
echo 'eval "$(rbenv init -)"' >> ~/.zshrc

:如果您不使用Zsh,請修改您的~/.bash_profile,而不是~/.zshrc

步驟2:重新啟動你的Shell

關閉您的終端並重新打開它以應用更改。

步驟3:安裝Ruby,設置全局版本並重新排序

現在,安裝Ruby並將其設置為您的全局Ruby版本:

rbenv install 2.0.0-p247
rbenv global 2.0.0-p247
rbenv rehash
步驟4:像往常一樣安裝Gems

現在您可以繼續安裝gems,而不會遇到權限問題。

gem install [gem-name]

您的gem現在應該成功安裝了!