What is Reddit's opinion of
GitHub Pages?
From 3.5 billion Reddit comments
100 reviews of this app found across Reddit:
I don't understand people who post web stuff without posting live demos. Or people who post .gifs as "demos", or youtube videos. Give me the damn page. You can host it for free on github even:
Live demos please...
I don't believe you have to "open source" for Github Pages. You should be able to host a project with any license. For it to be free (including the account) then the code will have to be public, but not open source.
If your code is just JavaScript/html, you might consider making a GitHub project page for it: https://pages.github.com
It's free, hosting to thousands of viewers won't be a problem, and has the added benefit of open sourcing your code for future bragging rights :)
I'm surprised a lot of people don't know about this, but github allows you to make a free website: https://pages.github.com/
Just make a repository as <yourusername>.github.io and throw in some html and css and you're done.
Edit: Here, even quickly wrote up a very very basic page for you.
- http://pastebin.com/rwqTHmek - save this text into a notepad and change the file type to '.html' , usually you would call this 'index.html'
- http://pastebin.com/0Cw3AsNm - save this text into a notepad and change the filetype to '.css' , make sure you call this file 'styles.css'
Then, just make sure both files are in the same directory. Or, in GitHub more specifically, put these files in the same repository. Fiddle around with the HTML first, get the text the way you want it, then try playing around with the colours and such in CSS. It's dead simple stuff. Change the font by changing the 'font-family' value, the bit that comes after the colon, after the 'font-family' property.
Anyway, not gonna give a whole lesson here lol but I encourage you to use Google, but if you need help with anything specific just ask man.
Edit 2: Should note that if you want to test around with it before you put it up on GitHub, just make sure both files are in the same directory on your computer and open up the html file in any browser. I use chrome, but I didn't use anything complex so it should show up fine on all browsers. This way it's a lot faster than waiting for it to change on your GitHub page.
Edit 3: I know nothing of SEO (search engine optimization), so it would be prudent to ask someone (or Google) how you can make your page very visible to search engines.
Set it up at name.github.io. Every account get's one.
Or if you buy a domain name you can still host for free on github.
http://www.curtismlarson.com/blog/2015/04/12/github-pages-google-domains/
Free, reliable, no BS. This is exactly what you're looking for. You are not going to get a free domain anywhere though without paying for something.
EDIT: Okay, I am wrong. There are some domains that are free.
Github has a free web hosting service: github pages. You domain would then be something like repository.github.io, however, you could change this buy purchasing a domain name on something like Namecheap and changing the domain in your github repository settings.
If you know basic HTML and CSS (or even if you don't - you can use Jekyll and write your pages in Markdown), you can create a website using GitHub Pages. I find it's nice to have complete control over the content on my website. It's also free.
Like others has said, I think it best not to overthink it. My first iteration wasn't really pretty, but it gave me a base to work on and keep improving.
Generally a static page (or static pages) is all you need for these types of websites, so feel free to check out free hosts such as GitHub Pages. That will accelerate development (and help offset costs!)
Here is my current portfolio.
For something that simple, look into shared hosting from someone like Dreamhost.
Once you're in, you'll upload your files to the server and everything should work once uploaded. Assuming you have a index.html (you said you do).
You'll need a domain name setup and pointing to your server but you can do all that typically with your host.
I wouldn't go with a Digitalocean setup since it sounds like you're very new to this server management thing. Shared hosting is what you need until you get more experience setting up and securely managing a server.
You could probably use https://pages.github.com as well. Which is nice and free if you're already using Github.
github.io sites are just project landing pages that allow the developer to create their own custom landing pages instead of linking directly to the source code on Github. github.io is run and maintained by Github.
Also, quick-start guide to getting your own website (so you can host as many cat pictures as you want :p):
Method 1: Free, but basic. Probably the best option for you right now.
Visit a free website builder, like Google Sites, Wix, Weebly, or Squarespace.
Add cat picture.
Method 2: Paid. More control over your content.
Get a domain name (fairly cheap, my own is $1/month from Google Domains). This is your web address, like google.com or piazza.com.
Get a website host -- this is the server space for your website. Do some research to find out which host is best for you. There's a free one called Viewen that I used for awhile, but their main server is in India so the loading speed isn't that great. Hosts that you pay for will have closer/better servers, generally speaking (or at least they should!). There are a few free ones online, but have more advertising and stuff.
Upload your HTML/CSS/JS files to your website host. Visit your domain name. See cat.
Method 3: Free, but requires a little more technical skill.
Get a Github account.
> And having a registered .com (I have one on godaddy, 7 dollars a month is pretty affordable) where you can show off your work is definitely a plus.
Even better would be to pay $10/year for a domain off namecheap, and host your site using Github Pages for free. Can also just stick to the free domain you get (username.github.io).
Github pages are free and easy to use
I use them to host my processing sketches so that I can share them easily while not losing any of the interactivity.
Buy a domain (Google Domains is cheap and easy to use), and use a free Github account to host it: Github Pages.
You'll have to learn Git if you aren't familiar with it, but it's a super powerful tool any dev should know.
If you want something like a blog, you can use Jekyll. Fair warning it's a bit more effort than just static html/css.
> I can't afford hosting so building example websites for a portfolio isn't happening
No excuses. Github pages. It's free.
> and there seem to be millions of other junior developers applying for the same jobs that I am...
They are. Set yourself apart. Doing a few Codecademy or Treehouse courses isn't going to do that.
> Is there a trick i'm missing or is it just super hard to get your first job in?
There is no trick, you have to prove you can code. You just have to keep working at it until you get that first job, and yes, it is super hard to get that first foot in the door. But once you do, it's much easier to get that second foot in the door.
Hi. I just moved my blog this weekend to Jekyll. Write posts in markdown and build static site. I made a small post about my move. http://topswagcode.com/2018/07/13/Moved-to-jekyll/ You can still make a dotnet core webapi and make webapp that uses your api.
I have even shared all the code for the blog online, so you can see how the structure is.
https://github.com/kiksen1987/blog
And best of all there is free hosting at https://pages.github.com
Just write me a message if you have any questions.
@/u/Seminko, I don't suppose you would like to post the source online to Github? It would provide a free host for your files and you can also use GitHub to handle your website auto-update requests: https://pages.github.com/
Maybe something like this is what you need: https://github.com/J2TeaM/autoit-updater
It can be a lot cheaper (or more expensive) to run a website than $600 a year. (E.g. you can use GitHub Pages to host a static website for free; and you can buy a domain for a few tens of bucks a year if you want mydomain.com instead of mydomain.github.io.)
The reason why you would host it on the IC is exactly because it's more secure (with most hosting solutions, if a hacker gets into a single server they can make whatever changes they want to your website); more reliable (there are at least 7 servers that serve your website) and faster (those 7 servers are distributed around the world, so there's bound to be one close to wherever your users are viewing it from).
Regarding costs on the IC, if you're talking a personal website (that gets hundreds or thousands views a month) then your costs are most likely going to be determined by storage. As already mentioned elsewhere, storage cost on the IC is on the order of $5 per GB per year. A million views a month would likely not be a lot more expensive (although I'm too lazy to look it up now). (o:
There are many places you can do this. A free and relatively easy option is to use github pages: https://pages.github.com/
This gives you the ability have html, css, and javascript based sites with no back end.
I hope this helps you get up and running.
There are many directions you can go. Not sure if this suggestion is the best, but I'll make it because it's completely free: github. You can host a static website on github with a custom domain completely for free. It's awesome because you don't have to worry about traffic, and they also don't require a "hosted by github" or anything like that.
The downside to this is it will take some learning. You'll need to learn how to use git a little bit, and also would need to build your website from scratch. However, there are many static site generators that can help a lot with the latter.
EDIT: another pro to github: unlimited space. I have a page on my github site with over 50 videos on it (the videos themselves are hosted on my github site, many many megabytes). Github don't care.
No, you're much better off just putting your pure HTML and CSS skills to the test and building a site with a bunch of static HTML/CSS only pages. You can host for free on GitHub Pages https://pages.github.com/. Until you're comfortable with the command line on your computer, you can do all of the file creation and editing right on GitHub (it has a decent text editor).
Your goal should be to practice building various different layouts with various techniques (floats, flex box etc), and practice with making responsive websites (e.g. sites that look good on all devices). You should become very comfortable with HTML & CSS.
Once you're done with that, start learning JavaScript. Start building single page applications with it, and then to start testing your skills, start utilizing various 3rd party APIs, like Google Maps, Firebase, etc. You can build a lot using just JavaScript and 3rd party APIs, without needing a server.
Then when you're ready to work on server-side programming, you can continue using JavaScript with Node. But you'll also want to be sure you're getting comfortable with the command line and git.
Also, if you want a simple server with a real life url you can always use github pages. https://pages.github.com/
It's free and let's you practice using git at the same time. The url has to match your username but at least you have a website that you can show other people.
I know this isn't really the question your asking but it is one solution and I find it much more inspiring if it's a real website that I can show anyone.
Considering your site seems to just be static files. If it is on GitHub, just set the repo up on GitHub pages. https://pages.github.com . If you have a custom domain in mind you can use it... Or it'll just follow the username.GitHub.io/repo-name pattern.
First create a repo with the name: username.github.io
Now any new repos you make, go into settings and and scroll down to enable GitHub pages.
That should be it.
I thought it was a nice read! Even though I sort of knew a bit of the concepts you talked about, I definitely learnt something with the way conversions and traits could be used, and how everything worked together. Now I'll end up keeping that in mind for any future Rust code, thanks :)
If you plan to write more, I would second the use of gists, or maybe even better, just markdown files in the repo instead of creating issues. Not that it really matters. You could also make use of github pages.
You might want to check out Lifehacker's list of 5 best personal landing pages. Alternately, GitHub Pages is a decent place for hosting your stuff without necessarily purchasing a domain and hosting.
What languages do you know? Your resume does not make it clear. Also you seem to like learning so why do you not have your own website can be made for free with GitHub Pages.
Github pages: https://pages.github.com/
​
I've been teaching myself some HTML and CSS over the new year period. This has been kind of an experiment with my new skills, and I wanted somewhere I could host the HTML directly for free. Honestly this was just the only one I've found that works - every other service seems to want to build a website for you instead
​
I guess it's a bit weird that it also hosts the source code as well. Maybe I should have put an easter egg in there or something? I'll keep it in mind for next time
Depending on what you want to work with, you could take a look at Github pages - it's basic and free hosting directly from your repository.
It doesn't support backend stuff nor databases, but there are other external solutions you could use for that.
Outside of that, learning how to use git in and of itself is already incredibly useful.
Hosting a website consists of two parts:
A webserver. This is a computer that your browser sends requests to, asking for "example.com". The computer then responds with the data requested.
A domain. This is the root part of the domain - e.g.
reddit.com- and all it does is translate into an IP through a process called a DNS lookup (e.g.reddit.combecomes151.101.1.140).
You already have both a webserver and a domain through your university - your university has a server set up to listen for "universityname.com". When that server receives a request it looks at the rest of the URL (the ~username/... part) and figures out which file it should serve using that.
You might be thinking, "if I buy a custom domain, can I simply point it to the university's web server?". Odds are, you can't. When the server receives a request for "example.com", it won't have any idea how to figure out which files to serve.
What you need is a webserver that knows how to listen for your domain. There are generally two options if you want your website to be out on the internet for the world to see:
GitHub Pages is free, and lets you host static content. That is, if your website doesn't require any server-side processing (and all it is is some HTML, CSS and JS files), you can host it on GitHub Pages. They have a feature built in that allows you to use custom domains, which means that it will work with your custom domain.
Rent a server. This costs a bit of money (usually ~$5 pr. month) and takes a lot more know-how to setup and control (although not a lot), but it also allows you to run non-static websites. If your website requires server-side processing (e.g. store data in a database), you'll have to rent yourself a server.
You should get a blog, so that all your articles are collected into one place. (Even just throwing the markdown files into a basic Github pages blog would be better than the only record being the reddit history. :) )
Well, it's hosted on Github Pages but the websites are built with Jekyll, that has themes. Github Pages themes are just Jekyll themes. Here is the list of supported themes on GHP: https://pages.github.com/themes/
The beauty of CSE is that you can develop a portfolio using only a computer. To differentiate yourself from the crowd, spend a month developing a personal project, develop custom portfolio website using https://pages.github.com/ and put your personal project on it, contribute to open source projects on github. Put the code for everything up for public use on your github page and then include your github page and portfolio on your resume.
I've spoken with CSE recruiters over Reddit before and they have told me that an astonishingly small number of applicants will include a github page with their resume, so those that do are instantly moved into the "Worth considering" pile.
I'd like to add to this, for really easy free hosting check out https://pages.github.com/, every account gets one free site and all you have to do it put it on github---you won't find an easier way.
FYI- You can use GitHub Pages to host a static website, for free, and straight out of a repository. You can then use a service like Namecheap to buy a domain (jsoncaserta.com, etc.) and simply forward visitors to your GitHub pages.
And, as /u/RodionGork suggested, a GitHub (or BitBucket) portfolio will go a long way. A webpage is nice, but most employers looking for CS grads are more interested in a vibrant portfolio than a pretty webpage.
I'm a big fan of Middleman. Static site generators like Middleman, Jekyll, and a slew of others just make sense for most sites. The page content rarely ever changes once published, so why involve server-side languages, DB queries, etc? That just adds needless overhead and slows the site down.
Static generators are super simple too, since most support markdown for writing posts/pages. And with the ability to host them on Github pages for free - meaning you get a CDN and your entire site is backed up and versioned at zero cost... it's a no brainer.
If you want to start with minimal cost, I'd recommend using Github Pages. You're very unlikely to screw things up or open a large security hole on a static-generated website. Additionally, it's on GitHub, which tends to make a good impression.
If you want a domain name, pages can also have domain names.
I think having a personal website is a good idea, it's a good way to show your personality too (it's pretty fun to make imo since you can make it personalized)! I used Github Pages for my website
This seems like a job for GitHub or a similar site, in both aspects.
> I want to make multiple websites for my portfolio but I don't want to pay for multiple domains.
With GitHub Pages you can create a repository that's actually a simple HTML/CSS/JS website. There's no database connectivity for more complex sites, but for something like a personal portfolio it is pretty easy and has just enough power. If you'd like to make it slightly more powerful you can try using Jekyll (a static site generator that uses Markdown to define pages) with plugins -- the plugins give Jekyll much more power than it would normally have, though IDK if they have things like DB access or etc.
As for working on your friends page the "version control" of GitHub and other services, or just the regular ol' programs like Git itself, could help greatly depending on what kind of site it is. You can have your copy of it separate from his and once you know it's stable deploy the code to his server (likely by hand, unless y'all can somehow set it up to automate that), and you can continue to work on it at your leisure without messing up his site.
Of course if the site is using a database or other more complex technologies or remote connections this complicates things greatly and it may in fact not be possible to test the entire site this way. In that case the easiest way I can think of would be to create an access-controlled area for your version of the site which only you two and any select testers can even access.
I host my portfolio on GitHub Pages. I've seen a few other UXers host through it too. My experience with it was pretty much hassle-free. There are simple instructions on https://pages.github.com/ and anything not there is easily found through Google or on Stack Overflow. It took me at most an hour to set things up iirc.
The one downside I can think of is that employers can cycle through your folio revisions on GitHub, but this hasn't been an issue for me.
If you have a good-looking free template to use, or your own good-looking theme already (or easily) built, then I'd say Pages is a great choice.
You can use Github Pages to host your html and css files for free under a .github.io domain for free. If you want to have your own domain like a .com or .me, etc. you will need to buy a domain name and pay for web hosting from a place like Hostgator.com.
If you're more technically inclined, you can self-host the web site on your own server for free and just pay for your domain name or use a free service like DuckDNS to get a yoursitehere.duckdns.org name for free. Check out /r/selfhosted for some more info about that kind of thing.
Well, that's a shame if it's true. Anyhow, if people are interested I might be down to put together a new site for the Mandela effect. My idea was to host it using GitHub Pages since that would provide a generous monthly bandwidth limit for free. This would also force it to be open source, giving others the ability to easily contribute, mirror and eventually fork the site if I'm unable to continue working on it.
If this is something people are interested in, let me know. Should be relatively easy to get something up over the weekend.
Try Github Pages it's free hosting for all you projects. Your domain becomes yourusername.github.io/yourproject and if you want to go fancy you can add a domain to your project.
If you get lost send me a message when you have a Github account and I'll point you in the right direction.
Hope it helps,
Firstly, get paid or barter. When you offer something for free, the client often doesn't realize the value of the resource which results in a unpleasant business relationship.
In terms of hosting/tech stack, I'd consider using one of the Ruby based static site frameworks like Jekyllrb or Middleman. These will allow you to expand your Ruby dev chops but also allow you to host for free or VERY cheaply (S3).
Domains
To put it simply, domains are the web addresses like reddit.com, facebook.com etc. when you're buying a domain, you're only buying the name. You still need to point the domain somewhere or it won't work.
For this, you need to have some kind of webhosting or a server. GoDaddy both sells domains and web hosting, but they're separate products and both cost separately. Usually you buy those on a yearly basis, once you buy a domain it's not yours forever, you still need to pay for it every year or so.
Hosting
There are places that offer free webhosting too, Github Pages allows you to run 'static' websites that don't require server side languages, databases or other kind of dynamic funtionality. If you only plan to write HTML, CSS and maybe some javascript, then it should be fine. https://pages.github.com/
If you want something like databases you'll need a webhost. There are a ton of different ones and I can't really recommend any as they differ in pricing and what they offer, it's kinda up to your needs.
If you're brave, you can rent a digital server. They go for as cheap as $5 a month on Digital Ocean. It requires some more know-how, but running your own server is extremely satisfying and you get a way better bang for your buck than with webhosts. https://www.digitalocean.com/
If you're a student, you'll also get $100 credit to Digital Ocean which should give you a server for 1.5 years and you also get a .me-domain for free. https://education.github.com/pack
If you have any questions, I'd be glad to help you out. If you decide to use Digital Ocean I also have an affiliate link you can use if you want to support me :)
I agree. Collapsing sections would make this doable. You'd start out by seeing a list of fairly high level explanations ("read keyboard input", "get IP from DNS", etc). Clicking each explanation expands the subcontents, revealing more detailed instructions. This could be repeated for a while.
It's pretty much like how file trees work. Here's a simple example (not my code -- result of a quick google search). Wouldn't be doable with Github markdown, but Github pages could do it.
There are two ways.
The first way is to use their built in page maker: https://pages.github.com/
The second way involves uploading your own html content to the gh-pages branch within your GitHub repository.
You could host your website on https://pages.github.com/ for free (if you decided to go that route). It's super easy to make a barebones html/css website with all the resources and templates now-a-days.
There are a ton of free hosts you could probably use for this, but if you'd prefer to keep it private you could always fire up an XAMPP server on your desktop, which you'd be able to access at home on your own network - it would be possible to access from elsewhere by opening port 80 on your router, but that can come later. Just leave it running in the background and you shouldn't see too much of a performance impact. This gives the added benefit of PHP support if you ever want to start learning more about the backend (PHP is a great language to start with when it comes to this because it can embed directly into HTML).
If you'd prefer you could go the GitHub Pages route, which will be a bit more complicated to start but you'll learn a very valuable tool - git. This is incredibly handy for managing file changes, and I highly recommend learning the basics early on.
Hope this points you in the right direction :)
I'd also consider using GitHub Pages for this repo. It'll let other developers see the app first without cloning the code and running it locally. And best of all its free!
His original comment was "Git?" but he Ninja edited it. (twice it looks like lol)
Git is source control software. Source control is how developers work together on a project.
Github is a place you can host Git projects. It's not affiliated with the software at all, it is just the most popular place to host it. There is also Bitbucket, GitLab, or you can host it yourself (don't do this).
If you use GitHub though, you can host your project for free for users to visit if it's a static site directly from your repo. https://pages.github.com
I'm not sure if they'll let mech students join the Computer Science Club but if you can, that's an option. They provide you with a server you can host stuff on.
Maybe this also might help but I'm not sure how to do this now that Nexusmail is gone.
Also for anyone else interested, if you're in CS or SE (or math in general?), you can host your website on linux.student.cs.uwaterloo.ca.
EDIT: If you live at 181 Lester, you can contact Tri-Shitty and they'll flash your router firmware such that you can set up port forwarding. I have a shitty little RPi server but it's not reliable at all 'cause, you know, Tri-Shitty.
EDIT2: GitHub Pages?
Have you looked in to static site generators? I personally like Jekyll and it is a fun way to built simple websites with just HTML and CSS, with just a little bit of logic sprinkled in, so like you said you don't have to update the header in for different places.
If you are use for learning something new I can highly recommend it. Check out the this video by CSS Tricks that helped me get started.
And when you are done you can even host it on Github for free ;) with the help of Github pages
hope it helps,
>Does the hosting a domain usually happen through separate services?
Yes and no. Some hosts, like dreamhost can also be your domain name registrar.
>How would I go about using the .html files I have to display on the site?
Your main html file should be named index.html. Once you FTP/get the files on your host. Going to your domain name in a browser, assuming everything is setup and working, your domain name will default to your index.html file.
>Is there a different way entirely I could go about getting critiques for my site?
Every Friday, this sub has a Feedback Friday event. Post the information there.
>Are there any guides out there that explain this stuff?
I don't have any off-hand to recommend but feel free to PM or ask here.
>I want to get critiques on my newest website, and sending a .zip to people and asking them to extract it isn't the most reasonable thing.
You're correct, it's not at all. If you want people to review your code, using a service like Github is recommended. Plus you begin building your developer resume. Github also has a service called Pages that will probably work for you, as I'm assuming your site is just HTML, CSS, and JS?
If you don't want to spend money on hosting your website. You could only buy a domain and use github as your hosting. But it can only be a static website. https://pages.github.com/ The advantage of this is that you get a free CDN and a lot of bandwidth.
And for your blog you can use either Jekyll with github or tumblr for easy WSIWYG blogging and just point blog.[mydomain].com to tumblr https://www.tumblr.com/docs/en/custom_domains
Not to sound like a jerk here at all man, but it sounds like there's some knowledge missing in your head - you've got a gap that needs filling before you'll understand this.
So, when you type in example.com, your computer looks up an entry in DNS ("Domain Name Service" - this is a topic unto itself so just accept it for now! :) ) and then forwards the request over HTTP - HyperText Transfer Protocol - to the server that DNS tells it to.
When the request gets to the server, the server can do whatever it wants with that request. Typically, there's web server software engineered and configured to look for files in a specific place on the server and then load them and send them to the computer that requested them. So if you go to example.com/something.html, the server looks for something.html in some pre-configured place and if found, sends it to you.
So now that this is out of the way, the question is: where do you put these files? Where you put them on the "server" and how they're uploaded differs between web hosts.
Squarespace is more than just a typical web host; they're a platform for content management and working with their platform isn't as simple as uploading stuff via cpanel or FTP. You'll have to read their documentation, and if what I gather from a quick read is right, probably copy-paste sections of the HTML source code you've written into their web-based front end editor in what they call "blocks" (I think).
Bottom line: this is Squarespace-specific.
Now, if you have all the source code, images, everything you need, and you don't need the content editing capabilities in Squarespace or to run any code on the server (e.g. sending email, etc.), you can just use GitHub Pages to host the files statically, as long as you can use git source control. That's basically free.
Good luck!
Jekyll is a static site generator that uses ruby. It uses the liquid template engine along with your own markdown (also textile/LaTeX), html, and css to make completely static pages.
You can find templates on the internet if design isn't your thing.
As a bonus, you can get free Jekyll site hosting through Github Pages.
Depends what your goals for the content are.
If you want to share your code and see the results, use https://jsfiddle.net or http://codepen.io.
If you want a more standard hosting setup to just share a URL hosting your content, use https://pages.github.com.
Dropbox isn't a CDN. It's pretty much the opposite. They take resources down if they get too many hits.
Get some cheap webspace, use GitHub Pages, or use something which pulls your stuff from Dropbox like Brace does.
GitHub Pages is aimed at developers, is free and hosts your .html, .css and .js files :)
It's expecially comfortable if you need to host a website for your open source project or if you just need to show off something simple and static.
Check out Github-Pages which have support for Jekyll, a static site generator, plus free hosting and custom domain support. Jekyll is built to support writing blogs in Markdown among other things, and is very easy to get into.
Digital Ocean's cheapest VPS is $5/mo and you can put files on it just about any way you want.
I know you said you hate git, but if your website is completely static and non-commercial, github will host it for free. I have my personal site hosted through them. I've never had an outage, even when the github service was offline.
Probably not that necessary, but you can run one for free using Github Pages if you're savvy enough. Just have to buy the domain somewhere, which is usually cheap enough to be negligible.
I'm not sure if it fits your vision, but I think you could accomplish this for free with github.
Github Pages allows you to host a static website for free. (Meaning you don't need to pay for S3. It's not at lot, but still).
The CORS/ loading part could be improved by using Github Actions. This allows you to run arbitrary code on a docker container (2000 minutes per month for free). I'm not sure what the best implementation would be. You could in theory parse all builds from an index (like dt's github page, or the lists on metabattle) and store them in the repo and just let that run every day. That way your github page contains all the data in a cache that you can regularly update, thus you don't need to query the actual pages.
Anyway, good luck with this.
Depends on what type of hosting you need?
If you just need something to host a webpage with only HTML, CSS and frontend JavaScript, then you can use GitHub Pages which is free even if you're not a student.
If you want cloud/server hosting, then the student pack provides credits for Microsoft Azure, Amazon Web Services (AWS), Heroku and DigitalOcean.
There's also web hosting via EducationHost part of the student pack.
The best alternative is Github Pages, let each developer unleash their own creativity in publishing their blog. Is this centralization of all content in one place really necessary?
I've seen a few games available to play on GitHub.
I think these games were using GitHub Pages to achieve that.
I haven't personally used this to host incremental games, but I think it might be a good place to check out for your project, and perhaps it is what you need.
If it's a static HTML website, I'd recommend Github Pages. Free (even with your own domain name) and best of all because each site is a Git repository, you have a full local copy of the site at all times and so don't need to worry about Github disappearing (not that it's likely to). I've used it for e.g. http://samwilson.github.io/cfb/ (although that's just a landing page for a PDF really).
https://medium.com/ seems like the new wordpress
just making a git repo with html in it is a good way https://pages.github.com/
personally, I put my posts on tumblr so people can interact with them if they want and then link to that from my website: see blog link on https://katagames.net/
No there's no problem with it at all as long as you keep them up to date.
Although for a personal website I'd suggest looking into static-site generators instead if you don't actually need any dynamic content. A static site generator will be able to generate HTML from a markdown document and because it's just plain HTML that's generated it'll load so much faster than anything built with Wordpress. If your strapped for cash you can also host it for nothing with your own domain name using Github Pages or Gitlab Pages.
Phaser is just JavaScript, so you can host a Phaser-game anywhere that can serve static sites (html css javascript). I just followed Github's own guide: https://pages.github.com/
If you made a client-server multiplayer game you'd need your own server.
Check out Github page. It turns your github repo into a public facing website. So in your case you can upload your mp3s, create your github page, then your mp3s are accessible from the internet. So in your RSS feed you can point it to your github url and it'll work.
For self hosting at home. Get a computer that's always going to be up and online. Maybe a raspberry pi. Then make it into a webserver with like Apache or something. Then configure your router to port forward incoming https and http traffic to your raspberry pi. So now anyone going to your public IP now can see your mp3s. Then you can use something like dyndns to link a url to your IP in case your IP changes.
I code it myself. If you're just starting to learn html/css, w3schools.com is your new best friend, probably the most helpful resource that I used when learning website development and still use to this day. I'd also recommend github pages for free website hosting and for practice. Happy coding!
Best way to showcase your code and website for this sort of thing is definitely Github. Github pages, specifically.
If this is the only thing you've made, though, I'd say it's too simple, and it's just... not well done. Looking at your code you don't even seem to understand how header and paragraph tags work, which I would categorize as "basic knowledge." All your paragraphs have the same size text, all your headers have the same size text. <p2>, <p3>, and <p4> tags don't exist. You should just repeat <p> each time, same with the headers. <h1>, <h2> etc are generally used for different size headers (<h1> for title and <h2> for subtitle, for example), not as counters for which header they are on the page. You can repeat them. And then in your css you can just style them once, rather than repeating the same information in 10 different places. And I'm just going to leave it there, for now..
But! That being said. Keep making stuff! If you're enjoying it, it's a great skill to have. You've taken one class, don't worry too much about not having these things down yet. Do you need to be able to say you know these things on your CV today, or do you have time to keep working on your skills for a while?
It's really hard to say what exactly is enough to claim knowledge. Why not say you've taken a class? Or show people what you've made so they can see your level first-hand?
Sia wouldn't really make a difference in these cases. When law enforcement takes down a site, they're taking down the front end web server. Sia is back end storage. The most Sia could do is store a resilient backup of the data, but a lot of services can do that.
There's maybe a future where Sia could host web sites if they're totally static (similar to hosting on S3 or Github pages, where the web site can be implemented entirely in HTML/CSS/JS), but we're probably at least a year away from something where that's even a possibility.
I also got my domain name from Namecheap. If you're just trying to create a personal website with static content, you can just use GitHub Pages to host your site, otherwise +1 to Digital Ocean.
No, you're doing it right - Wordpress & Squarespace just try to hold your hand a lot because most people don't want to get bogged down in design. If you just need a place to post your own html/css, GitHub pages is really the best bet: https://pages.github.com
Learn how to deploy any static website first. https://css-tricks.com/deployment/ is a good place to start. I always recommend people to start with the basics first rather than jumping on a framework and wondered where they are years after. I looked at your repo and to be honest, you don't need angular 2 for this. I might be wrong and you might be adding more features into it in the feature which justifies your choice of framework now.. but for a static website with 4 pages, come on.. even if you really want the website to be SPA, vanilla js is more than enough for this. Heck, you might be learning more stuff (AJAX, Dom) than you do with angular 2. Learn how to make html pages, webservers and where do you go to host them etc. if you're already using github, take a look at github pages https://pages.github.com . Angular 2 compiles to html, js and css so it's pretty much static website. Now when you're ready, start on more projects that angular 2 is more geared to, which is web apps.
> I thought hosting my own website was going to be an option but, domain name to my knowledge HAS to be "rented".
Look into free Dynamic DNS providers. Sure, you'll get a hokey domain-name, but not only is it free, it should work without getting a static IP address from your ISP.
Though, you're usually better off using a hosting service for online content. The internet can be a rough place—you'll end up with a HDD full of Viagra spam if you're not careful.
Oh, and one place to put up a web page for free is GitHub. You should be using Git for HTML/CSS development anyway, so using GitHub Pages should be fairly painless.
The above comment hits the nail on the head. However, there are free hosting options available like Heroku and GitHub Pages. I think you would do yourself no damage by learning Git while you're at it as its a core aspect of web development, so I'd go for GitHub Pages.
Plan things to go in small steps. Start with a hello world html page and try to get that live. No need to buy a domain just yet as GitHub will create a sub-domain from their site for you for the moment. Then add your CSS with any HTML amends before repeating the process with JavaScript.
Once you have your first website live, it's time to play with upgrading it, perhaps using SCSS or and JavaScript framework, but because everything is in Git, you can roll back to any state the site was in previously.
Good luck and feel free to PM with progress. Just remember, Google, StackOverflow and the plethora of blogs with tutorials are there to help and there to teach you nifty tricks and capabilities of the browser
I believe the best option would be to host it on the official datguylirik.tv website. For static content you could also try something like Github Pages. Using someone else's domain to host the past broadcasts might be a bit weird IMHO (you would get something like lirik.randomcompanyname.tld).
I'm surprised no one has mentioned github pages. I'm on mobile but I'll try to find a link. They are free, and learning the amount of git you need to upload files takes less than 10 minutes. :)
Here you go: https://pages.github.com
They even guide to thorough it! :)
Not related to your code, but if you copy everything to a branch called gh-pages then Github will host for you and you can demo it online.
Click "project site" here for instructions: https://pages.github.com/
GitHub.
Unless you need support for a server-side language that GitHub Pages doesn't support, there's no reason to use anything else. And trust me, it looks great to potential employers.
/u/martinoj2009 posted a quick video on how he manages his site using Jeckyll and Git yesterday. https://www.youtube.com/watch?v=ROISt8oAWoQ
There are free webhosts that also offer domain names such as 000webhost. A quick Google search will show you many however I do not have much experience with them so cannot give you any guidance or advice on which to choose.
However as long as your site does not use a back-end or database and you don't mind some extra research I would recommend using Github Pages, the source code for your website will be public and open source but you will get a quick and reliable website.
More info on Github Pages here: https://pages.github.com/
>Why can't I just upload files to a server and run my website like that?
You absolutely can and plenty of people still build websites like this. The very popular Github Pages is built entirely around uploading and hosting static sites. Django and other web frameworks are a different way of doing things.
>Can a website written in Rails be made using Django?
Yes, some things will be a little harder others will be a little easier depending on how comfortable you are with each language and dev environment.
>I've started the Django tutorial on the official site, but I'm starting from scratch with web dev and am not really understanding the material. What can I do to fill in the gaps?
Web dev is much more than just the Python side of things. It's probably easier to start building simple sites with HTML and CSS, and then incorporate a server-side language when you find a need for it.
>Anything else I should do before venturing in to web development?
Full stack web development requires a huge amount of divergent skills. HTML and CSS are mostly about design, layout, responsiveness, and wrangling with browser quirks. This is almost 100% removed from the skills required for building web APIs, or database design, or working with application server frameworks such as Django. Each requires its own skillset with not much overlap.
Find one thing and focus on it, when you need the skills for something else slowly incorporate those too. Baby steps and learning only what you need right now will help you not become overwhelmed.
So 3 ideas. None of them quite ideal, but maybe something works for you.
1) The simplest, but with smallest gains - Vimeo. Vimeo will deliver slightly less compressed result.
2) Might be worth researching what are the best encoding settings for yt. I know yt has their guidelines, but some clever folks have figured out tweaks for those as well that might work better for animation. But I can't recall them from the top of my head.
3) Another idea would be to get a free host (GH pages, for example) and drop an h264 encoded mp4 file there. All modern browsers will be capable of playing it back. And you control the output quality.
Github allows you to host simple static sites using their GitHub pages service. It's a great service, especially if you familiarize yourself with the likes of Jekyll.
If you don't already, get yourself a GitHub account and make a GitHub page. It's completely free. You'll get a url that looks like myGitHubAccountName.github.io, but if you decide buy a domain name, you can point it to the page pretty easily.
I use DigitalOcean these days, but it requires a bit of sys admin work to get going. If you're looking purely at a static HTML/CSS/JS site without any back-end required then I'd suggest you give Github Pages a shot - it's not only free hosting, but teaches you version control (Git) and Jekyll as part of the process. Enjoy! :)
You might want to look into GitHub Pages. It allows you to host a static website for free, and its ideal for small hobby projects. It's also a good opportunity to learn how Git works if you haven't done that yet.
Have you looked into Github Pages?
Regardless, if you want to be a developer, you really should start using git asap (whether that be with Github, GitLab, bitbucket, or something else).
Ich schreibe diesen Vorschlag im Wesentlichen, um eine Möglichkeit für technikaffine Leute aufzuzeigen. Trifft dies auf eure Gruppe nicht zu, ist die Verwendung einer CMS-basierenden Lösung sicher die bessere Wahl.
GitHub bietet mit GitHub Pages einen Hosting-Service für statische Webseiten an. Hat man ein HTML-Grundgerüst, können Artikel mit Markdown (was auch hier auf Reddit für Kommentare verwendet wird) geschrieben werden. Steckt man die in ein GitHub-Repository, erstellt GitHub daraus automatisch eine Webseite mit einer Unterseite pro Markdown-Datei. Das HTML-Gerüst drumrum (Navigation, Style usw) muss man allerdings selbst machen oder was vorgefertigtes nehmen.
Die einzelnen Artikel schreibt man also auf dem PC oder auf der GitHub Benutzeroberfläche als einzelne Markdown-Dateien und sobald man sie ins GitHub-Repository lädt, erscheinen sie auf der Webseite.
Vorteile (gegenüber einer klassischen CMS-Lösung):
- Datensicherung trivial (Klon des Repositories; kein SQL-Gefrickel)
- Kein eigenes Benutzermanagement (Schreibberechtigung läuft über GitHb-Nutzer)
- Keine Sicherheitsprobleme auf der Webseite, da alles statisch ist.
- Keine Abhängigkeit zu einem Anbieter (verwendete Software ist Open Source und das generierte HTML kann prinzipiell auch auf einen eigenen Webspace geladen werden).
Nachteile:
- Keine Benutzerrollen (jeder sieht alles)
- Wikiinhalt ist für alle sichtbar
- Keine dynamischen Features wie etwa Volltextsuche
- Jemand muss das HTML bauen
- Jemand muss sich mit Git auskennen
Thanks for the reply. If you would like to make this tool more transparent and auditable, you should start by hosting the expanded source code on GitHub and making changes there. Ideally cryptocurrencytools.org would also be hosted from there using Github Pages.
https://education.github.com/pack
Even if you're not a CS/IT/programming related major, you can get a free registration for a domain ending in .me for 1 year, and $50 credit through DigitalOcean.
If setting up DigitalOcean is too much for you, you can use Github Pages with a custom domain for a simple website. Nice place to put a resume.
I think that for simple website without backend Github Pages should be ok.
I did not use it though so i cannot say how to use it. You just have repository which can be displayed as HTML site.
Incredibly sorry for the huge delay!! Don't really watch this subreddit anymore (which is poor form...)
Was running through a checklist of things before going on holiday and spotted the 404. Have jumped on the server and corrected the issue - it should be back now.
More info, if you are interested.
Looks like there have been three unscheduled restarts of my server in the 2-3 weeks, and on the second the partition mounts changed location, which ruined the web server configuration - it couldn't find the files for rplaylister as a result.
I'm actually halfway through the process of migrating rplaylister to GitHub Pages, as this isn't the first instance of this sort of problem. That way I won't have to worry about hosting and hopefully problems like this, which I totally failed to notice, won't occur.
Yes, there are free hosting services for static web pages. GitHub is one of them! https://pages.github.com/
The url they make for your github account is already nice, and they support CNAMEs for using your own domain.
You already use Git to upload your files to Github, right? (Hint: if you know what 'git push' is, that's a yes)
If you can do that, you can deploy your site using GitHub, kind of in the way you describe. But instead of pushing to your main 'master' branch, you can push to a special branch that GitHub automatically sets aside for you: the 'gh-pages' branch.
GitHub pages allows you to store your static website a repository, like you're already doing. Here's the bonus: you can view your stored code as a website, too. It's super-fast and, with a few tries at updating stuff, really easy to understand.
Start here: https://pages.github.com . This should take maximum one hour to do. If it's taking longer, post here on in Stack Overflow for support. Good luck!