in 네트워크프로그래밍
네트워크 태그 테스트 포스팅입니다.
네트워크프로그래밍1 There are multiple ways of installing Hydejack. The easiest and cleanest way is via the Starter Kit. Alternatively, you can use the Ruby gem. If you don’t mind a cluttered source directory, you can use the zip file. Finally, If you know what you are doing, you can fork the git repository.
네트워크 태그 테스트 포스팅입니다.
네트워크프로그래밍3 There are multiple ways of installing Hydejack. The easiest and cleanest way is via the Starter Kit. Alternatively, you can use the Ruby gem. If you don’t mind a cluttered source directory, you can use the zip file. Finally, If you know what you are doing, you can fork the git repository.
Buyers of the PRO version should follow these steps.
Using the Starter Kit has the advantage of not cluttering your blog repository. Additionally, it allows you to publish your site on GitHub Pages with a single push.
If you have a GitHub account, fork the hy-starter-kit repository. Otherwise download the source files and unzip them somewhere on your machine.
NOTE: In addition to the docs here, you can follow the quick start guide in the Starter Kit.
cd into the directory where _config.yml is located and follow the steps in Running locally.
Alternatively, you can just 
.
Jekyll has built-in support for using themes that are hosted on RubyGems.
If you haven’t already, create a new Jekyll site first:
$ jekyll new <PATH>
Your site’s root dir should look something like this
├── _posts
│ └── 2017-04-07-welcome-to-jekyll.markdown
├── _config.yml
├── about.md
├── Gemfile
├── Gemfile.lock
└── index.md
NOTE: Hydejack works with Jekyll’s default config.yml, but it is recommended that you replace it with Hydejack’s default config file. It contains the names of all config options known to Hydejack and provides sensible defaults (like minifying HTML and CSS in production builds).
Next, you’ll want to add jekyll-theme-hydejack as a dependency by adding the following line to the Gemfile.
gem "jekyll-theme-hydejack"
(You can also remove the old theme jekyll-theme-minima from the Gemfile)
Now you want to edit the _config.yml of your Jekyll site and set Hydejack as the theme. Look for the theme key and set its value to jekyll-theme-hydejack.
theme: jekyll-theme-hydejack
For more information on gem-based themes, see the Jekyll Documentation.
You can now continue with running locally.
If you downloaded the extended zip, extract the contents somewhere on your machine. The high-level folder structure will look something like.
├── _data
├── _featured_categories
├── _featured_tags
├── _includes
├── _js
├── _layouts
├── _posts
├── _sass
├── assets
├── _config.yml
├── 404.md
├── about.md
├── index.html
└── posts.md
cd into the directory where _config.yml is located and follow the steps in Running locally.
If you are familiar with using git, you can add the Hydejack repository as a remote, and merge its master branch into your working branch.
$ git remote add hydejack git@github.com:hydecorp/hydejack.git
$ git pull hydejack master
You can also update Hydejack this way. The master branch will not contain work in progress, but will contain major (breaking) changes. This approach is recommended if you intend to customize Hydejack.
You can now continue with running locally.
If you bought the PRO version, you’ve received a zip archive with the following contents:
├── install
├── upgrade
├── CHANGELOG.pdf
├── Documentation.pdf
├── NOTICE.pdf
├── PRO License.pdf
├── PRO–hy-drawer License.pdf
├── PRO–hy-img License.pdf
├── PRO–hy-push-state License.pdf
└── .ssh
installupgrade.sshFor new installations only the install folder is relevant. Unzip the archive somewhere on your machine, then cd into the install folder, e.g.
$ cd ~/Downloads/hydejack-pro-8.5.2/install/
You can now continue with Running locally.
If you know how to handle SSH keys, you can also install the PRO version as a gem-based theme via GitHub. The advantage of this method is that you avoid cluttering your Jekyll repository with Hydejack’s source files.
The downloaded zip contains a read-only key for a private GitHub repository. It is located at <dowloaded zip>/.ssh/hydejack_8_pro. You have to copy the key file to ~/.ssh (or wherever your SSH keys are located), e.g.:
$ cp ~/Downloads/hydejack-pro-8.5.2/.ssh/hydejack_8_pro ~/.ssh/
It is required that your private key files are NOT accessible by others, e.g.:
$ chmod 600 ~/.ssh/hydejack_8_pro
Then add the following to .ssh/config:
Host hydejack
HostName github.com
IdentitiesOnly yes
IdentityFile ~/.ssh/hydejack_8_pro
Next, open Gemfile in your Jekyll repository and add:
gem "jekyll-theme-hydejack-pro", git: 'git@github.com:qwtel/hydejack-pro-8.git'
In your _config.yml, add:
theme: jekyll-theme-hydejack-pro
You can now continue with Running locally.
Make sure you’ve cded into the directory where _config.yml is located. Before running for the first time, dependencies need to be fetched from RubyGems:
$ bundle install
NOTE: If you are missing the bundle command, you can install Bundler by running gem install bundler.
Now you can run Jekyll on your local machine:
$ bundle exec jekyll serve
and point your browser to http://localhost:4000 to see Hydejack in action.
Continue with Config
네트워크 태그 테스트 포스팅입니다.
네트워크프로그래밍3 There are multiple ways of installing Hydejack. The easiest and cleanest way is via the Starter Kit. Alternatively, you can use the Ruby gem. If you don’t mind a cluttered source directory, you can use the zip file. Finally, If you know what you are doing, you can fork the git repository.
Buyers of the PRO version should follow these steps.
Using the Starter Kit has the advantage of not cluttering your blog repository. Additionally, it allows you to publish your site on GitHub Pages with a single push.
If you have a GitHub account, fork the hy-starter-kit repository. Otherwise download the source files and unzip them somewhere on your machine.
NOTE: In addition to the docs here, you can follow the quick start guide in the Starter Kit.
cd into the directory where _config.yml is located and follow the steps in Running locally.
Alternatively, you can just .
Jekyll has built-in support for using themes that are hosted on RubyGems.
If you haven’t already, create a new Jekyll site first:
$ jekyll new <PATH>
Your site’s root dir should look something like this
├── _posts
│ └── 2017-04-07-welcome-to-jekyll.markdown
├── _config.yml
├── about.md
├── Gemfile
├── Gemfile.lock
└── index.md
NOTE: Hydejack works with Jekyll’s default config.yml, but it is recommended that you replace it with Hydejack’s default config file. It contains the names of all config options known to Hydejack and provides sensible defaults (like minifying HTML and CSS in production builds).
Next, you’ll want to add jekyll-theme-hydejack as a dependency by adding the following line to the Gemfile.
gem "jekyll-theme-hydejack"
(You can also remove the old theme jekyll-theme-minima from the Gemfile)
Now you want to edit the _config.yml of your Jekyll site and set Hydejack as the theme. Look for the theme key and set its value to jekyll-theme-hydejack.
theme: jekyll-theme-hydejack
For more information on gem-based themes, see the Jekyll Documentation.
You can now continue with running locally.
If you downloaded the extended zip, extract the contents somewhere on your machine. The high-level folder structure will look something like.
├── _data
├── _featured_categories
├── _featured_tags
├── _includes
├── _js
├── _layouts
├── _posts
├── _sass
├── assets
├── _config.yml
├── 404.md
├── about.md
├── index.html
└── posts.md
cd into the directory where _config.yml is located and follow the steps in Running locally.
If you are familiar with using git, you can add the Hydejack repository as a remote, and merge its master branch into your working branch.
$ git remote add hydejack git@github.com:hydecorp/hydejack.git
$ git pull hydejack master
You can also update Hydejack this way. The master branch will not contain work in progress, but will contain major (breaking) changes. This approach is recommended if you intend to customize Hydejack.
You can now continue with running locally.
If you bought the PRO version, you’ve received a zip archive with the following contents:
├── install
├── upgrade
├── CHANGELOG.pdf
├── Documentation.pdf
├── NOTICE.pdf
├── PRO License.pdf
├── PRO–hy-drawer License.pdf
├── PRO–hy-img License.pdf
├── PRO–hy-push-state License.pdf
└── .ssh
installupgrade.sshFor new installations only the install folder is relevant. Unzip the archive somewhere on your machine, then cd into the install folder, e.g.
$ cd ~/Downloads/hydejack-pro-8.5.2/install/
You can now continue with Running locally.
If you know how to handle SSH keys, you can also install the PRO version as a gem-based theme via GitHub. The advantage of this method is that you avoid cluttering your Jekyll repository with Hydejack’s source files.
The downloaded zip contains a read-only key for a private GitHub repository. It is located at <dowloaded zip>/.ssh/hydejack_8_pro. You have to copy the key file to ~/.ssh (or wherever your SSH keys are located), e.g.:
$ cp ~/Downloads/hydejack-pro-8.5.2/.ssh/hydejack_8_pro ~/.ssh/
It is required that your private key files are NOT accessible by others, e.g.:
$ chmod 600 ~/.ssh/hydejack_8_pro
Then add the following to .ssh/config:
Host hydejack
HostName github.com
IdentitiesOnly yes
IdentityFile ~/.ssh/hydejack_8_pro
Next, open Gemfile in your Jekyll repository and add:
gem "jekyll-theme-hydejack-pro", git: 'git@github.com:qwtel/hydejack-pro-8.git'
In your _config.yml, add:
theme: jekyll-theme-hydejack-pro
You can now continue with Running locally.
Make sure you’ve cded into the directory where _config.yml is located. Before running for the first time, dependencies need to be fetched from RubyGems:
$ bundle install
NOTE: If you are missing the bundle command, you can install Bundler by running gem install bundler.
Now you can run Jekyll on your local machine:
$ bundle exec jekyll serve
and point your browser to http://localhost:4000 to see Hydejack in action.
Continue with Config
in Network on Network
네트워크 태그 테스트 포스팅입니다.
네트워크프로그래밍2 There are multiple ways of installing Hydejack. The easiest and cleanest way is via the Starter Kit. Alternatively, you can use the Ruby gem. If you don’t mind a cluttered source directory, you can use the zip file. Finally, If you know what you are doing, you can fork the git repository.
Buyers of the PRO version should follow these steps.
Using the Starter Kit has the advantage of not cluttering your blog repository. Additionally, it allows you to publish your site on GitHub Pages with a single push.
If you have a GitHub account, fork the hy-starter-kit repository. Otherwise download the source files and unzip them somewhere on your machine.
NOTE: In addition to the docs here, you can follow the quick start guide in the Starter Kit.
cd into the directory where _config.yml is located and follow the steps in Running locally.
Alternatively, you can just .
Jekyll has built-in support for using themes that are hosted on RubyGems.
If you haven’t already, create a new Jekyll site first:
$ jekyll new <PATH>
Your site’s root dir should look something like this
├── _posts
│ └── 2017-04-07-welcome-to-jekyll.markdown
├── _config.yml
├── about.md
├── Gemfile
├── Gemfile.lock
└── index.md
NOTE: Hydejack works with Jekyll’s default config.yml, but it is recommended that you replace it with Hydejack’s default config file. It contains the names of all config options known to Hydejack and provides sensible defaults (like minifying HTML and CSS in production builds).
Next, you’ll want to add jekyll-theme-hydejack as a dependency by adding the following line to the Gemfile.
gem "jekyll-theme-hydejack"
(You can also remove the old theme jekyll-theme-minima from the Gemfile)
Now you want to edit the _config.yml of your Jekyll site and set Hydejack as the theme. Look for the theme key and set its value to jekyll-theme-hydejack.
theme: jekyll-theme-hydejack
For more information on gem-based themes, see the Jekyll Documentation.
You can now continue with running locally.
If you downloaded the extended zip, extract the contents somewhere on your machine. The high-level folder structure will look something like.
├── _data
├── _featured_categories
├── _featured_tags
├── _includes
├── _js
├── _layouts
├── _posts
├── _sass
├── assets
├── _config.yml
├── 404.md
├── about.md
├── index.html
└── posts.md
cd into the directory where _config.yml is located and follow the steps in Running locally.
If you are familiar with using git, you can add the Hydejack repository as a remote, and merge its master branch into your working branch.
$ git remote add hydejack git@github.com:hydecorp/hydejack.git
$ git pull hydejack master
You can also update Hydejack this way. The master branch will not contain work in progress, but will contain major (breaking) changes. This approach is recommended if you intend to customize Hydejack.
You can now continue with running locally.
If you bought the PRO version, you’ve received a zip archive with the following contents:
├── install
├── upgrade
├── CHANGELOG.pdf
├── Documentation.pdf
├── NOTICE.pdf
├── PRO License.pdf
├── PRO–hy-drawer License.pdf
├── PRO–hy-img License.pdf
├── PRO–hy-push-state License.pdf
└── .ssh
installupgrade.sshFor new installations only the install folder is relevant. Unzip the archive somewhere on your machine, then cd into the install folder, e.g.
$ cd ~/Downloads/hydejack-pro-8.5.2/install/
You can now continue with Running locally.
If you know how to handle SSH keys, you can also install the PRO version as a gem-based theme via GitHub. The advantage of this method is that you avoid cluttering your Jekyll repository with Hydejack’s source files.
The downloaded zip contains a read-only key for a private GitHub repository. It is located at <dowloaded zip>/.ssh/hydejack_8_pro. You have to copy the key file to ~/.ssh (or wherever your SSH keys are located), e.g.:
$ cp ~/Downloads/hydejack-pro-8.5.2/.ssh/hydejack_8_pro ~/.ssh/
It is required that your private key files are NOT accessible by others, e.g.:
$ chmod 600 ~/.ssh/hydejack_8_pro
Then add the following to .ssh/config:
Host hydejack
HostName github.com
IdentitiesOnly yes
IdentityFile ~/.ssh/hydejack_8_pro
Next, open Gemfile in your Jekyll repository and add:
gem "jekyll-theme-hydejack-pro", git: 'git@github.com:qwtel/hydejack-pro-8.git'
In your _config.yml, add:
theme: jekyll-theme-hydejack-pro
You can now continue with Running locally.
Make sure you’ve cded into the directory where _config.yml is located. Before running for the first time, dependencies need to be fetched from RubyGems:
$ bundle install
NOTE: If you are missing the bundle command, you can install Bundler by running gem install bundler.
Now you can run Jekyll on your local machine:
$ bundle exec jekyll serve
and point your browser to http://localhost:4000 to see Hydejack in action.
Continue with Config
in Network on Network
네트워크 태그 테스트 포스팅입니다.
네트워크프로그래밍2 There are multiple ways of installing Hydejack. The easiest and cleanest way is via the Starter Kit. Alternatively, you can use the Ruby gem. If you don’t mind a cluttered source directory, you can use the zip file. Finally, If you know what you are doing, you can fork the git repository.
Buyers of the PRO version should follow these steps.
Using the Starter Kit has the advantage of not cluttering your blog repository. Additionally, it allows you to publish your site on GitHub Pages with a single push.
If you have a GitHub account, fork the hy-starter-kit repository. Otherwise download the source files and unzip them somewhere on your machine.
NOTE: In addition to the docs here, you can follow the quick start guide in the Starter Kit.
cd into the directory where _config.yml is located and follow the steps in Running locally.
Alternatively, you can just .
Jekyll has built-in support for using themes that are hosted on RubyGems.
If you haven’t already, create a new Jekyll site first:
$ jekyll new <PATH>
Your site’s root dir should look something like this
├── _posts
│ └── 2017-04-07-welcome-to-jekyll.markdown
├── _config.yml
├── about.md
├── Gemfile
├── Gemfile.lock
└── index.md
NOTE: Hydejack works with Jekyll’s default config.yml, but it is recommended that you replace it with Hydejack’s default config file. It contains the names of all config options known to Hydejack and provides sensible defaults (like minifying HTML and CSS in production builds).
Next, you’ll want to add jekyll-theme-hydejack as a dependency by adding the following line to the Gemfile.
gem "jekyll-theme-hydejack"
(You can also remove the old theme jekyll-theme-minima from the Gemfile)
Now you want to edit the _config.yml of your Jekyll site and set Hydejack as the theme. Look for the theme key and set its value to jekyll-theme-hydejack.
theme: jekyll-theme-hydejack
For more information on gem-based themes, see the Jekyll Documentation.
You can now continue with running locally.
If you downloaded the extended zip, extract the contents somewhere on your machine. The high-level folder structure will look something like.
├── _data
├── _featured_categories
├── _featured_tags
├── _includes
├── _js
├── _layouts
├── _posts
├── _sass
├── assets
├── _config.yml
├── 404.md
├── about.md
├── index.html
└── posts.md
cd into the directory where _config.yml is located and follow the steps in Running locally.
If you are familiar with using git, you can add the Hydejack repository as a remote, and merge its master branch into your working branch.
$ git remote add hydejack git@github.com:hydecorp/hydejack.git
$ git pull hydejack master
You can also update Hydejack this way. The master branch will not contain work in progress, but will contain major (breaking) changes. This approach is recommended if you intend to customize Hydejack.
You can now continue with running locally.
If you bought the PRO version, you’ve received a zip archive with the following contents:
├── install
├── upgrade
├── CHANGELOG.pdf
├── Documentation.pdf
├── NOTICE.pdf
├── PRO License.pdf
├── PRO–hy-drawer License.pdf
├── PRO–hy-img License.pdf
├── PRO–hy-push-state License.pdf
└── .ssh
installupgrade.sshFor new installations only the install folder is relevant. Unzip the archive somewhere on your machine, then cd into the install folder, e.g.
$ cd ~/Downloads/hydejack-pro-8.5.2/install/
You can now continue with Running locally.
If you know how to handle SSH keys, you can also install the PRO version as a gem-based theme via GitHub. The advantage of this method is that you avoid cluttering your Jekyll repository with Hydejack’s source files.
The downloaded zip contains a read-only key for a private GitHub repository. It is located at <dowloaded zip>/.ssh/hydejack_8_pro. You have to copy the key file to ~/.ssh (or wherever your SSH keys are located), e.g.:
$ cp ~/Downloads/hydejack-pro-8.5.2/.ssh/hydejack_8_pro ~/.ssh/
It is required that your private key files are NOT accessible by others, e.g.:
$ chmod 600 ~/.ssh/hydejack_8_pro
Then add the following to .ssh/config:
Host hydejack
HostName github.com
IdentitiesOnly yes
IdentityFile ~/.ssh/hydejack_8_pro
Next, open Gemfile in your Jekyll repository and add:
gem "jekyll-theme-hydejack-pro", git: 'git@github.com:qwtel/hydejack-pro-8.git'
In your _config.yml, add:
theme: jekyll-theme-hydejack-pro
You can now continue with Running locally.
Make sure you’ve cded into the directory where _config.yml is located. Before running for the first time, dependencies need to be fetched from RubyGems:
$ bundle install
NOTE: If you are missing the bundle command, you can install Bundler by running gem install bundler.
Now you can run Jekyll on your local machine:
$ bundle exec jekyll serve
and point your browser to http://localhost:4000 to see Hydejack in action.
Continue with Config