I have a small portfolio site that I work on in my spare time as a way of demonstrating and applying what I have learned from school/work. Part of this demonstration involves me currently listing the repository as "public" on GitHub for anyone to see and browse. The reasoning behind this is that this means people can see how I approach project management and how I structure my code.
However, this introduces some security risks and other problems. Obviously, I now cannot include any private information, such as passwords of any kind (or private ports, mail variables, etc); rather, this needs to be moved elsewhere. For a while this was fine, until I decided that I wanted to include a blog, which necessitated users, which necessitates login functionality (whole new can of worms).
Because of this, I am now wondering where I can store all of the additional confidential information that I have created. Would I be better off to mark the repository as "private" and simply host some examples on my website? To me this is slightly less ideal, as it appears less authentic (ie. I might have spent additional time refactoring those files, above and beyond what I would typically do in my work).
However, is this something that would be a better idea in the long run, as well as simplifying development by consolidating my files?
UPDATE: The site uses almost no frameworks (other than Foundation 6 for front end markup) as this is the primary purpose of the site (to teach myself the concepts from the ground up).
Primary Question: Is there any benefit to hosting the site on a public repository that can't be gained by only exposing specific files elsewhere? i.e. in a Projects section of the site?