Project name should be pygrunn.org #1

Closed
cyberco opened this Issue Feb 11, 2014 · 9 comments

Comments

Projects
None yet
5 participants
Contributor

cyberco commented Feb 11, 2014

The current projectname is very confusing.

Contributor

bubenkoff commented Feb 11, 2014

not possible, github only allows names in format .github.com for
publishing static

On 11 February 2014 09:17, cyberco notifications@github.com wrote:

The current projectname is very confusing.

Reply to this email directly or view it on GitHubhttps://github.com/paylogic/paylogic.github.com/issues/1
.

Anatoly Bubenkov

Contributor

cyberco commented Feb 11, 2014

This means that for the Paylogic repos there can only be one static site and that is now used for PyGrunn.org?

Contributor

bubenkoff commented Feb 11, 2014

yes, that is correct

On 11 February 2014 09:20, cyberco notifications@github.com wrote:

This means that for the Paylogic repos there can only be one static site
and that is now used for PyGrunn.org?

Reply to this email directly or view it on GitHubhttps://github.com/paylogic/paylogic.github.com/issues/1#issuecomment-34734038
.

Anatoly Bubenkov

Contributor

cyberco commented Feb 11, 2014

Hmm...not too big on that. We'll leave it for now, but I'd prefer to, e.g., manually push approved new versions of the site to S3. We should create a 'release' branch that is always deployable and only merge approved pull requests into 'release'.

Contributor

maikelwever commented Feb 11, 2014

Pushing to Gh-pages branch is still supported and should allow you to name
the repo whatever you like, as with the dev-portal.
https://help.github.com/articles/user-organization-and-project-pages.
Op 11 feb. 2014 09:30 schreef "cyberco" notifications@github.com:

Hmm...not too big on that. We'll leave it for now, but I'd prefer to,
e.g., manually push approved new versions of the site to S3. We should
create a 'release' branch that is always deployable and only merge approved
pull requests into 'release'.


Reply to this email directly or view it on GitHubhttps://github.com/paylogic/paylogic.github.com/issues/1#issuecomment-34734585
.

Contributor

bubenkoff commented Feb 11, 2014

you gave a proof of my statement
only one repo is allowed to be a 'root'
you can use others to be 'subfolders' but that will mean we need a redirect
from root, which we don't want
we want only CNAME record

On 11 February 2014 09:35, Maikel Wever notifications@github.com wrote:

Pushing to Gh-pages branch is still supported and should allow you to name
the repo whatever you like, as with the dev-portal.
https://help.github.com/articles/user-organization-and-project-pages.
Op 11 feb. 2014 09:30 schreef "cyberco" notifications@github.com:

Hmm...not too big on that. We'll leave it for now, but I'd prefer to,
e.g., manually push approved new versions of the site to S3. We should
create a 'release' branch that is always deployable and only merge
approved
pull requests into 'release'.

Reply to this email directly or view it on GitHub<
https://github.com/paylogic/paylogic.github.com/issues/1#issuecomment-34734585>

.

Reply to this email directly or view it on GitHubhttps://github.com/paylogic/paylogic.github.com/issues/1#issuecomment-34734863
.

Anatoly Bubenkov

Contributor

maikelwever commented Feb 11, 2014

For the Github url yes, that'll be ugly, but CNAME is also supported for gh-pages branch, and the domain in the CNAME won't need a redirect, only DNS A record has to be set, as with the dev-portal.

Contributor

bubenkoff commented Feb 11, 2014

then my bad, i didn't know dev-portal is set only using A record!
we can rename then with np

On 11 February 2014 09:51, Maikel Wever notifications@github.com wrote:

For the Github url yes, that'll be ugly, but CNAME is also supported for
gh-pages branch, and the domain in the CNAME won't need a redirect, only
DNS A record has to be set, as with the dev-portal.

Reply to this email directly or view it on GitHubhttps://github.com/paylogic/paylogic.github.com/issues/1#issuecomment-34735841
.

Anatoly Bubenkov

@spirosikmd spirosikmd closed this Feb 19, 2014

Owner

xolox commented Feb 19, 2014

As it turns out we couldn't rename with no problem because after the rename of the repository from paylogic.github.com to pygrunn.org the dev-portal (which is also hosted on GitHub Pages) went offline :-). After some debugging I suspect that this is a bug / misfeature of GitHub:

  • Previously there was one project specific GitHub Pages site under the @paylogic account (dev-portal) but no account specific GitHub Pages site
  • As per this issue an account specific GitHub Pages site was accidentally created and then removed again by renaming the paylogic.github.com repository to pygrunn.org
  • I suspect that creating and/or removing the account specific GitHub Pages site is what broke the existing project specific GitHub Pages site.

On a hunch I created a (more or less) empty commit in the gh-pages branch of the dev-portal repository and pushed that to GitHub, hoping it would revive the developer portal. It did :-D.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment