JEKYLL
- Linux
About
Jekyll is a trend-setting static html page generator. It’s popular not just for being free and open-source, but also for its simplicity and utility. Written in Ruby, it renders Markdown or Textile templates to build and publish static pages in one go. Also, it would require Ruby and Ruby gems installation. It supports JSON, YAML, TSV, and CSV files for loading content which is then converted by the Liquid templating engine for generating the website for front-end user’s consumption.
Features
Clutter-free and Effortless Site Building
Almost all the website generation cases are covered by auto-generator and Markdown renderer with no gap between what the developer’s action and outcome. Also, at the beginning, the user is free from the burden of configuring Jekyll.
Content friendly
Publishing, updating, and managing content with Jekyll is super-easy. It stores files as text files which can be modified easily. Just like working with the text editor!
Ample Themes and Templates
Its simplicity makes it easier for beginners laying their hands on development and content management. Besides, the availability of a large number of templates makes it enjoyable and encouraging too.
Built-in Development Server
The built-in Development Server allows the developer to experiment with intuition without having to worry about wasting time. Refresh the page and see the changes and updates in effect.
Connectors that Enable Editors
Jekyll websites are connectible to various Cloud-based CMS. Content editors can do their job without coding with the help of connectors like CloudCannon, Siteleaf, Forestry etc.
- Type virtual machines in the search.
- Under Services, select Virtual machines.
- In the Virtual machines page, select Add. The Create a virtual machine page opens.
- In the Basics tab, under Project details, make sure the correct subscription is selected and then choose to Create new resource group. Type myResourceGroup for the name.*.
- Under Instance details, type myVM for the Virtual machine name, choose East US for your Region, and choose Ubuntu 18.04 LTS for your Image. Leave the other defaults.
- Under Administrator account, select SSH public key, type your user name, then paste in your public key. Remove any leading or trailing white space in your public key.
- Under Inbound port rules > Public inbound ports, choose Allow selected ports and then select SSH (22) and HTTP (80) from the drop-down.
- Leave the remaining defaults and then select the Review + create button at the bottom of the page.
- On the Create a virtual machine page, you can see the details about the VM you are about to create. When you are ready, select Create.
It will take a few minutes for your VM to be deployed. When the deployment is finished, move on to the next section.
Connect to virtual machine
Create an SSH connection with the VM.
- Select the Connect button on the overview page for your VM.
- In the Connect to virtual machine page, keep the default options to connect by IP address over port 22. In Login using VM local account a connection command is shown. Select the button to copy the command. The following example shows what the SSH connection command looks like:
bashCopy
ssh azureuser@10.111.12.123
- Using the same bash shell you used to create your SSH key pair (you can reopen the Cloud Shell by selecting >_ again or going to https://shell.azure.com/bash), paste the SSH connection command into the shell to create an SSH session.
Usage/Deployment Instructions
Step 1: Access Jekyll in Azure Marketplace and click on Get it now button.
Click on Continue and than click on Create.
Step 2: Now to create a virtual machine, enter or select appropriate values for zone, machine type, resource group and so on as per your choice.
Click on Review + create;
Step 3: The below window confirms that VM was deployed.
Step 4: Open port 4000 in security group by going to resource group –
- Select your network security group.
- Select Inbound security rules from the left menu, then select Add.
- You can limit the Source as needed or leave the default of Any.
- Limit the Destination as 4000.
- Choose a common Service from the drop-down menu, TCP. You can also select Custom if you want to provide a specific port to use like Port_4000.
- Optionally, change the Priority or Name. The priority affects the order in which rules are applied: the lower the numerical value, the earlier the rule is applied.
- Select Add to create the rule.
Step5: Open putty and connect with your machine. Add IP address of the running Virtual Machine.
Step 6: Login with user name and password that you provided during machine creation.
Step 7: — Starting Jekyll’s Web Server
Move to directory –
sudo su
cd ~/www
Run command –
jekyll serve –host=0.0.0.0
Step 8: Visit server’s IP address and port 4000 to see default web page. Example:
You should see your Jekyll site in the following image:
Enjoy Your Application.
- (510) 298-5936
Submit Your Request
Until now, small developers did not have the capital to acquire massive compute resources and ensure they had the capacity they needed to handle unexpected spikes in load. Amazon EC2 enables any developer to leverage Amazon’s own benefits of massive scale with no up-front investment or performance compromises. Developers are now free to innovate knowing that no matter how successful their businesses become, it will be inexpensive and simple to ensure they have the compute capacity they need to meet their business requirements.
The “Elastic” nature of the service allows developers to instantly scale to meet spikes in traffic or demand. When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.
Traditional hosting services generally provide a pre-configured resource for a fixed amount of time and at a predetermined cost. Amazon EC2 differs fundamentally in the flexibility, control and significant cost savings it offers developers, allowing them to treat Amazon EC2 as their own personal data center with the benefit of Amazon.com’s robust infrastructure.
When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.
Secondly, many hosting services don’t provide full control over the compute resources being provided. Using Amazon EC2, developers can choose not only to initiate or shut down instances at any time, they can completely customize the configuration of their instances to suit their needs – and change it at any time. Most hosting services cater more towards groups of users with similar system requirements, and so offer limited ability to change these.
Finally, with Amazon EC2 developers enjoy the benefit of paying only for their actual resource consumption – and at very low rates. Most hosting services require users to pay a fixed, up-front fee irrespective of their actual computing power used, and so users risk overbuying resources to compensate for the inability to quickly scale up resources within a short time frame.
No. You do not need an Elastic IP address for all your instances. By default, every instance comes with a private IP address and an internet routable public IP address. The private address is associated exclusively with the instance and is only returned to Amazon EC2 when the instance is stopped or terminated. The public address is associated exclusively with the instance until it is stopped, terminated or replaced with an Elastic IP address. These IP addresses should be adequate for many applications where you do not need a long lived internet routable end point. Compute clusters, web crawling, and backend services are all examples of applications that typically do not require Elastic IP addresses.
You have complete control over the visibility of your systems. The Amazon EC2 security systems allow you to place your running instances into arbitrary groups of your choice. Using the web services interface, you can then specify which groups may communicate with which other groups, and also which IP subnets on the Internet may talk to which groups. This allows you to control access to your instances in our highly dynamic environment. Of course, you should also secure your instance as you would any other server.
Highlights
- Excellent support for chronological content like Blogs posts along with an easy naming convention.
- Directory Watcher to track files that change at intervals.
- Classifier for enabling Semantic Indexing with Bayes implementation.
Application Installed
