I'm trying to set up a site with Github pages.
My Github username has a mix of capital and lowercase.
Every way I have tried naming the repo results in it publishing at "username.github.io/username" rather than "username.github.io".
Renaming the repo with all lowercase has the same result. Does anybody have an idea?
The answer is sumple: The domain needs to be included.
Name your repo jrhutson.github.io instead of JRHutson.
This will link your repository to the URL https://jrhutson.github.io and not https://jrhutson.github.io/JRHutson.
See https://pages.github.com/ (step 1) for reference.
Related
I'm looking for a cool template which is using Github Issues for Github Pages.
Actually, When I open Github Pages site, the repository is just for design and config. Only post files are, rarely, content.
And I can use Github Issues because Github Pages site is also one of github repository.
In my case, I'm usally uploading images on Github Issues to embed on my Github Pages site. I don't like including images in repository. It cannot remove any file permanantly. Anyone can find in my commit history.
So I want topic and comment in Github Issues as post and comment in Github Pages for content.
in example,
Jekyll
Github Issues
Template what I expect
post
topic
post
comment
comment
comment
tag
tag
tag
category
project
category
-
author
author
-
milestone
period
Any idea is there?
Thank you.
I know that Django websites contain a secret key which is not to be disclosed to anyone. However, I really want to showcase my website on GitHub, as I feel it is nice. Unfortunately, I am worried about the secret key's security, and if it would be safe to upload that website to GitHub where everyone can see.
The website type is a personal portfolio website that showcases my projects and more.
So, would it be okay to upload my entire Django Project to GitHub? The only sensitive information I can think of would be my superuser information, and maybe my database, where I store all my project Models for displaying on the website. Pretty much all I know I need to guard is my superuser information
The django secret key should not be publicly available (see https://docs.djangoproject.com/en/2.0/ref/settings/#std:setting-SECRET_KEY)
Many sites use an environment variable to set the key.
So your settings file could have something like:
SECRET_KEY = os.environ.get('DJANGO_SECRET_KEY', '')
Have a look at https://github.com/jpadilla/django-dotenv.
You can set your secret_key inside a .env file which you should add to your .gitignore. This means it will not be tracked or added to any git commit, hence, won't be shown in Github.
I just created my first GitHub page.
I created new repository with the name of my user name and I pushed index.html file to master branch. Everything according to documentation.
They said in the documentation, that i can access my index page by http(s)://username.github.io url.
But I get 404 at this url. I have to type http(s)://username.github.io/USERNAME to make it working.
https://vadzvnik.github.io/vadzvnik/ - works
https://vadzvnik.github.io - doesn't work
Maybe someone already had this issue? How to make it working with out username at the end of the url?
Thank you for your help.
Dude, your problem is that you created a repository with just your username so it will be live at https://USERNAME.github.io/USERNAME, to make it appear on your root domain you need to create a new repository or rename it to username.github.io in your case vadzvnik.github.io that will make your website be at https://vadzvnik.github.io. Hope I helped you.
i have a domain navyad.in and i want to host some static pages for that domain on github.
I'm using User pages not the project pages on github.
What i did :
1). created a github repo called navyad.github.io.
2). under master branch of repo i have index.html, CNAME, README.md files.
In CNAME file i have my domain mentioned.
when navyad.github.iois entered in browser, it takes me to the navyad.in. But the index file is not displayed. instead it is going to the page from where i have bought that domain www.net4.in.
what can be the issue ?.
That should mean that:
You did follow the first part of the GitHub help page on custom domain: "Setting the domain in your repo", and GitHub does take you to your actual domain
But you might not have completed the second step "Setting up DNS", which you should do in the net4.in administration page, setting up an A record pointing to 204.232.175.78.
Github pages help page says there are two basic types of Pages available, User/Organization Pages and Project Pages:
In User/Organization Pages the repo must use the username/username.github.com naming scheme and username.github.com is the domain of the page, also, the content should be putted in master branch.
And in Project Pages the gh-pages branch is used to build and publish from.
But in this list of Jekyll-powered blogs, I find this repo, which have a custom domain http://gitready.com, seems doesn't meet the requirement of any one of the two kinds of pages(branch name, and repo naming scheme). But do seems hosted on github, according to this test.
Is this site hosted on github? If it is, why it doesn't meet the requirements?
First, since yesterday (April 5th 2013), this should be username/username.github.io
Second, you can have you own domain, with redirection to the right github address.
See "Setting up a custom domain with Pages".
GitHub Pages allows you to direct a domain name of your choice at your Page.
When you set up a custom domain, the server will automatically create a few redirects for you:
username.github.io ⇒ example.com for user pages
This looks to be an exception to the GitHub Pages rules (as you point out, it appears to be served from neither a master nor gh-pages branch), but the server signature still seems to match that for other GitHub Pages sites. Possible reasons for this include:
Nick Quaranto is a creator of Git Ready and is also one of the creators of Jekyll, the static site generator that powers GitHub Pages, and was able to get GitHub to make a tiny exception for this when it was moved from his User repo to its own Organization repo.
GitReady is strategically important to GitHub (encouraging more Git users), so they made an exception to support it outside of normal Pages rules, as it was an early, popular example of GitHub Pages' functionality