Trouble uploading project to GitHub pages? - github-pages

I have my project working on localhost perfectly, but when I deploy my app and I go to the GitHub Pages, it is just blank with an error:
Failed to load resource: the server responded with a status of 404 ()
How to avoid that error message?

Check the type of GitHub pages, and verify your GitHub repository is one of them:
To publish a user site, you must create a repository owned by your user account that's named <user>.github.io.
To publish an organization site, you must create a repository owned by an organization that's named <organization>.github.io.
Unless you're using a custom domain, user and organization sites are available at http(s)://<username>.github.io or http(s)://<organization>.github.io.
The source files for a project site are stored in the same repository as their project.
Unless you're using a custom domain, project sites are available at http(s)://<user>.github.io/<repository> or http(s)://<organization>.github.io/<repository>.
Then check the source of publication:
The default publishing source for user and organization sites is the master branch.
If the repository for your user or organization site has a master branch, your site will publish automatically from that branch.
You cannot choose a different publishing source for user or organization sites.
The default publishing source for a project site is the gh-pages branch.
If the repository for your project site has a gh-pages branch, your site will publish automatically from that branch.
Project sites can also be published from the master branch or a /docs folder on the master branch

Related

local gitlab Auth 2.0 and django

Hello We made our own Gitlab installation on our server. I installed Readthedocs Local in the link below. In order to connect our accounts on gitlab with readthedocs, I was asked to make the following settings from the gitlab section in the readthedocs document.
https://readthedocs.org/
https://dev.readthedocs.io/en/latest/install.html
But interestingly, even though I set the settings on our own server gitlab.local, by default django goes to gitlab.com when I connect to gitlab via devthedocs.org. However, it should connect to gitlab.local on my server, how can I fix this problem?
On page 34 of this document here
https://readthedocs.org/projects/django-allauth/downloads/pdf/latest/
"The GitLab provider works by default with https://gitlab.com. It allows you to connect to your private GitLab
server and use GitLab as an OAuth2 authentication provider as described in GitLab docs at http://doc.gitlab.com/
ce/integration/oauth_provider.html"
I need your support in this matter.
Thank you very much.
Configure the applications on GitHub, Bitbucket, and GitLab. For each of these, the callback URI is http://devthedocs.org/accounts//login/callback/ where is one of github, gitlab, or bitbucket_oauth2. When setup, you will be given a “Client ID” (also called an “Application ID” or just “Key”) and a “Secret”.
Take the “Client ID” and “Secret” for each service and enter it in your local Django admin at: http://devthedocs.org/admin/socialaccount/socialapp/. Make sure to apply it to the “Site”.

Can you Hide your API Key on GH-Pages?

GitHub Pages requires your repository to be public. However, I have an .env variable that is using an API key to call my CMS, and I would not like that API key to be shown.
Does GitHub or GitHub Pages have a way to do that?
I have used a .gitignore, but it does not solve my problem.
GitHub Pages requires your repository to be public.
Your repository can be private, but the website will be published only in priced Github plans.
EDIT: Github has a functionality for secret values like those required in a continuous integration or Github workflow. This is explained in detail here: https://docs.github.com/en/actions/security-guides/encrypted-secrets
You can store up to 100 repository secrets, each one up to 64KB. On your repository main page, you will find the option under:
Settings > Secrets > Actions > New repository secret
Once added, you can use it in your website publishing workflow using proper shell quotations: https://docs.github.com/en/actions/security-guides/encrypted-secrets

In AWS Amplify, is it possible to have two separate teams (repos) working on the frontend and backend exclusively?

I would like to develop a React app using Amplify and two dev teams. Can one team work on the frontend exclusively, without giving them access to the backend code (the amplify folder)? The backend team can have access to both the backend and frontend code. If possible, how would I set it up?
By following the instructions on AWS Amplify's multiple frontends workflow page, you could get this to work.
According to the docs,
If you’re building a mobile and web app in separate repositories, the recommended workflow is to keep the backend definition (the amplify folder) in only one of the repositories and pull the metadata (the aws-exports.js or amplifyconfiguration.json file) in the second repository to connect to the same backend.
Therefore, you can keep the backend code in one of the reposities with a fake/demo frontend and then have the real/current frontend in a different folder with only aws-exports.js or amplifyconfiguration.json.

Sitecore 9.0 - Looking to implement Azure AD B2C

Thank you for reading my question.
I'am trying to implement Azure AD B2C in Sitecore 9.0.2 version that being said i have used a sample code from Git Hub which implemented ADB2C using ASP.NET MVC. I created a feature project in Sitecore added all the files needed,built the solution and deployed it to Sitecore web root, resolved dll conflicts but still seeing one issue:
Sitecore have an older version of "System.IdentityModel.Tokens.Jwt" dll with class "System.IdentityModel.Tokens.JwtSecurityTokenHandler" which is no longer available in Version=5.2.1.0
Any help/guidance here to resolve this issue or is there any sample implementation available in Sitecore with Azure AD B2C.
Note: i'am not looking for Federated Authentication (Azure Active Directory) Azure AD
enter image description here
Steps to create Azure AD B2C :
Login to Portal.azure.com and create a New Tenant (working directory
with subscription)
Link your Subscription
Create/Register an Application (Client)
Create Client Secret, User Flows, Custom policies reference
Create an MVC application which can generate Azure Login Url reference
Deploy your code to sitecore root & browse the site.
Open Issues : Users need to be created in Sitecore manually even after having Virtual User creation in place.

WSO2 P.PaaS : Accessing the AS and other WSO2 products

So I have got WSO2 P.PaaS installed and running. I want to deploy .war file to the Application Server. It seems the AS on P.PaaS does not accept .war file; but the stand-alone one does. See here. Also, I want to use the WSO2 products deployed into the PaaS. I am not sure what URL or port I should use. Is there a tutorial that I can use to experiment?
Sorry for the brevity, but, I am new to WSO2.
What PPaaS version you have installed, 4.0.0 or from current master branch which is 4.1.0 milestone 1 version?
Here is the quick start guide Quick start guide .
You can access the management console as https://STRATOS_DOMAIN:9443/console.
Assuming you are using PP 4.0.0 version,
Log into management console
Go to cartridges page. There you can find the available cartridges, you should find Application Server as a cartridge.
Click on AS cartridge in order to subscribe for it. At subscribing process you would be asked a GIT repository URL.
After you subscribe, PP will clone what is in your GIT repository url in to Application server. So if you provide a url which has your web application, those application would be automatically deployed into the Application server. Here is a sample GIT repository , you can include your web apps under "webapps" folder.
There after if you modify your web apps (say web app version 2) and commit the changes to your repository, Stratos/PP automatically update Application server with the new web apps.
Since you have already deployed PP, you can have a loot at this screencast to see how you can deploy a web app