I pushed a new commit to my pages https://akshatgadodia.github.io/personalwebsite/, but the new updates or content isn't showing up there.
My repo is https://github.com/akshatgadodia/personalwebsite
Everything builds and runs locally. My Git repository is up to date, and there is nothing on the GitHub status page about problems with builds, so I'm at a little bit of a loss about where to go with this. How can I get my page to update with new content that I add?
Related
I'm using the code from a github repo for my project, and have been trying to understand some of the dev history about a problem I'm having. However, I'm unable to list the commits from one particular developer. Usually, you will see a link option to list all the commits, on the page of any one commit of any given author. But for this one dev only, that link isn't there. Github docs say this could be due to that author no longer having a github account, but that isn't the case here. Also, I can manually append a commits?author=username to the URL, but that doesn't work either. The only way I can see the commits is to load the network graph, scroll the timeline, and mouse-over each commit dot one at a time. It is a difficult way to scan through dozens of commits.
This is best done locally. Clone the repo and then use log or shortlog:
git log --author=author#email.com
or
git shortlog --author=author#email.com
gitk also supports the --author option to filter commits by author.
I have made some changes to a Django template, saved them, committed them to git, pushed to GitHub and then deployed this new version to Heroku.
The build succeeds and I can view the template but the change is not there.
I checked the GitHub repo, the change is there. When I check the activity feed on Heroku I can see the change when I click the Compare diff link.
When I make changes to other areas of the project, views etc there's no problem, I have updated other templates without issue but can not get the new CSS into the deployed version.
Inspecting the code of the deployed version shows the old CSS not the new so it isn't just an issue with my stylesheet, inheritance or so on.
I've run out of ideas, any suggestions of how I can resolve this?
I have found an answer, it seems a little like using a sledge hammer to crack a nut but ...
Anyway I deleted the templates directory, went through a cycle of commit, push deploy. Reinstated the templates directory redid the commit, push, deploy cycle and for whatever reason the CSS is now being picked up and displayed as expected.
I still have no idea what the original problem was, why it happened or how probable it is I will have the same sort of issues again so any suggestions, explanations and clarifications would still be much appreciated.
I have taken a project live with the help of Heroku. I set secret keys properly, using environment variables etc, not committing local settings containing any secret keys etc.
Then, reviewing which actual files had been pushed to the git repo within Heroku, I found an 'old_settings'-file which in a pure oversight had been missed. That file contained the secret-key.
I cleaned out the file and pushed the changes to the repo (git push heroku master). Then I deleted all past commits following the last answer:
removing commit history in git
Should this be fine? Reading Mipadis answer so it seems:
Pushing secret keys to heroku, safe?
Should this be a problem, or would this be considered problem solved?
Appreciate any feedback, and should my English be confusing at all I'd be happy to clarify.
Edit
Generated a new secret-key the same way Django does it, and updated the Heroku environment-variable
heroku config:set secret_key=NEWKEY.
Question remains: would this be sufficient?
GitHub states:
Warning: Once you have pushed a commit to GitHub, you should consider any data it contains to be compromised. If you committed a password, change it! If you committed a key, generate a new one.
This article tells you how to make commits with sensitive data unreachable from any branches or tags in your GitHub repository. However, it's important to note that those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on GitHub, and through any pull requests that reference them. You can't do anything about existing clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on GitHub by contacting GitHub Support or GitHub Premium Support.
It would be best to generate a new secret-key just to be sure.
I went here and started on the first task which is to create a registry. I later closed my browser and when I go back to that page, I just get the homepage again and if I start that wizard, it acts as if I've never done it before and forces me to create a new repository.
How the heck do I get back to the repository I created initially and then how can I continue on with this wizard to the next steps with that repo? Or do I lose the repo entirely until I get through all steps in this wizard? Where the heck did my repo go? It says it exists but where? How do I get to back to that repo on the AWS control panel?
https://console.aws.amazon.com/ecs/home?region=us-east-1#/repositories
no? I couldn't comment instead of posting as answer due to insufficient reputation, sorry for that.
Alright, so I have started using Github to easily share my code, and to keep track of updates. My main problem is that I have put my code in my repo, but I am not sure how to update it without saving the updates as a different file, and then pushing that to my repo.
Short version: Is there a way to update my code without pushing a whole new file.
Your question isn't very clear but if I'm understanding you correctly, you can do the following:
Edit the files you need to change
Do git add for each file to make git track the changes i.e. add the files to the staging area.
When you're ready to commit, do git commit to commit the changes. This will commit locally.
When you are ready to push up to github, do a git push. Git is smart about sending up the changes, not whole files.
Git takes a while to understand and it sounds like you're not there yet. I would spend some time going through at least the first few chapters of the Pro Git book, which is available free online at http://progit.org/book/.
Hope this helps.