I can't seem to find a definitive answer to this.
I would like to purchase the Developer package on Github and set up multiple static sites on completely different custom domains (not subdomains). For example, with one Github Developer account (username: SampleUsername), create a blog about horses (horsesblog.com), a blog about cats (catsblog.com) and a blog about dogs (dogsblog.com).
The key here is that they are all on separate private project repositories within the SampleUsername account and are completely independent of each other.
Is this possible?
Running multiple sites on different apex domains in GitHub Pages is entirely possible!
You just need to add the relevant A records (or ALIAS/ANAME is supported) for the domain.
Related
I have two websites: www.mycompany.com and shopmycompany.com (not a subdomain) and would like to publish the relationship between them using schema.org. At present the www.mycompany.com identifies itself as an Organization and shopmycompany.com as a WebSite but there is no linkage between them. What would be best practices to present that connection?
Just from a quick skimming of https://schema.org/WebSite, there are multiple properties that would be fine as linking the website with the company:
author/creator
maintainer
provider
publisher
However, I wonder whether the Shop really should classified as a WebSite (which is a CreativeWork) and not rather as a Store which may simply have a parentOrganisation.
Yet another alternative would be to classify it as a Service, which is provided by the Organisation and can offer things.
And yet another alternative could be to classify the shop website as the OfferCatalog of offers made by the company.
I have built a Tableau extension, and now need to publish the extension in a manner that (a) allows others in my organization to view dashboards using the extension + utilize the extension in their own dashboards, and (b) does (a) in a secure manner.
This page of the Tableau Extensions API docs (https://tableau.github.io/extensions-api/docs/trex_contributing.html#hosting) suggests two approaches for hosting extensions:
Host your static content on GitHub pages
Host your node app on Heroku
Regarding these approaches, I don't believe (1) is sufficiently secure, as (my understanding is that) GitHub Pages are publicly accessible by all, whereas (2) seems a bit excessive.
I am wondering if there is a way to host on GitHub pages, but also make the extension / web app accessible only to users with access to the private repository. Otherwise, I am seeking other possible solutions to this problem.
Depending on how dynamic your extensions are, you can simplify deployment with AWS S3 or similar. I've used S3 bucket hosting for all of my extensions to this point with no problems. That should meet both your privacy and availability requirements.
Is it possible to give read-only access to private Github project boards? Not to the code projects, just to the boards? The code is for developers but other people in the company should be able to see the status of various projects.
Also, is such access free? I'm setting this up for a small startup and funds are still tight. I don't want to make it expensive for them to get help from friends and family.
You can give access to read or write access to repositories, but it does not provide access like this, but you can look for permission information on this link.
https://help.github.com/articles/permission-levels-for-an-organization/
You can review the article at https://code.tutsplus.com/articles/team-collaboration-with-github--net-29876
We have used waffle in past and it works for providing status only. You can use Waffle for providing the status on different issues https://waffle.io without giving access.
I am using github to share a set of SPARQL queries:
http://www.boisvert.me.uk/opendata/sparql_aq+.html?file=specific%20sensor.txt
Currently the simple work allows end-users to access queries stored on the github repository, but ultimately I want to allow them to also modify the queries, as with a pastebin, and make use of the repository to better manage the shared system. Ideally I would want end-users who may not be very tech-savvy, to be able to make minor changes to queries to an open, linked data endpoint: so to keep the technology barrier low.
My problem is this: how best to structure the github project and exploit the API to make the most of the available information? I can think of different points:
Currently the project (https://github.com/boisvert/unshaql) holds client code and example queries. Does it make a difference to create an independent project (separate from the web client code) for SPARQL queries?
I would use directories within the project to classify/tag queries, and file names to title them. Are there better alternatives? It strikes me that a hierarchical structure is not a good fit to tags.
When end-users save, a simpler (and cruder) option is to allow them to push their file into just one branch, which holds the examples. A better engineered one would be to allow them to use their github credentials to fork the set of SPARQL queries and edit theirs, but with unaware users, how do I avoid creating a mess?
I think that a rigular Github repository is a rather bad fit for this kind of content. If your users have a GitHub account, you should probably use Gists instead: https://help.github.com/articles/about-gists/ I never used this myself, but it seems perfectly adapted to what you are planning. Your site could become a DB of tags over user-provided gists. That would however lock you into GitHub-specific solutions.
Even if you go for a regular repository, you should not allow the users to commit into the repository hosting your code: that would be a serious security hazard as you won't be able to control the parts of the repository to which they are allowed to commit.
If you setup two repositories, it's rather easy to have the code of a webpage in a repository, and the code automatically commited in another repository (under an anonymous identity so that your users don't have to create a github account).
Also, note that the oauth token should never be stored in a public repository (or the GitHub robots will invalidate it in a matter of hours).
See Hiding GitHub token in .gitconfig for a solution to this sub-problem.
I'm using the Github applications for Windows for 2 accounts.
One is my personal and the other one is a professional account.
The problem is that everytime I logout and login (depending on which project I'm working on) Github sends me an email that a new ssh key pair has been generated for this computer.
I tried to unsubscribe from these mails or even setup a fixed multiple key pair but to no avail.
Any tips?
It is not intended by GitHub to have several User-Accounts for different needs. Ususally you have only one User-Account and use the collaborative-features on repositories to work together.
In a professional context you'd use GitHub's organizations to create teams for the specific repositories - where every team-member uses its one and only GH-account.
However, to use different GitHub-accounts you may try to use the Git CLI as described here or a different Git GUI (Sourcetree seems to provide a kind of multiple account-management).