- Add link macdown for mac#
- Add link macdown install#
- Add link macdown code#
- Add link macdown free#
- Add link macdown windows#
We can clone a git repository with the command `git clone` followed by the address to it.
Add link macdown install#
If we don't have Homebrew and didn't install it above yet, we can install it with the following:
Add link macdown for mac#
The easiest way to install `git` is probably with () (a package manager for Mac OSs). If we do have `git`, let's jump to [**step 4a. If we have don't have `git`, let's go to [**step to install it.
That will return a message with "command not found" if we do not have it. We can check to see if we have `git` like so: We need the program `git` in order to be able to do this. Then we can create a new environment and install jekyll like so: If we don't yet have it, we can get and install conda with the following: () may be an easy path for some folks with Mac Mojave.
Add link macdown free#
If that happens, conda may help, so feel free to try that, or don't worry about it for now, and we'll try installing jekyll again a different way in a little bit. This has not worked perfectly so far, and some folks have had a failure on installing jekyll while the bundler successfully installs. So here we are attempting to install a gem called bundler and the gem that holds jekyll ¯\_(ツ)_/¯ I don't really get all these terms in the ruby world, but if interested at all, I *think* "gems" are individual packages, and "bundler" handles many gems at once. It is going to look something like this following line, but we will need to change the first two "X"s to match the first two digits of the ruby version that we have:Įcho 'export PATH="$HOME/.gem/ruby/X.X.0/bin:$PATH"' > ~/.bash_profileįor instance, my ruby version says `ruby 2.4.1p111 ( revision 58053) `, so I would change the "X.X.0" in the above command to be "2.4.0".
It seems the easiest way to do this is with () (a package manager for Mac OSs), we can install Homebrew with the following:Īnd we can now install a newer ruby like this:Īnd we are now adding that to () with this line, and then refreshing our terminal environment to incorporate this change:Įcho 'export PATH="/usr/local/opt/ruby/bin:$PATH"' > ~/.bash_profileĪnd we want to add one more thing to () before we move on that is based on our ruby version. Installing newer ruby version (if needed) If we have a version >= 2.4.0, then we can go to (). If we have less than 2.4.0, then we need to install a newer version and we should go to (). Jekyll needs to have a ruby version >= than 2.4.0, we can see what we have on our system with this: If this is already installed, running this won't cause any problems, it will just tell us it is, so let's run this:
Add link macdown windows#
If you hit any snags and want some help trouble-shooting, feel free to message me (Mike Lee) on slack or email me: NOTE:** Right now this is only for Mac computers because we haven't gone through it with Windows yet, but I'd start with their (), and please let us know if you have to iron out any snags on the way that might be helpful to others so we can add them here!Įxcept for where noted, this is all performed at the terminal. So here's a walkthrough built off of their documentation with some additional notes of what we've done recently when trying to get this set up. Despite their good documentation, it can be easy to run into some snags still. () is the primary program used to do this, and they have really good documentation. That can be particularly helpful if we want to maybe make our own (), or if we want to make large changes/edits to a site.
Add link macdown code#
This is different than editing a github wiki () – that is easiest to do directly at the wiki with the "Edit" and "New Page" buttons at the top right because there is much less web stuff going on under those wiki pages (less weird rendering things can go wrong, and easy to preview while editing).Ĭhanging a github-hosted site can be done directly at the github code area for it, like (), by editing and uploading files, or it can be done locally at your computer by using `git` to "clone" the repository, making the changes we want, and using a program called () to render our local version of the site temporarily so we can check it out and make sure things are looking the way we expect them to look. This is specfically referring to editing a site (), or the pages at that site like the () (which will be the example here). # Being able to edit our github-hosted site