Welcome the continuing series on using Jekyll. In this tutorial we will go through making your first blog post. Overview We will go through all of the steps to create a new post, add metadata such as title/categories/tags/date, and then make it live on the site. Section 1: Creating the file Thr first step is to create a new file to hold the content of the blog post. In Jekyll all of the blog post are markdown files and are stored in the _post directory.
So I brought up a new machine and tried to run my ASP.NET web site in IIS Express that uses Windows Authentication and was greeted with the following error: Error The requested page cannot be accessed because the related configuration data for the page is invalid. Details: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault=“Deny”), or set explicitly by a location tag with overrideMode=“Deny” or the legacy allowOverride=“false”.
Welcome to the first tutorial of a multi part series on blogging using Jekyll on Github. Github has an awesome free option for hosting a blog for you and you can get a blog up and running in 10 minutes or less. This series will cover everything that you to know to host, manage and customized a Jekyll blog that is hosted on Github. Section 1: Overview Github uses the Jekyll engine which turns markdown into static Html pages.
I ran into an issue today on the vagrant IonicBox when I tried to create a new Ionic project at work behind the firewall/proxy even with all of the configurations for npm, git, bower, and bash setup for the proxy as detailed at proxy-configurations. Luckily, Ionic had a fix for this already. Linux All I had to do was put PROXY=http://myserver:myport in front of the ionic start command. PROXY=http://myserver:myport ionic start todo blank Windows
If you have looked at setting up the Ionic Framework or have it done it before, you know on much of a pain it can be, especially when something doesn’t work. Luckily, Ionic offers a free virtual machine called Ionicbox that is already configured with all of the software that you need. Prerequisites: Before you can use Ionicbox you need to install VirtualBox and Vagrant. If you are on Windows and using Chocolatey, you can install both using cinst virtualbox and cinst vagrant.
When you are using npm, bower, and git behind a proxy server you have to do a little bit of configuration. Luckily it is super easy to do these configurations. Almost all of the programs have command line commands to set and unset the proxy server. Updates: Updated 2015-Feb-01: Added running source command for Bash and Ruby Gems section Updated 2015-May-07: Added the Ionic Start command Updated 2015-May-08: Added the Android SDK Updated 2015-Aug-03: Added command lines to set proxy Updated 2015-Oct-20: Added Gradle Windows Command Prompt Current Command Prompt Only set http_proxy=[Your Proxy]:[Proxy Port] set https_proxy=[Your Proxy]:[Proxy Port] Unset Current Session set http_proxy= set https_proxy= Globally as a System Environment Variable Run from an administrative command prompt
I am finally making myself learn the git command line instead of just using a UI so that I can actually understand what git is really doing. Plus I have started playing a lot with the IonicBox and running a Ubuntu vagrant controlled VM for this blog and both of those are just linux shell command prompt only machines. Below are my notes on various commands so that I can stop having to Google each time I forgot one of them.
Updates: 2016-08-13: Added Gradle and VS Code to software installed. Changed from JDK7 to JDK8. Removed Ant. Added Android SDK Apis install to Chocolatey script. Switched suggested emulator to Visual Studio Emulator for Android. If you are like me and just starting to work with the Ionic Framework and don’t already have a machine setup to do Android, iOS, Node, etc development then many of the guides out there leave out a number of steps that you need to do in order to get everything working.
Updates: 2016-08-13: Added Gradle and VS Code. Changed from JDK7 to JDK8. Removed Ant. If you are like me and just starting to work with the Ionic Framework and don’t already have a machine setup to do Android, iOS, Node, etc development then many of the guides out there leave out a number of steps that you need to do in order to get everything working. Even being a Windows user I was able to pretty easily get Ionic working on a Mac.
The Android emulator is super super slow and I could never get it working on my development virtual machine. I thought no problem I will just use Genymotion but due to a video card driver issue on my laptop (not Genymotion’s fault), I couldn’t use it either. I was thinking ok I will just have to use a real device and always have it on me when I do Android development work.