I deploy an angular project on GitHub successfully but when I click on the link of the project documentation appear instead of project How can I open the project on browser. the link of the project is https://khaledelmasry247.github.io/myNote/
This is Jekyll that runs by default on GitHub Pages.
You can disable it by adding the file .nojekyll in the root of your project.
More here:
https://github.blog/2009-12-29-bypassing-jekyll-on-github-pages/
I have faced the similar issue long back with my repository. You can check these steps:
navigate to repository
Go to settings of your repository
In the options section, navgate to github pages.
In the source select "root" as shown below.
Then check it once.
In order for GitHub pages to work with your project, you will need to build the angular project and push the built artifacts to your repository. You will also need to tell GitHub which directory to look at for your built files. It will look for index.html by default. Looking at your repo, it looks like you have already built your project and the files are in your gh-pages branch. You will need to do something like #KushalSeth suggests, except in your instance, you will have to change it to look at the gh-pages branch.
Click on the Settings for your project.
Scroll down to the GitHub Pages section.
Change the branch to your gh-pages branch.
Save.
Related
I created a github page with jeyll as per https://docs.github.com/en/free-pro-team#latest/github/working-with-github-pages/getting-started-with-github-pages
This is my public repo https://github.com/MrBuggySan/mrbuggysan.github.io & this is the github page link https://mrbuggysan.github.io/
I've setup the github-pages dependency on the gemfile and this same repo works for me locally. Is there something I missed here?
First, make sure you have configured the main branch, folder docs, as publishing shource
Second, in that docs folder, you should see what Jekyll has generated: docs the "destination" folder in Jekyll configuration.
(like Jekyll itself does when it builds its documentation)
I created a todo app and had it using GitHub Pages. It does not pull anything other than the readme.md when clicking the live link. I do not understand what I messed up here. I have a different repo using same style of programming that is working fine.
Issue repo: https://github.com/jsfilas/todo-app
Similar working repo: https://github.com/jsfilas/Restaurant-Page
Restaurant-Page is deployed to a gh-pages branch. There does not appear to be a gh-pages branch for todo-app. You have to put your dist folder on an orphan branch called gh-pages to deploy a static site.
https://github.com/jsfilas/Restaurant-Page/tree/gh-pages This is what GitHub is looking at for your Restaurant-Page.
Another way to deploy GitHub pages is to name your /dist folder /docs and update your GitHub pages settings to look at the /docs folder.
My Hugo site starts locally, but only returns a 404.html page when hit on GitHub Pages.
I've tried re-instantiating the repo, rebuilding the site with different commands, pushing and deploying with the Hugo deploy script, and rm -rf the public folder and re-adding it.
Repository: https://github.com/jschalz/jschalz.github.io
When following the tutorial, running git submodule add -b master git#github.com:jschalz/jschalz.github.io.git public:
'public' already exists in the index
Currently hosted at https://jschalz.github.io.
I'd expect the site to come up with my pages (and I definitely have non-draft pages on there), but it's only returning 404.html. It's possible it's because I renamed the repo at one point, but I'm not sure. Troubleshooting ideas are very appreciated.
UPDATE: The issue was that I didn't have an index.html, index.xml, or README.md in my repo. Fixed.
2022: A different approach uses now GitHub Actions, since those are the default to build GitHub pages, since Aug. 2022.
Hence the new section "Build Hugo With GitHub Action" and the GitHub actions/hugo-setup.
Original answer 2019:
The issue was that I didn't have an index.html, index.xml, or README.md in my repo. Fixed.
Not exactly fixed.
The point of the tutorial was:
git submodule add -b master git#github.com:<USERNAME>/<USERNAME>.github.io.git public
This creates a git submodule.
Now when you run the hugo command to build your site to public, the created public directory will have a different remote origin (i.e. hosted GitHub repository).
Meaning what you should be pushing if, from your public subfolder, only what Hugo has generated.
You should not push your Hugo project (config.toml, themes, and so on): those should be pushed in a separate GitHub repository for safekeeping and versionning.
I'm starting a new Sitecore 9 project using Helix and TDS. I've got my basic structure setup, using Hedgehog's fork of the Habitat site as a guide. I'm also referencing Hedgehog's docs.
My solution is just a start, so it's very simple right now, only a Foundation.Serialization module that contains the TDS projects for the basic layer folders and a Project.Website module that contains a TDS project and an MVC Website project (MVC)....it's got a basic Razor view and some random CSS/JS files.
The TDS Habitat readme, says to use Solution > Deploy Solution to deploy the projects. When I do this on my project it builds and the Sitecore items are deployed to Sitecore, but my Views and CSS/JS are not....presumably because I haven't configured anything to facilitate this.
Looking at the docs and the TDS Habitat solution, it's not clear to me how to configure TDS to know anything about how to deploy files. I'm finding info on the web that says that TDS will deploy files, transform configs, etc but with no examples of how to actually make that happen.
How do I set things up so Deploy Solution will also deploy files from all of the web projects in a solution to my local web root?
First, you will need to make sure the Sitecore Deploy Folder is set. From the documentation:
Sitecore Deploy Folder – Contains the path to the ROOT of the Sitecore
instance on the file system. This setting is used to install the TDS
Classic service when needed and to deploy the compiled code when the
TDS Classic project is built.
You also need to make sure that file deployment has not been disabled:
Disable File Deployment – Stops TDS Classic deploying files to the
directory specified in the Sitecore Deploy Folder.
If you are still not seeing the files being deployed, you will need to check if the process has access to the deploy folder.
You can also deploy files as a .update package and then use another automated tool to deploy the .update package to the target environment.
I figured out the issue. On the properties page for a TDS project there is a field where you indicate which projects should be built and deployed along with the sitecore items:
https://www.hhogdev.com/help/tds/propgeneral
When I create a project in JetBrains WebStorm, a folder called .idea gets created. Is it okay if I delete it? Will it affect my project?
When you use the IntelliJ IDE, all the project-specific settings for the project are stored under the .idea folder.
Project settings are stored with each specific project as a set of xml
files under the .idea folder. If you specify the default project
settings, these settings will be automatically used for each newly
created project.
Check this documentation for the IDE settings and here is their recommendation on Source Control and an example .gitignore file.
Note: If you are using git or some version control system, you might want to set this folder "ignore".
Example - for git, add this directory to .gitignore. This way, the application is not IDE-specific.
There is no problem in deleting this. It's not only the WebStorm IDE creating this file, but also PhpStorm and all other of JetBrains' IDEs.
It is safe to delete it but if your project is from GitLab or GitHub then you will see a warning.
As of year 2020, JetBrains suggests to commit the .idea folder.
The JetBrains IDEs (webstorm, intellij, android studio, pycharm, clion, etc.) automatically add that folder to your git repository (if there's one).
Inside the folder .idea, has been already created a .gitignore, updated by the IDE itself to avoid to commit user related settings that may contains privacy/password data.
It is safe (and usually useful) to commit the .idea folder.
It contains your local IntelliJ IDE configs. I recommend adding this folder to your .gitignore file:
# intellij configs
.idea/
The reason my device was not being recognized was because my emulator was frozen.
What helped me was to wipe my emulator's data.
Android Emulator freezes
Checkout #gimme-the-411 's comment on this thread.