Created
October 7, 2013 12:48
-
-
Save iani/6867369 to your computer and use it in GitHub Desktop.
notes/tips for website publishing on github, using .htaccess, o-blog, orgmode-beamer and other slide presentation tools
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| * web site programming+publishing | |
| ** password protection with htaccess | |
| http://www.htaccesstools.com/articles/password-protection/ | |
| PASSWORD PROTECTION WITH HTACCESS | |
| With .htaccess it is very easy to password protect a folder or directory. The method is called htaccess password protection or htaccess authentication, and works by uploading two files called .htaccess and .htpasswd in the directory you want to password protect. The htaccess file should contain the following: | |
| AuthType Basic | |
| AuthName "Password Protected Area" | |
| AuthUserFile /path/to/.htpasswd | |
| Require valid-user | |
| You only need to change “/path/to/.htpasswd” with the full path to your .htpasswd. Take a look at my article on how to find the full path using PHP. Next you need to upload the .htpasswd file which contains the username and password to enter the password protected folder. The .htpasswd file should contain: | |
| test:dGRkPurkuWmW2 | |
| The above code will allow the user “test” to access the password proteced area with the password “test”. The text “dGRkPurkuWmW2″ is a encrypted version of the password. You will need to use a [[http://www.htaccesstools.com/htpasswd-generator/][htpasswd generator]] to create another password. Each line in the .htpasswd file contains a username and password combination, so feel free to add as many combinations as you like. | |
| The automatic way – Use the generator | |
| You can also just use the htaccess authentication generator to create a htaccess file for password protection. | |
| Also from: http://www.elated.com/articles/password-protecting-your-pages-with-htaccess/ | |
| Protecting a folder | |
| To password protect a folder on your site, you need to put the following code in your .htaccess file: | |
| #+BEGIN_EXAMPLE | |
| AuthUserFile /full/path/to/.htpasswd | |
| AuthType Basic | |
| AuthName "My Secret Folder" | |
| Require valid-user | |
| #+END_EXAMPLE | |
| *** See also: | |
| http://www.elated.com/articles/password-protecting-your-pages-with-htaccess/ | |
| http://www.javascriptkit.com/howto/htaccess3.shtml | |
| http://www.tools.dynamicdrive.com/password/#.UlGCORb8sao | |
| ** publishing a website on github | |
| :PROPERTIES: | |
| :DATE: <2013-10-07 Mon 14:46> | |
| :END: | |
| See: http://pages.github.com | |
| Details: https://help.github.com/articles/user-organization-and-project-pages | |
| Summary: | |
| - There is one single user main web site per github user account: If you have a repository whose name is <username>.github.io, then this repository gets published as a website accessible at: <username>.github.io. For example: My repository named iani.github.com is seen as website at: http://iani.github.io/index.html The .com ending is because of an older version (I assume). If I remake it, it should be with the name ending in github.io. | |
| - Document structure for above github.io site repository: Exactly the same as if you would be publishing the website on the home directory (say ~/public_html) on any apache or similar server site. | |
| - Additionally there can be one web site for each of the repositories in a user's github account. As explaned in https://help.github.com/articles/user-organization-and-project-pages: To create a web site for a project named "myproject", create a repository named "myproject", and then create a branch named "gh-pages" in that project. Put the web site's document files in the gh-pages branch, starting with index.html at the root level of the repository. The site will be made available at: <username>.github.io/myproject. For example if the user name is iani and the repository is named Lilt2 and you create a branch gh-pages in that repository, and put index.html and any further html pages in that branch, then a site will become available at: iani.github.io/Lilt2. | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| *** o-blog | |
| http://renard.github.io/o-blog/index.html | |
| Seems recent, active. | |
| Got it working at: [2013-10-07 Mon 12:58]. | |
| Has many possibilities - but requires more study than my dynsite to configure. | |
| To evaluate further. | |
| **** Examples of o-blog sites (using bootstrap): | |
| http://www.djcbsoftware.nl | |
| http://from-the-cloud.com/en/emacs/2013/03/19_emacs-243-release-and-pythonel.html | |
| http://renard.github.io/o-blog/ | |
| http://docs.chezwam.org | |
| http://mikio.github.io/index.html | |
| http://pharos-alexandria.github.io | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ** Beamer and other slide presentation options :orgmode: | |
| :PROPERTIES: | |
| :DATE: <2013-10-06 Sun 23:37> | |
| :ENTRYTYPE: note | |
| :END: | |
| *** This example from beamer worked fine, and can be found in scratch: | |
| http://orgmode.org/manual/Beamer-export.html | |
| Be careful to use the right command (capital O for beamer export). | |
| *NOTE: Be sure to include the right header.* | |
| *Following is crucial in the header of the file for the beamer export option to appear:* | |
| #+startup: beamer | |
| *** Following non-beamer options would be quite useful for presenting in class: | |
| http://orgmode.org/worg/org-tutorials/non-beamer-presentations.html | |
| Of these, the following were installed and work fine: | |
| *** epresent https://github.com/eschulte/epresent | |
| *** org-tree-slide https://github.com/takaxp/org-tree-slide/blob/master/org-tree-slide.el | |
| *** The orgreveal .js seems also very cool and worth trying out: http://naga-eda.org/home/yujie/org-reveal/#/ | |
| See reveal.js presentation here: http://lab.hakim.se/reveal-js/#/ | |
| See interesting demos here: https://github.com/hakimel/reveal.js/wiki/Example-Presentations. For example: http://zackdesario.com/#/ | |
| Tutorial! http://htmlcheats.com/reveal-js/reveal-js-tutorial-reveal-js-for-beginners/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment