dcycle / dcycleu Goto Github PK

If I have 5 lessons in class 1 and 4 lessons in class 2, I have the following in index.md:

 * [*Class 1: Basics ({{ site.posts 1 | size }} lessons)*](class-01-basics): How to get help on this course; using the command line; setting up a local development environment, ssh keys, and security basics. We'll use [Docker](https://www.docker.com) for local development, testing, and deployment.
 * [*Class 2: Continuous integration ({{ site.posts "2" | size }} lessons)*](class-02-continuous-integration): tools like [Jenkins](https://jenkins-ci.org) and [CircleCI](https://circleci.com) let you know the minute your code breaks. [Coming soon]

The size shows the total for all classes in both cases, I want to filter the list by class.

This package can no longer be found, so it is now impossible to run a local version of DcycleU.

This raises the important issue of Docker not being 100% bulletproof. Docker simply runs the exact same server provisioning script in a consistent manner; however, although generally packages with a given version (ruby1.9.1-dev) remain available, sometimes they stop being available, as is the the case now.

You should probably specify that one should configurate git locally (whatever that means) so that committing does not cause a "*** please tell me who you are" error. It should be specified in the 1.4 section of SSH keys.

Mock objects allow you to develop a connection to external APIs but use a simulation instead of the real thing.

Lorsque je modifie la page de mon blogue les modifications n'apparaisse plus. Pourquoi? Pouvez-vous me rembourser le temps que j'ai perdu (75$ + taxes)? Merci et au plaisir,

This rather cryptic message appears when you manage your CoreOS virtual machine on /path/io/its/original/spot for a time, then move it to /a/new/path and run vagrant up. In such a case, on Mac OS, you will get the error:

NFS is reporting that your exports file is invalid. Vagrant does
this check before making any changes to the file. Please correct
the issues below and execute "vagrant reload":

exports:2: path contains non-directory or non-existent components: /path/io/its/original/spot
exports:2: no usable directories in export entry
exports:2: using fallback (marked offline): /

What is happening here is that Vagrant uses the host system's NFS mapping scheme to map /path/io/its/original/spot to the shared folder on your Vagrant machine, but doesn't update that path when you change the location of your box to /a/new/path.

This mapping information is stored in a file called /etc/exports on your hosts, and the host will remember the initial location of your VM.

You can look at the contents of that file by typing cat /etc/exports and you will see there the out-of-date path. You can edit that file to remove the out-of-date lines, or you can delete the entire file if it doesn't contain anything you want to keep: sudo mv /etc/exports /etc/exports-backup will remove the file from its expected location and make a backup so you don't lose its contents.

For now we need to run:

./scripts/dev.sh

To build the container, and then every time a change is made we need to run:

./scripts/jekyll-build.sh 

I'd like changes to occur automatically, in the background.

I tried these approaches but they don't work for me:

jekyll build --watch
jekyll build --watch &

Other Jekyll-Docker projects such as this one might have some insight.

Until then it is necessary to run

./scripts/jekyll-build.sh 

every time a change is made.

I personnally use Smultron 6, mostly because I can choose the proper coding scheme of the text file that I am opening and because I like the search and replace interface. I tried textwrangler before but do not remember what feature convinced me to stop using it. I also used to be fond of taco html for web development.