I created a website with Jekyll and uploaded it to github. This allowed me to host my site for free (It's mostly just a template at the moment) repo here:
https://github.com/themallardcomplexion/themallardcomplexion.github.io
It serves fine online with the domain name but I tried to download it and serve it locally but get the following errors:
Configuration file: none
Source: C:/Users/isw/Desktop/Taijisoce/themallardcomplexion.github.io-master
Destination: C:/Users/isw/Desktop/Taijisoce/themallardcomplexion.github.io-master/_site
Incremental build: disabled. Enable with --incremental
Generating...
Build Warning: Layout 'post' requested in themallardcomplexion.github.io-master/_posts/2019-01-19-welcome-to-jekyll.markdown does not exist.
Build Warning: Layout 'default' requested in themallardcomplexion.github.io-master/404.html does not exist.
Build Warning: Layout 'page' requested in themallardcomplexion.github.io-master/about.md does not exist.
Build Warning: Layout 'home' requested in themallardcomplexion.github.io-master/index.md does not exist.
done in 0.587 seconds.
Auto-regeneration: enabled for 'C:/Users/isw/Desktop/Taijisoce/themallardcomplexion.github.io-master'
Server address: http://127.0.0.1:4000
Server running... press ctrl-c to stop.
It serves with no formatting and just shows a plain text site.... any ideas?
I have tried downloading the code via the Github app and downloading it as zip
The errors are coming from Jekyll looking for layouts for the pages you built. You need to make a /_layouts/ folder with all the layouts your site needs:
/_layouts/
|
|--default.html
|
|--post.html
|
|--page.html
|
These all correspond to the build warnings that are coming up. See the Jekyll tutorials and docs for more details.
Also, instead of downloading the repo, it's better to clone it. That way you can work on changes locally then push changes to GitHub. Here's the link to docs for cloning a repo
Related
I am managing a mostly static site through GoDaddy.
The site is a React single page application, that is still currently under development, and that occasionally needs content updating. The project folder is hosted as a public git repository.
My goal is to be able to automate the process of updating the site. Currently I need to:
npm run build
navigate to the build folder in windows file explorer
navigate to the public html folder in cpanel, in my web browser
delete the current build files
upload the contents of the build files into cpanel, folder by folder (cpanel will not allow me to upload subfolders)
I have looked through countless forum posts, and blogs, etc to find a way to automate this, but I always end up doing it manually.
You need to investigate using continuous deployment (CD/CI) and using a different hosting setup. Unfortunately, the type of platform that you use (with CPanel) is limiting and is not really oriented at your use case.
However, CPanel does have an option to use Git version control to manage the files and folders in your account. Go into this option and say "Clone repository", where you'll have to link a repo and say where it should install. Note: It is possible that your hosting provider has disabled this feature.
I suspect that this CPanel feature does not automatically pull in changes when you update the repo, so you would probably still need to manually clone the repo again when you make changes (which is still easier than copying files over). Also note that any data you store may be removed when cloning again.
I'm struggling to get a Google sample working.
I think I'm following the instructions correctly but now, when testing (in project-y), I receive a warning:
You are testing the Actions that you have created in project: project-x
I had previously used project-x but it has since been deleted. I've tried deleting the project and recreating, redeploy etc. but I'm entirely unable to avoid the error.
I'm unable to determine where project-y references project-x and how to correct this.
The only location where project-[x|y] are referenced is in ./sdk/setting/setting.yaml:
defaultLocale: en
localizedSettings:
developerEmail:
developerName:
displayName: Updates sample
fullDescription:
privacyPolicyUrl:
pronunciation: Updates sample
shortDescription:
smallLogoImage:
termsOfServiceUrl:
projectId: project-y
When I gactions push and gactions preview deploy, both commands correctly reference project-y and the generated URLs correctly point to project-y:
gactions push
Pushing files in the project "project-y" to Actions Console. This may take a few minutes.
Sending configuration files...
gactions deploy preview
Deploying files in the project "project-y" to Actions Console for preview. This may take a few minutes.
Sending configuration files...
I've scoured the gactions config and the cloned directory for hidden configuration files but am unable to find any references to project-x.
If I search, the only reference I find is the single reference to project-y in the above YAML.
I have seen the same issue.
In my case, it is because I used the same Display name for project-x and project-y.
I hope you check your project's Display name on Develop tab in Actions Console and solve your issue.
I have been creating this website for a few weeks now (I am fairly new to web-dev) and have just recently made a repo (on Github) for it.
Link:
https://github.com/Lathryx/TopShelf-Recipes
I want to deploy with Netlify however I am unable to. Netlify continuously gives a 404 error on the site(s) that I create. I think it has something to do with the publish directory but I'm not sure. I want it to open to landing.html.
The few times I have tried to deploy now I have tried:
No build command/publish directory.
No build command and the publish directory set to TopShelf Recipes
(have also tried /TopShelf Recipes).
No build command and the publish directory set to TopShelf Recipes/landing.html.
No build command and the publish directory set to /TopShelf Recipes/landing.
Image of Error:
I really don't know what to do. Does anybody know why this is happening?
The netlify/my-first-netlify-deploys demo project shows files with a netlify.toml to adtually generates the files.
Result: https://playwith.netlify.app/
But if there are no generation involved, then said files should be directly at the root folder of the repository, not in a subfolder.
The landing page of your site must be titled index.html (as I’ve found), this fixed it for me. Mine (originally) was titled landing.html.
I will keep this in mind in the future.
I want to host a simple blog on Github pages. Therefore I set up a repository and used Hexo as a compile and deployment tool.
After testing my site locally I run the following command:
hexo deploy --generate
Sadly I, just a few seconds later, get the following message from Github:
The page build failed with the following error:
The hacker theme is not currently supported on GitHub Pages. For more
information, see
https://help.github.com/articles/adding-a-jekyll-theme-to-your-github-pages-site.
For information on troubleshooting Jekyll see:
https://help.github.com/articles/troubleshooting-jekyll-builds
If you have any questions you can contact us by replying to this
email.
How can I publish my site using the hacker theme? If this is not possible which themes are supported by Github? How do I use them with Hexo?
Bypassing Jekyll on GitHub Pages
It is now possible to completely bypass Jekyll processing on GitHub
Pages by creating a file named .nojekyll in the root of your pages
repo and pushing it to GitHub. This should only be necessary if your
site uses files or directories that start with underscores since
Jekyll considers these to be special resources and does not copy them
to the final site.
Source: https://github.com/blog/572-bypassing-jekyll-on-github-pages
[..] I used the username.github.io repo and deployed directly to master
and it works!
https://github.com/CodeDaraW/Hacker/issues/9
Here's an example of a project:
https://github.com/storm-enroute/macrogl
The README.md of this project contains a build status image from a Jenkins running on a server somewhere else:
[](https://ci.storm-enroute.com:8080/job/public-macrogl/)
This image is rendered perfectly in Stackoverflow and Github static pages, but on the Github website it is cached to the content delivery network called Fastly. Opening the image URL shows "Not found".
Why is this happening?
How do I have the Github web interface render a markdown with such an image correctly?
How do I have the Github web interface render a markdown with such an image correctly?
The syntax is correct.
Some other project leverage such feature (see LibGit2Sharp Readme or libgit2 Readme for instance).
Why is this happening?
Few seconds ago, https://ci.storm-enroute.com:8080/job/public-macrogl/badge/icon was returning a 404 for me. It looks now fixed.
However, there's a possibility that when the CI server is offline/can't be reached, the 404 is temporarily cached by Camo and served until the cache expires.
install jenkins plugin for embeddable-build-status from: https://plugins.jenkins.io/embeddable-build-status
add to your README.md the tags you want:
Plain Link (with view)
http://URL:8080/buildStatus/icon?job=JOB_NAME
Plain Link (without view)
http://URL:8080/buildStatus/icon?job=JOB_NAME
Markdown (with view)
Build Status http://URL:8080/buildStatus/icon?job=JOB_NAME
Markdown (without view)
Build Status http://URL:8080/buildStatus/icon?job=JOB_NAME
3.Configure jenkins security to allow the status view:
Manage Jenkins -> Configure Security -> Authorization -> choose matrix-based security and check the "ViewStatus" box for the Anonymous user.
if admin user is not there, add it and give it permission to all the boxes.
For anyone else spending way more time than intended on this and wanting a little clarity on what link(s) to use after installing the Emeddable Build Status plugin:
If you navigate to the job in the Jenkins (jenkins_home >> repo >> project >> branch), there's a "Emeddable Build Status" widget you can click on the left pane, and it'll show list exactly what links you can use for your specific jobs.
The following URL structure might also get you to the embeddable build status page:
https://<jenkins_host>/job/<github_owner_or_org>/job/<github_repo_name>/job/master/badge/
Update: I had a similar issue. It turned that the cache server requires the image to be hosted behind a HTTPS, with a fully valid SSL certificate chain (CA(s) + cert). Once your server provides the full cert chain, github will display your badge.