Replace Github with GitHub (#34971)
This commit is contained in:
@ -7,7 +7,7 @@ challengeType: 2
|
||||
## Description
|
||||
<section id='description'>
|
||||
As a reminder, this project is being built upon the following starter project on <a href='https://glitch.com/#!/import/github/freeCodeCamp/boilerplate-advancednode/'>Glitch</a>, or cloned from <a href='https://github.com/freeCodeCamp/boilerplate-advancednode/'>GitHub</a>.
|
||||
A strategy is a way of authenticating a user. You can use a strategy for allowing users to authenticate based on locally saved information (if you have them register first) or from a variety of providers such as Google or Github. For this project we will set up a local strategy. To see a list of the 100's of strategies, visit Passports site <a href='http://passportjs.org/'>here</a>.
|
||||
A strategy is a way of authenticating a user. You can use a strategy for allowing users to authenticate based on locally saved information (if you have them register first) or from a variety of providers such as Google or GitHub. For this project we will set up a local strategy. To see a list of the 100's of strategies, visit Passports site <a href='http://passportjs.org/'>here</a>.
|
||||
Add <em>passport-local</em> as a dependency and add it to your server as follows: <code>const LocalStrategy = require('passport-local');</code>
|
||||
Now you will have to tell passport to <b>use</b> an instantiated LocalStartegy object with a few settings defined. Make sure this as well as everything from this point on is encapsulated in the database connection since it relies on it! <pre>passport.use(new LocalStrategy(
|
||||
function(username, password, done) {
|
||||
@ -20,7 +20,7 @@ Now you will have to tell passport to <b>use</b> an instantiated LocalStartegy o
|
||||
});
|
||||
}
|
||||
));</pre> This is defining the process to take when we try to authenticate someone locally. First it tries to find a user in our database with the username entered, then it checks for the password to match, then finally if no errors have popped up that we checked for, like an incorrect password, the users object is returned and they are authenticated.
|
||||
Many strategies are set up using different settings, general it is easy to set it up based on the README in that strategies repository though. A good example of this is the Github strategy where we don't need to worry about a username or password because the user will be sent to Github's auth page to authenticate and as long as they are logged in and agree then Github returns their profile for us to use.
|
||||
Many strategies are set up using different settings, general it is easy to set it up based on the README in that strategies repository though. A good example of this is the GitHub strategy where we don't need to worry about a username or password because the user will be sent to GitHub's auth page to authenticate and as long as they are logged in and agree then GitHub returns their profile for us to use.
|
||||
In the next step we will set up how to actually call the authentication strategy to validate a user based on form data! Submit your page when you think you've got it right up to this point.
|
||||
</section>
|
||||
|
||||
|
@ -37,7 +37,7 @@ tests:
|
||||
testString: getUserInput => $.get(getUserInput('url')+ '/_api/package.json') .then(data => { var packJson = JSON.parse(data); assert.property(packJson.dependencies, 'passport-github', 'Your project should list "passport-github" as a dependency'); }, xhr => { throw new Error(xhr.statusText); })
|
||||
- text: Dependency required
|
||||
testString: getUserInput => $.get(getUserInput('url')+ '/_api/server.js') .then(data => { assert.match(data, /require.*("|')passport-github("|')/gi, 'You should have required passport-github'); }, xhr => { throw new Error(xhr.statusText); })
|
||||
- text: Github strategy setup correctly thus far
|
||||
- text: GitHub strategy setup correctly thus far
|
||||
testString: getUserInput => $.get(getUserInput('url')+ '/_api/server.js') .then(data => { assert.match(data, /passport.use.*new GitHubStrategy/gi, 'Passport should use a new GitHubStrategy'); assert.match(data, /callbackURL:( |)("|').*("|')/gi, 'You should have a callbackURL'); assert.match(data, /process.env.GITHUB_CLIENT_SECRET/g, 'You should use process.env.GITHUB_CLIENT_SECRET'); assert.match(data, /process.env.GITHUB_CLIENT_ID/g, 'You should use process.env.GITHUB_CLIENT_ID'); }, xhr => { throw new Error(xhr.statusText); })
|
||||
|
||||
```
|
||||
|
@ -42,7 +42,7 @@ You should be able to login to your app now- try it! Submit your page when you t
|
||||
|
||||
```yml
|
||||
tests:
|
||||
- text: Github strategy setup complete
|
||||
- text: GitHub strategy setup complete
|
||||
testString: getUserInput => $.get(getUserInput('url')+ '/_api/server.js') .then(data => { assert.match(data, /GitHubStrategy[^]*db.collection/gi, 'Strategy should use now use the database to search for the user'); assert.match(data, /GitHubStrategy[^]*socialusers/gi, 'Strategy should use "socialusers" as db collection'); assert.match(data, /GitHubStrategy[^]*return cb/gi, 'Strategy should return the callback function "cb"'); }, xhr => { throw new Error(xhr.statusText); })
|
||||
|
||||
```
|
||||
|
@ -7,9 +7,9 @@ challengeType: 2
|
||||
## Description
|
||||
<section id='description'>
|
||||
As a reminder, this project is being built upon the following starter project on <a href='https://glitch.com/#!/import/github/freeCodeCamp/boilerplate-socialauth/'>Glitch</a>, or cloned from <a href='https://github.com/freeCodeCamp/boilerplate-socialauth/'>GitHub</a>.
|
||||
The basic path this kind of authentication will follow in your app is: <ol><li>User clicks a button or link sending them to our route to authenticate using a specific strategy (EG. Github)</li><li>Your route calls <code>passport.authenticate('github')</code> which redirects them to Github.</li><li>The page the user lands on, on Github, allows them to login if they aren't already. It then asks them to approve access to their profile from our app.</li><li>The user is then returned to our app at a specific callback url with their profile if they are approved.</li><li>They are now authenticated and your app should check if it is a returning profile, or save it in your database if it is not.</li></ol>
|
||||
Strategies with OAuth require you to have at least a <em>Client ID</em> and a <em>Client Secret</em> which is a way for them to verify who the authentication request is coming from and if it is valid. These are obtained from the site you are trying to implement authentication with, such as Github, and are unique to your app- <b>THEY ARE NOT TO BE SHARED</b> and should never be uploaded to a public repository or written directly in your code. A common practice is to put them in your <em>.env</em> file and reference them like: <code>process.env.GITHUB_CLIENT_ID</code>. For this challenge we're going to use the Github strategy.
|
||||
Obtaining your <em>Client ID and Secret<em> from Github is done in your account profile settings under 'developer settings', then '<a href='https://github.com/settings/developers'>OAuth applications</a>'. Click 'Register a new application', name your app, paste in the url to your glitch homepage (<b>Not the project code's url</b>), and lastly for the callback url, paste in the same url as the homepage but with '/auth/github/callback' added on. This is where users will be redirected to for us to handle after authenticating on Github. Save the returned information as 'GITHUB_CLIENT_ID' and 'GITHUB_CLIENT_SECRET' in your .env file.
|
||||
The basic path this kind of authentication will follow in your app is: <ol><li>User clicks a button or link sending them to our route to authenticate using a specific strategy (EG. GitHub)</li><li>Your route calls <code>passport.authenticate('github')</code> which redirects them to GitHub.</li><li>The page the user lands on, on GitHub, allows them to login if they aren't already. It then asks them to approve access to their profile from our app.</li><li>The user is then returned to our app at a specific callback url with their profile if they are approved.</li><li>They are now authenticated and your app should check if it is a returning profile, or save it in your database if it is not.</li></ol>
|
||||
Strategies with OAuth require you to have at least a <em>Client ID</em> and a <em>Client Secret</em> which is a way for them to verify who the authentication request is coming from and if it is valid. These are obtained from the site you are trying to implement authentication with, such as GitHub, and are unique to your app- <b>THEY ARE NOT TO BE SHARED</b> and should never be uploaded to a public repository or written directly in your code. A common practice is to put them in your <em>.env</em> file and reference them like: <code>process.env.GITHUB_CLIENT_ID</code>. For this challenge we're going to use the GitHub strategy.
|
||||
Obtaining your <em>Client ID and Secret<em> from GitHub is done in your account profile settings under 'developer settings', then '<a href='https://github.com/settings/developers'>OAuth applications</a>'. Click 'Register a new application', name your app, paste in the url to your glitch homepage (<b>Not the project code's url</b>), and lastly for the callback url, paste in the same url as the homepage but with '/auth/github/callback' added on. This is where users will be redirected to for us to handle after authenticating on GitHub. Save the returned information as 'GITHUB_CLIENT_ID' and 'GITHUB_CLIENT_SECRET' in your .env file.
|
||||
On your remixed project, create 2 routes accepting GET requests: /auth/github and /auth/github/callback. The first should only call passport to authenticate 'github' and the second should call passport to authenticate 'github' with a failure redirect to '/' and then if that is successful redirect to '/profile' (similar to our last project).
|
||||
An example of how '/auth/github/callback' should look is similar to how we handled a normal login in our last project: <pre>app.route('/login')
|
||||
.post(passport.authenticate('local', { failureRedirect: '/' }), (req,res) => {
|
||||
|
@ -38053,7 +38053,7 @@
|
||||
" [6, 7, 10, 7, 6]]</pre>",
|
||||
"<p>See, also:</p><a href=\"https://youtu.be/ftcIcn8AmSY?t=536\" title=\"link: https://youtu.be/ftcIcn8AmSY?t=536\">Four Solutions to a Trivial Problem</a> – a Google Tech Talk by Guy Steele",
|
||||
"<a href=\"http://stackoverflow.com/questions/24414700/amazon-water-collected-between-towers/\" title=\"link: http://stackoverflow.com/questions/24414700/amazon-water-collected-between-towers/\">Water collected between towers</a> on Stack Overflow, from which the example above is taken)",
|
||||
"<a href=\"https://gist.github.com/paf31/9d84ecf6a6a9b69cdb597a390f25764d\" title=\"link: https://gist.github.com/paf31/9d84ecf6a6a9b69cdb597a390f25764d\">An interesting Haskell solution</a>, using the Tardis monad, by <a href=\"https://gist.github.com/paf31\" title=\"link: https://gist.github.com/paf31\">Phil Freeman</a> in a <a href=\"https://gist.github.com/paf31/9d84ecf6a6a9b69cdb597a390f25764d\" title=\"link: https://gist.github.com/paf31/9d84ecf6a6a9b69cdb597a390f25764d\">Github gist</a>."
|
||||
"<a href=\"https://gist.github.com/paf31/9d84ecf6a6a9b69cdb597a390f25764d\" title=\"link: https://gist.github.com/paf31/9d84ecf6a6a9b69cdb597a390f25764d\">An interesting Haskell solution</a>, using the Tardis monad, by <a href=\"https://gist.github.com/paf31\" title=\"link: https://gist.github.com/paf31\">Phil Freeman</a> in a <a href=\"https://gist.github.com/paf31/9d84ecf6a6a9b69cdb597a390f25764d\" title=\"link: https://gist.github.com/paf31/9d84ecf6a6a9b69cdb597a390f25764d\">GitHub gist</a>."
|
||||
],
|
||||
"challengeSeed": [
|
||||
"function replaceMe (foo) {",
|
||||
|
@ -20,7 +20,7 @@ This is essential, because this way you are able to work on your copy of freeCod
|
||||
2. Click the "Fork" Button in the upper right hand corner of the interface ([More Details Here](https://help.github.com/articles/fork-a-repo/))
|
||||
3. After the repository has been forked, you will be taken to your copy of the freeCodeCamp at `https://github.com/YOUR_USER_NAME/freeCodeCamp`
|
||||
|
||||

|
||||

|
||||
|
||||
## Preparing the development environment
|
||||
|
||||
|
@ -13,7 +13,7 @@ The following basic steps are necessary to do the most standard current approach
|
||||
|
||||
1. Maintain a central repo and an active `master` branch.
|
||||
|
||||
There has to be a code repository for everyone to merge into and pull changes from. This can be on Github or any number of code-storage services.
|
||||
There has to be a code repository for everyone to merge into and pull changes from. This can be on GitHub or any number of code-storage services.
|
||||
|
||||
2. Automate the build.
|
||||
|
||||
|
@ -4,7 +4,7 @@ title: Direct Upload to GitHub Via Android Studio
|
||||
|
||||

|
||||
|
||||
[GitHub](https://services.github.com/on-demand/intro-to-github/) is a web based version control which is an amazing tool used by developers to store multiple versions of their projects. There may be times when you may add a feature to your project but may want to keep that bit of code separate. On Github you can create seperate branches and store the necessary code.
|
||||
[GitHub](https://services.github.com/on-demand/intro-to-github/) is a web based version control which is an amazing tool used by developers to store multiple versions of their projects. There may be times when you may add a feature to your project but may want to keep that bit of code separate. On GitHub you can create seperate branches and store the necessary code.
|
||||
|
||||
The following are the steps to be followed in case the project has not been connected to GitHub from Android Studio:
|
||||
|
||||
|
@ -7,7 +7,7 @@ There are several ways to get started with Bulma.
|
||||
|
||||
* Installing the Bulma package with <b>npm</b>
|
||||
* Using a <b>CDN</b> to link to the Bulma stylesheet.
|
||||
* Use the <b>Github Repository</b> to get the latest development version.
|
||||
* Use the <b>GitHub Repository</b> to get the latest development version.
|
||||
|
||||
1) Using npm
|
||||
```terminal
|
||||
|
@ -10,7 +10,7 @@ Bulma is a free and open source frontend CSS framework based on Flexbox. It cont
|
||||
* 100% Responsive.
|
||||
* Modular.
|
||||
* Modern.
|
||||
* Free (Source code on Github).
|
||||
* Free (Source code on GitHub).
|
||||
* growing community.
|
||||
* Easy to learn.
|
||||
* Quick Customization.
|
||||
|
@ -28,5 +28,5 @@ Spark’s RDD (Resilient Distributed Dataset) abstraction resembles Crunch’s P
|
||||
* Data operations are transparently distributed across the cluster, even as you type.
|
||||
|
||||
#### More information
|
||||
* <a href='https://github.com/apache/spark' target='_blank' rel='nofollow'>Spark Github page</a>
|
||||
* <a href='https://github.com/apache/spark' target='_blank' rel='nofollow'>Spark GitHub page</a>
|
||||
* <a href='https://en.wikipedia.org/wiki/Apache_Spark' target='_blank' rel='nofollow'>Wikipedia</a>
|
||||
|
@ -50,4 +50,4 @@ Godot has been used to make a wide range of games such as [Mr Bean - Around the
|
||||
- [Godot Official Website](https://godotengine.org/)
|
||||
- [Godot Docs](http://docs.godotengine.org/en/3.0/)
|
||||
- [Wikipedia](https://en.wikipedia.org/wiki/Godot_(game_engine))
|
||||
- [Github](https://github.com/godotengine)
|
||||
- [GitHub](https://github.com/godotengine)
|
||||
|
@ -9,7 +9,7 @@ title: libGDX
|
||||
libGDX is a free and open-source game-development application framework written in the Java programming language with some C and C++ components for performance dependent code.
|
||||
|
||||
### Overview
|
||||
LibGDX supports both 2d and 3d game development, and is written in Java. In addition to Java, other JVM languages, such as Kotlin or Scala can be used to program libGDX games. At its core, libGDX uses LWJGL 3 to handle basic game functions such as graphics, input, and audio. LibGDX offers a large API to simplify game programming. LibGDX has an informative [wiki](https://github.com/libgdx/libgdx/wiki) on its Github page, and there are many tutorials on the internet.
|
||||
LibGDX supports both 2d and 3d game development, and is written in Java. In addition to Java, other JVM languages, such as Kotlin or Scala can be used to program libGDX games. At its core, libGDX uses LWJGL 3 to handle basic game functions such as graphics, input, and audio. LibGDX offers a large API to simplify game programming. LibGDX has an informative [wiki](https://github.com/libgdx/libgdx/wiki) on its GitHub page, and there are many tutorials on the internet.
|
||||
|
||||
#### Resources:
|
||||
|
||||
|
@ -24,7 +24,7 @@ Gatsby's build is powered by GraphQL and rendered through HTML, CSS, and React.
|
||||
Since Gatsby is built on React you straight away get all the things we love about React, like composability, one-way binding, resuability, great environment and allows you to query your data however you want!
|
||||
|
||||
#### Deploy
|
||||
Gatsby deploys the site on a static web host such as Amazon S3, Netlify, Github Pages, Surge.sh and many more.
|
||||
Gatsby deploys the site on a static web host such as Amazon S3, Netlify, GitHub Pages, Surge.sh and many more.
|
||||
|
||||
### Installation and using the Gatsby CLI
|
||||
* Node: `npm install --global gatsby-cli`
|
||||
|
@ -41,7 +41,7 @@ in which:
|
||||
- `REMOTE-NAME` is the name of the remote repository you want to push to
|
||||
|
||||
### Push to a specific branch with force parameter
|
||||
If you want to ignore the local changes made to Git repository at Github(Which most of developers do for a hot fix to development server) then you can use --force command to push by ignoring those changs.
|
||||
If you want to ignore the local changes made to Git repository at GitHub(Which most of developers do for a hot fix to development server) then you can use --force command to push by ignoring those changs.
|
||||
|
||||
```bash
|
||||
git push --force <REMOTE-NAME> <BRANCH-NAME>
|
||||
|
@ -12,7 +12,7 @@ Now a publisher typically publishes messages with a _routing key_ to something c
|
||||
|
||||
## Getting started
|
||||
|
||||
We're going to cook up a very simple example where a publisher script publishes a message to Rabbit, containing a URL, and a consumer script listens to Rabbit, takes the published URL, calls it and displays the results. You can find the finished sample up on [Github](https://github.com/rudimk/freecodecamp-guides-rabbitmq-tortoise).
|
||||
We're going to cook up a very simple example where a publisher script publishes a message to Rabbit, containing a URL, and a consumer script listens to Rabbit, takes the published URL, calls it and displays the results. You can find the finished sample up on [GitHub](https://github.com/rudimk/freecodecamp-guides-rabbitmq-tortoise).
|
||||
|
||||
First, let's initialize a npm project:
|
||||
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Creating a New Github Issue
|
||||
title: Creating a New GitHub Issue
|
||||
---
|
||||
Before submitting an issue try <a href='https://forum.freecodecamp.com/t/searching-for-existing-issues-in-github/18390' target='_blank' rel='nofollow'>Searching for Your Issue on Github</a>
|
||||
Before submitting an issue try <a href='https://forum.freecodecamp.com/t/searching-for-existing-issues-in-github/18390' target='_blank' rel='nofollow'>Searching for Your Issue on GitHub</a>
|
||||
|
||||
Crafting a good issue will make it much easier for the dev team to replicate and resolve your problem. Follow these steps to do it right:
|
||||
|
||||
1. Go to FreeCodeCamp's <a href='https://github.com/FreeCodeCamp/FreeCodeCamp/issues' target='_blank' rel='nofollow'>Github Issues</a> page and click on `New Issue`.
|
||||
1. Go to FreeCodeCamp's <a href='https://github.com/FreeCodeCamp/FreeCodeCamp/issues' target='_blank' rel='nofollow'>GitHub Issues</a> page and click on `New Issue`.
|
||||
2. **Have a useful title**
|
||||
* Write a meaningful title that describes the issue. Some good examples are `Logging in from the News and Field Guide pages doesn't redirect properly (using e-mail)` and `Typo: "for" instead of "while" loop`; bad examples include `A bug, HELP!!!11` and `I found this bug in a Challenge`.
|
||||
|
||||
|
@ -16,7 +16,7 @@ Typically once the work is completed on a feature and it is recommended to delet
|
||||
|
||||
## The Delete workflow:
|
||||
|
||||
Lets say you have a repo called as `AwesomeRepo`, and its hosted on Github, at a location such as `https://github.com/my_username/AwesomeRepo`.
|
||||
Lets say you have a repo called as `AwesomeRepo`, and its hosted on GitHub, at a location such as `https://github.com/my_username/AwesomeRepo`.
|
||||
|
||||
Also lets assume it has the branches like:
|
||||
`master`
|
||||
|
@ -29,7 +29,7 @@ These are the steps you need to follow to deploy to <a href='https://www.openshi
|
||||
|
||||
* Fill our Git URL and our branch name
|
||||
|
||||

|
||||

|
||||
|
||||

|
||||
|
||||
|
@ -1,4 +1,4 @@
|
||||
---
|
||||
title: Emojis for Gitter and Github
|
||||
title: Emojis for Gitter and GitHub
|
||||
---
|
||||
Gitter IM and GitHub both support a range of cool emoji (emoticons). From `:sunny:`  to `:poop:`  you can express a range of emotions!
|
@ -11,7 +11,7 @@ title: Heroku Deployment Guide
|
||||
|
||||
2. You'll be taken to a dashboard for that app. Click on the Deploy tab.
|
||||
|
||||
3. There you'll be pleased to find that you can connect to a github repo. In the Deployment Method section, choose Github and authenticate by signing into Github.
|
||||
3. There you'll be pleased to find that you can connect to a github repo. In the Deployment Method section, choose GitHub and authenticate by signing into GitHub.
|
||||
|
||||
4. Right below that, fill in your github repo name. (This of course requires that you've pushed a repo to github from either cloud9 or your local machine...and that you've correctly configured it. More on that below.)
|
||||
|
||||
|
@ -26,7 +26,7 @@ Download and install the 4 prerequisites. When installing Python and Node it is
|
||||
|
||||
**The following commands all _have_ to be executed in Git Bash**
|
||||
|
||||
1. Follow the instructions here <a href='https://github.com/FreeCodeCamp/freecodecamp' target='_blank' rel='nofollow'>**freeCodeCamp on Github**</a> and clone the project.
|
||||
1. Follow the instructions here <a href='https://github.com/FreeCodeCamp/freecodecamp' target='_blank' rel='nofollow'>**freeCodeCamp on GitHub**</a> and clone the project.
|
||||
2. Make sure you're in the directory you cloned with GitHub (by default, this is freecodecamp).
|
||||
3. Run `cp sample.env .env`
|
||||
4. Run `npm install`
|
||||
|
@ -14,7 +14,7 @@ Free Code Camp Issue Mods and staff are on hand to assist with Pull Request rela
|
||||
## Setting Up your System
|
||||
|
||||
1. Install <a href='https://git-scm.com/' target='_blank' rel='nofollow'>Git</a> or your favorite Git client
|
||||
2. (Optional) <a href='https://help.github.com/articles/generating-ssh-keys/' target='_blank' rel='nofollow'>Setup an SSH Key</a> for Github.
|
||||
2. (Optional) <a href='https://help.github.com/articles/generating-ssh-keys/' target='_blank' rel='nofollow'>Setup an SSH Key</a> for GitHub.
|
||||
Using SSH can greatly speed up your interactions with GitHub, since you will not be prompted for your password.
|
||||
3. Create a parent projects directory on your system. For the purposes of this document we will assume it is `/mean/`
|
||||
|
||||
|
@ -8,4 +8,4 @@ Sorry that you are stuck. Luckily there are many campers who hang out on Gitter
|
||||
* If the problem seems to be with the site itself, post a screenshot of the issue or describe it well.
|
||||
2. Remember that the people there are campers just like you, so be courteous!
|
||||
|
||||
3. If your problem has baffled everyone in Gitter, try <a href='http://forum.freecodecamp.com/t/searching-for-existing-issues-in-github/18390' target='_blank' rel='nofollow'>Searching for Your Issue on Github</a> for anyone who has posted about a similar issue.
|
||||
3. If your problem has baffled everyone in Gitter, try <a href='http://forum.freecodecamp.com/t/searching-for-existing-issues-in-github/18390' target='_blank' rel='nofollow'>Searching for Your Issue on GitHub</a> for anyone who has posted about a similar issue.
|
||||
|
@ -58,7 +58,7 @@ nothing to commit, working directory clean
|
||||
|
||||
## Common Steps
|
||||
|
||||
1. Once the edits have been committed, you will be prompted to create a pull request on your fork's Github Page.
|
||||
1. Once the edits have been committed, you will be prompted to create a pull request on your fork's GitHub Page.
|
||||
2. By default, all pull requests should be against the FCC main repo, `staging` branch.
|
||||
3. Make a clear title for your PR which succinctly indicates what is being fixed. Do not add the issue number in the title. Examples: `Add Test Cases to Algorithm Drop It` `Correct typo in Challenge Size Your Images`
|
||||
4. In the body of your PR include a more detailed summary of the changes you made and why.
|
||||
|
@ -8,7 +8,7 @@ Free Code Camp learners are encouraged to use <a href='http://www.codepen.io/' t
|
||||
3. **imgur hotlinking:** If you use images from <a href='http://imgur.com' target='_blank' rel='nofollow'>http://imgur.com</a> they will not show up most of the time, this is due to their TOS. A way to solve this is to use an alternate service like <a href='http://postimg.org' target='_blank' rel='nofollow'>http://postimg.org</a>
|
||||
4. **auto reload:** By default, everytime you make changes in the HTML or JS editor windows, the preview window refreshes. You can turn this off and enable a "Run Button", by going to Settings > Behaviour > "Want a Run Button?" and unticking the box.
|
||||
5. **location.reload:** If you run into an issue of your code working in the debug view or in JSFiddle, but not in Codepen editor view or full page view, double check if you used `location.reload()`. If you did, you have to find another way to achieve desired, because Codepen will strip `location.reload` and leave only `()` in your code. Read more <a href='https://blog.codepen.io/documentation/editor/things-we-strip/' target='_blank' rel='nofollow'>here:</a>
|
||||
6. **display images, add css/js files, hosted on Github:** You may want to include in your Codepen project stylesheet, image or js file hosted on a Github. If you add Github link of your file to your settings in Codepen, or to your html/css it will not work out of box. What you need to do is:
|
||||
6. **display images, add css/js files, hosted on GitHub:** You may want to include in your Codepen project stylesheet, image or js file hosted on a GitHub. If you add GitHub link of your file to your settings in Codepen, or to your html/css it will not work out of box. What you need to do is:
|
||||
1. Go to the "Raw" version of the file
|
||||
2. Copy the URL
|
||||
3. Change `raw.githubusercontent.com` to `rawgit.com`
|
||||
|
@ -26,7 +26,7 @@ You can embed Latex in GitterIM. Examples:
|
||||
|
||||
## Details
|
||||
|
||||
<a href='https://github.com/Khan/KaTeX' target='_blank' rel='nofollow'>KaTeX Github Repo</a> LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents. His advantages are noticable in long documents like books, papers or thesis.
|
||||
<a href='https://github.com/Khan/KaTeX' target='_blank' rel='nofollow'>KaTeX GitHub Repo</a> LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents. His advantages are noticable in long documents like books, papers or thesis.
|
||||
|
||||
Gitter uses Katex (an custom implementation of LaTeX) and it can be used introducing the following code:
|
||||
|
||||
|
@ -26,7 +26,7 @@ You can embed Latex in GitterIM. Examples:
|
||||
|
||||
## Details
|
||||
|
||||
<a href='https://github.com/Khan/KaTeX' target='_blank' rel='nofollow'>KaTeX Github Repo</a> LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents. His advantages are noticable in long documents like books, papers or thesis.
|
||||
<a href='https://github.com/Khan/KaTeX' target='_blank' rel='nofollow'>KaTeX GitHub Repo</a> LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents. His advantages are noticable in long documents like books, papers or thesis.
|
||||
|
||||
Gitter uses Katex (an custom implementation of LaTeX) and it can be used introducing the following code:
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Linking Your Account with Github
|
||||
title: Linking Your Account with GitHub
|
||||
---
|
||||
In August 2015, we pushed some changes that caused trouble for many of our campers.
|
||||
|
||||
|
@ -110,6 +110,6 @@ In the next tutorial we will cover some more advanced steps, including:
|
||||
|
||||
<a href="https://webpack.js.org/" target='blank' rel='nofollow'>Webpack website</a>
|
||||
|
||||
<a href="https://github.com/webpack/webpack" target='blank' rel='nofollow'>Webpack Github</a>
|
||||
<a href="https://github.com/webpack/webpack" target='blank' rel='nofollow'>Webpack GitHub</a>
|
||||
|
||||
<a href="https://github.com/webpack/webpack-dev-server" target='blank' rel='nofollow'>webpack-dev-server Github</a>
|
||||
<a href="https://github.com/webpack/webpack-dev-server" target='blank' rel='nofollow'>webpack-dev-server GitHub</a>
|
||||
|
@ -1,14 +1,14 @@
|
||||
---
|
||||
title: Searching for Existing Issues in Github
|
||||
title: Searching for Existing Issues in GitHub
|
||||
---
|
||||
If you still see problems after <a>Getting Help on Gitter</a>, you will want to try to see if anyone else has posted about a similar problem.
|
||||
|
||||

|
||||
|
||||
1. Go to FreeCodeCamp's <a href='https://github.com/FreeCodeCamp/FreeCodeCamp/issues' target='_blank' rel='nofollow'>Github Issues</a> page.
|
||||
1. Go to FreeCodeCamp's <a href='https://github.com/FreeCodeCamp/FreeCodeCamp/issues' target='_blank' rel='nofollow'>GitHub Issues</a> page.
|
||||
|
||||
2. Use the search bar to search for already filed issues that may be related to your problem.
|
||||
|
||||
* If you find one, read it! You can subscribe to get updates about that specific issue by clicking on `Subscribe` in the sidebar. You can also comment on the issue if you have something to add.
|
||||
|
||||
* If you cannot find any relevant issues you should <a>Create a New Github Issue</a>.
|
||||
* If you cannot find any relevant issues you should <a>Create a New GitHub Issue</a>.
|
||||
|
@ -5,10 +5,10 @@ If you still see problems after <a href='http://forum.freecodecamp.com/t/how-to-
|
||||
|
||||

|
||||
|
||||
1. Go to FreeCodeCamp's <a href='https://github.com/FreeCodeCamp/FreeCodeCamp/issues' target='_blank' rel='nofollow'>Github Issues</a> page.
|
||||
1. Go to FreeCodeCamp's <a href='https://github.com/FreeCodeCamp/FreeCodeCamp/issues' target='_blank' rel='nofollow'>GitHub Issues</a> page.
|
||||
|
||||
2. Use the search bar to search for already filed issues that may be related to your problem.
|
||||
|
||||
* If you find one, read it! You can subscribe to get updates about that specific issue by clicking on `Subscribe` in the sidebar. You can also comment on the issue if you have something to add.
|
||||
|
||||
* If you cannot find any relevant issues you should <a href='http://forum.freecodecamp.com/t/creating-a-new-github-issue/18392' target='_blank' rel='nofollow'>Create a New Github Issue</a>.
|
||||
* If you cannot find any relevant issues you should <a href='http://forum.freecodecamp.com/t/creating-a-new-github-issue/18392' target='_blank' rel='nofollow'>Create a New GitHub Issue</a>.
|
||||
|
@ -15,6 +15,6 @@ By 2000, Ruby was more popular than Python in Japan; but as the <a href='http://
|
||||
|
||||
Today, Ruby on Rails is considered a solid web framework; and it has pioneered lot of great practices in web development.
|
||||
|
||||
Similarly a lot of <a href='https://prograils.com/posts/top-10-famous-sites-built-with-ruby-on-rails' target='_blank' rel='nofollow'>popular sites</a> are coded in Ruby on Rails like Github, Airbnb, Groupon, etc.
|
||||
Similarly a lot of <a href='https://prograils.com/posts/top-10-famous-sites-built-with-ruby-on-rails' target='_blank' rel='nofollow'>popular sites</a> are coded in Ruby on Rails like GitHub, Airbnb, Groupon, etc.
|
||||
|
||||
There are various <a href='https://github.com/cogitator/ruby-implementations/wiki/List-of-Ruby-implementations' target='_blank' rel='nofollow'>implementations</a> of Ruby. JRuby (Ruby on the JVM), Ruby MRI (also called CRuby) and IronRuby (Ruby for .NET and Silverlight) are some of the most popular ones.
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Use Github Static Pages to Host Your Front End Projects
|
||||
title: Use GitHub Static Pages to Host Your Front End Projects
|
||||
---
|
||||
**Benefits**
|
||||
|
||||
@ -12,11 +12,11 @@ I love Codepen.io, it's a wonderful, easy-to-use tool for simple front-end exper
|
||||
* Git versioning
|
||||
* Improved screen real-estate experience
|
||||
|
||||
## Git to Github
|
||||
## Git to GitHub
|
||||
|
||||
Since I'm already saving locally, and using git for version control, I figured might as well upload to Github. Plus, Github has a fantastic, free service for front-end projects called <a href='https://pages.github.com/' target='_blank' rel='nofollow'>Github Pages</a>. Just update your repo and your changes are live.
|
||||
Since I'm already saving locally, and using git for version control, I figured might as well upload to GitHub. Plus, GitHub has a fantastic, free service for front-end projects called <a href='https://pages.github.com/' target='_blank' rel='nofollow'>GitHub Pages</a>. Just update your repo and your changes are live.
|
||||
|
||||
How it works is simple. Github checks if your repository has a branch called `gh-pages` and serves any code that's sitting in that branch. No back-end stuff here, but HTML, CSS and JS work like a charm.
|
||||
How it works is simple. GitHub checks if your repository has a branch called `gh-pages` and serves any code that's sitting in that branch. No back-end stuff here, but HTML, CSS and JS work like a charm.
|
||||
|
||||
## First things first
|
||||
|
||||
|
@ -39,7 +39,7 @@ Git is a free and open source distributed version control system designed to han
|
||||
* <a href='http://cbx33.github.io/gitt/' target='_blank' rel='nofollow'>Git In The Trenches</a> - Git In The Trenches, or GITT is designed to be a book that focusses on teaching people to use Git by associating with scenarios that are experienced by a fictional company called Tamagoyaki Inc. Download this book in PDF, mobi, or ePub form for free.
|
||||
* <a href='https://git-scm.com/docs/gittutorial' target='_blank' rel='nofollow'>Official Git Tutorial</a> - This tutorial explains how to import a new project into Git, make changes to it, and share changes with other developers.
|
||||
* <a href='https://git-scm.com/docs/user-manual.html' target='_blank' rel='nofollow'>Official Git User Manual</a> - This manual is designed to be readable by someone with basic UNIX command-line skills, but no previous knowledge of Git.
|
||||
* <a href='https://try.github.io' target='_blank' rel='nofollow'>Try Git Tutorial by Github and CodeSchool</a> - This tutorial is a quick 15 minutes sprint to get started with Git within the browser.
|
||||
* <a href='https://try.github.io' target='_blank' rel='nofollow'>Try Git Tutorial by GitHub and CodeSchool</a> - This tutorial is a quick 15 minutes sprint to get started with Git within the browser.
|
||||
|
||||
## Other Resources
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Writing a Markdown File for Github Using Atom
|
||||
title: Writing a Markdown File for GitHub Using Atom
|
||||
---
|
||||
Markdown is a way to style text on the web, and GitHub users make use of markdown to provide documentation for their repositories.
|
||||
|
||||
|
@ -44,7 +44,7 @@ It began as a simple wrapper around Werkzeug and Jinja and has become one of the
|
||||
|
||||
Flask offers suggestions, but doesn't enforce any dependencies or project layout. It is up to the developer to choose the tools and libraries they want to use. There are many extensions provided by the community that make adding new functionality easy.
|
||||
|
||||
Flask was made in 2004 by an international group of Pythonists called 'Pocoo', as an April Fools joke which was later made into a 'real' thing. According to Wikpedia, it was the most used Python web framework on Github. It is a free and open-source micro-framework written in Python ([view on GitHub](https://github.com/freeCodeCamp/guide/tree/master/src/pages/javascript)). As the Wikipedia states,
|
||||
Flask was made in 2004 by an international group of Pythonists called 'Pocoo', as an April Fools joke which was later made into a 'real' thing. According to Wikpedia, it was the most used Python web framework on GitHub. It is a free and open-source micro-framework written in Python ([view on GitHub](https://github.com/freeCodeCamp/guide/tree/master/src/pages/javascript)). As the Wikipedia states,
|
||||
|
||||
Flask is classified as a microframework because it does not require particular tools or libraries. It has no database abstraction layer, form validation, or any other components where pre-existing third-party libraries provide common functions.
|
||||
|
||||
|
@ -121,4 +121,4 @@ MyComponent.defaultProps = {
|
||||
|
||||
For more information about PropTypes and other docs on React.
|
||||
|
||||
Go to the [Official Site](https://reactjs.org/) and read the docs, or the [Github Repo](https://github.com/facebook/react/)
|
||||
Go to the [Official Site](https://reactjs.org/) and read the docs, or the [GitHub Repo](https://github.com/facebook/react/)
|
||||
|
@ -64,7 +64,7 @@ const store = createStore(
|
||||
```
|
||||
|
||||
### References
|
||||
* [Redux Thunk Github Repo](https://github.com/reduxjs/redux-thunk)
|
||||
* [Redux Thunk GitHub Repo](https://github.com/reduxjs/redux-thunk)
|
||||
* [Redux Middleware](https://redux.js.org/advanced/middleware)
|
||||
|
||||
### Sources
|
||||
|
@ -124,6 +124,6 @@ More resources here: http://www.rubymotion.com/
|
||||
|
||||
|
||||
## What to do after learning Ruby?
|
||||
Every programming language plays an important role. You can contribute to a lot of open source projects or you can apply for some big companies after having a good grasp on Ruby. As many big internet sites such as Basecamp, Airbnb, Bleacher Report, Fab.com, Scribd, Groupon, Gumroad, Hulu, Kickstarter, Pitchfork, Sendgrid, Soundcloud, Square, Yammer, Crunchbase, Slideshare, Funny or Die, Zendesk, Github, Shopify are built on Ruby so there are plenty of options out there.
|
||||
Every programming language plays an important role. You can contribute to a lot of open source projects or you can apply for some big companies after having a good grasp on Ruby. As many big internet sites such as Basecamp, Airbnb, Bleacher Report, Fab.com, Scribd, Groupon, Gumroad, Hulu, Kickstarter, Pitchfork, Sendgrid, Soundcloud, Square, Yammer, Crunchbase, Slideshare, Funny or Die, Zendesk, GitHub, Shopify are built on Ruby so there are plenty of options out there.
|
||||
|
||||
Moreover, a lot of startups are hiring people who have skills with Ruby on Rails as not many programmers try to learn Ruby.
|
||||
|
@ -86,7 +86,7 @@ $ rails s
|
||||
| test/ | Unit tests, fixtures, and other test apparatus. These are covered in Testing Rails Applications. |
|
||||
| tmp/ | Temporary files (like cache and pid files). |
|
||||
| vendor/ | A place for all third-party code. In a typical Rails application this includes vendored gems. |
|
||||
| .gitignore | This file tells git which files (or patterns) it should ignore. See Github - Ignoring files for more info about ignoring files. |
|
||||
| .gitignore | This file tells git which files (or patterns) it should ignore. See GitHub - Ignoring files for more info about ignoring files. |
|
||||
|
||||
A great place to getting started with this awesome framework is reading his [Getting Started page](http://guides.rubyonrails.org/getting_started.html).
|
||||
|
||||
@ -105,4 +105,4 @@ Controller (Action controller) interacts with the views and model to direct the
|
||||
Not only is it free to use, you can also help make it better. More than 4,500 people have already contributed code to [Rails](https://github.com/rails/rails). It’s easier than you think to become one of them.
|
||||
|
||||
## Famous websites use or used Ruby on Rails
|
||||
Twitter was originally written in Ruby on Rails but moved away to a Java-based framework when needing to scale more. Twitch also heavily used Ruby and Ruby on Rails in the early stages but moved certain parts to Go-lang for anything that needed to be high-performant. Many websites that become famous and popular move parts or all of their back-end systems to frameworks based on compiled languages such Java, C++/C, and Go-lang from dynamic languages Ruby, Python, and Javascript (node). This is not always the case. Certain website are able to make dynamic language frameworks scale to as large as they need. Some good example are Github, Gitlab(open-source), Shopify, and Hulu.
|
||||
Twitter was originally written in Ruby on Rails but moved away to a Java-based framework when needing to scale more. Twitch also heavily used Ruby and Ruby on Rails in the early stages but moved certain parts to Go-lang for anything that needed to be high-performant. Many websites that become famous and popular move parts or all of their back-end systems to frameworks based on compiled languages such Java, C++/C, and Go-lang from dynamic languages Ruby, Python, and Javascript (node). This is not always the case. Certain website are able to make dynamic language frameworks scale to as large as they need. Some good example are GitHub, Gitlab(open-source), Shopify, and Hulu.
|
||||
|
@ -19,7 +19,7 @@ The companies that sponsor these programs gain several benefits:
|
||||
### Notable companies and organizations that offer bug bounties
|
||||
- Cisco
|
||||
- Facebook
|
||||
- Github
|
||||
- GitHub
|
||||
- Google
|
||||
- Instagram
|
||||
- Mastercard
|
||||
|
@ -29,5 +29,5 @@ Some useful plugins to get you started are :
|
||||
You may add more plugins to your Vim installation.
|
||||
|
||||
#### More Information:
|
||||
- <a href='https://github.com/junegunn/vim-plug' target='_blank' rel='nofollow'>Github Repository</a> - Vim-Plug
|
||||
- <a href='https://github.com/junegunn/vim-plug' target='_blank' rel='nofollow'>GitHub Repository</a> - Vim-Plug
|
||||
- <a href='https://vimawesome.com/' target='_blank' rel='nofollow'>VimAwesome</a> - Explore Vim plugins</a>
|
||||
|
@ -28,5 +28,5 @@ Some useful plugins to get you started are :
|
||||
|
||||
|
||||
#### More Information:
|
||||
- <a href='https://github.com/VundleVim/Vundle.Vim' target='_blank' rel='nofollow'>Github Repository</a>
|
||||
- <a href='https://github.com/VundleVim/Vundle.Vim' target='_blank' rel='nofollow'>GitHub Repository</a>
|
||||
|
||||
|
@ -10,7 +10,7 @@ Official Site: [https://wordpress.org/gutenberg/](https://wordpress.org/gutenber
|
||||
|
||||
## Block Boilerplate
|
||||
|
||||
Developer [Ahmad Awais](https://ahmadawais.com/) has developed a boilerplate and startup toolkit that can be used to help spin up your own custom Gutenberg blocks. You can learn more about this toolkit in Ahmad's Github repo here: [https://github.com/ahmadawais/create-guten-block](https://github.com/ahmadawais/create-guten-block)
|
||||
Developer [Ahmad Awais](https://ahmadawais.com/) has developed a boilerplate and startup toolkit that can be used to help spin up your own custom Gutenberg blocks. You can learn more about this toolkit in Ahmad's GitHub repo here: [https://github.com/ahmadawais/create-guten-block](https://github.com/ahmadawais/create-guten-block)
|
||||
|
||||
## Block Libraries
|
||||
|
||||
|
@ -194,7 +194,7 @@ After confirming installation your will be on the WordPress Dashboard.
|
||||
### More Information
|
||||
- [WordPress Theme Directory](https://wordpress.org/themes/)
|
||||
- [WordPress Plugin Directory](https://wordpress.org/plugins/)
|
||||
- [WordPress Github Repository](https://github.com/WordPress/WordPress)
|
||||
- [WordPress GitHub Repository](https://github.com/WordPress/WordPress)
|
||||
- [WordPress Support Forums](https://wordpress.org/support/)
|
||||
- [Download WordPress](https://wordpress.org/download/)
|
||||
- [WPHub-WordPress Themes](https://www.wphub.com/)
|
||||
|
@ -3,7 +3,7 @@ title: Difference between Git and GitHub
|
||||
---
|
||||
## Difference between Git and GitHub
|
||||
|
||||
Git and Github are two different things. [Git](https://git-scm.com/) is the [version control system](https://en.wikipedia.org/wiki/Version_control), while [GitHub](https://github.com/) is a service for hosting Git repos and help people collaborate on writing software. However, they are often confounded because of their similar name, because of the fact that GitHub builds on top of Git, and because many websites and articles don't make the difference between them clear enough.
|
||||
Git and GitHub are two different things. [Git](https://git-scm.com/) is the [version control system](https://en.wikipedia.org/wiki/Version_control), while [GitHub](https://github.com/) is a service for hosting Git repos and help people collaborate on writing software. However, they are often confounded because of their similar name, because of the fact that GitHub builds on top of Git, and because many websites and articles don't make the difference between them clear enough.
|
||||
|
||||

|
||||
|
||||
|
@ -41,7 +41,7 @@ in which:
|
||||
- `REMOTE-NAME` is the name of the remote repository you want to push to
|
||||
|
||||
### Push to a specific branch with force parameter
|
||||
If you want to ignore the local changes made to Git repository at Github(Which most of developers do for a hot fix to development server) then you can use --force command to push by ignoring those changs.
|
||||
If you want to ignore the local changes made to Git repository at GitHub(Which most of developers do for a hot fix to development server) then you can use --force command to push by ignoring those changs.
|
||||
|
||||
```bash
|
||||
git push --force <REMOTE-NAME> <BRANCH-NAME>
|
||||
|
Reference in New Issue
Block a user