Github html website doesn't work [404 file not found]

[Mark Kaine]

17 hours ago, tikker said:

I still have no issue even adding a Jekyll theme (apart from that the style doesn't apply to html files). Odd.

 

Does the account name contain weird characters or dots or something that might mess things up?

 

I also see suggestions to push something to the repository. If you have a command line ready you can try an empty commit

Really the only thing that makes sense to me is something was messed up with that html file... i mean thats not unlikely.

 

and well idk anything about these command lines tbh, this is super confusing,  and really the opposite of what im used to from other "file hosting sites", usually you upload something and when you have an update you upload that *separately* either in addition to the previous upload (ie an actual "update") or to replace the old file(s) completely, thats much better for anyone involved and doesn't actually use more data or  anything either... github seems to mix everything into 1 file, so you cant really *replace* something,  seems that way to me at least... i mean i know you can delete stuff, ive seen it, and you can also push "updates" separately in the same repo... but that may be different for the web page thing...  

i mean I'll probably figure it out somehow,  but for now it just seems needlessly complicated for something that really needs just 1 option... "upload"  : p

 

As for the other 2 points,  account name has capital letters, but that shouldn't matter because it eventually actually worked,  with the jekyll theme...

 

and as for the cache, that's a good tip but was probably not the issue either since it worked with that theme right away?

 

 

i mean im tempted to just buy another domain for 10 bucks as that seems overall much easier,  but for something simple like a 100% html site github would make a lot of sense... and i would actually learn something,  with the namecheap web builder on my other website its almost too easy,  even though its also actually fun !

 

 

[tikker]

1 hour ago, Mark Kaine said:

and well idk anything about these command lines tbh, this is super confusing,  and really the opposite of what im used to from other "file hosting sites", usually you upload something and when you have an update you upload that *separately* either in addition to the previous upload (ie an actual "update") or to replace the old file(s) completely, thats much better for anyone involved and doesn't actually use more data or  anything either... github seems to mix everything into 1 file, so you cant really *replace* something,  seems that way to me at least... i mean i know you can delete stuff, ive seen it, and you can also push "updates" separately in the same repo... but that may be different for the web page thing...  

i mean I'll probably figure it out somehow,  but for now it just seems needlessly complicated for something that really needs just 1 option... "upload"  : p

GitHub isn't a file hosting site. It hosts files, but it's function is as a platform to host software managed through a version control system such as git. If you change or overwrite a file that is reflected on GitHub as well. Git will detect that the file has changed and when you push, those changes are incorporated in the remote repository. As far as I know git does upload the entire file and doesn't work through just differences.

 

The point of git and GitHub (and version control in general) is to track changes and be able to easily revert them. It just happens to offer page hosting for a little personal page. That's why you have to "add" changed files (i.e. you select the changes that will happen), "commit" them (i.e. make journal entry describing the changes) and finally "push" them to the remote to incorporate the changes on the hosted files.

 

1 hour ago, Mark Kaine said:

As for the other 2 points,  account name has capital letters, but that shouldn't matter because it eventually actually worked,  with the jekyll theme...

 

and as for the cache, that's a good tip but was probably not the issue either since it worked with that theme right away?

Might depend on what the Jekyll page returns. Can you access the page directly through username.github.io/index.html? That may tell you if it's really not finding it or if there's something just interfering with using that as the main page.