Skip to content
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.

repoint project-repos.ipfs.io to existing gh pages site #27

Closed
harlantwood opened this issue Dec 30, 2015 · 4 comments
Closed

repoint project-repos.ipfs.io to existing gh pages site #27

harlantwood opened this issue Dec 30, 2015 · 4 comments

Comments

@harlantwood
Copy link
Collaborator

Deploying to IPNS is currently a lot of work (see #9, #11, ipfs/infra#137 for more details).

@jbenet said in #11 (comment):

publishing to IPNS wont work, unless you run CI every few hours. the reason is that IPNS needs to be republished over time.
We'll be changing that to allow other nodes to re-share records-- it's a major protocol issue.

Right now, with every push to master, we rebuild this app and deploy to github pages.

Until IPNS is more baked, and perhaps until we have a unified strategy for deploying apps to IPNS, let's use what is already working, and point the CNAME for project-repos.ipfs.io to ipfs.github.io. @lgierth will you make this so?

@harlantwood
Copy link
Collaborator Author

@jbenet will you point the CNAME for
project-repos.ipfs.io
to
ipfs.github.io? Discussion above.

I want to get this thing out. We can do more fancy self hosting later. Right now it works, and I'd like to point to it at our own subdomain.

@jbenet
Copy link

jbenet commented Jan 9, 2016

i would, but there's a lot of records on there atm-- @lgierth are we using
any? ok to do the CNAME?

@ghost
Copy link

ghost commented Jan 9, 2016

Sorry I totally missed this despite the highlight, sorry -- taking care of it in ipfs-inactive/ops-requests#9

@harlantwood
Copy link
Collaborator Author

NP, Next time I'll post to ops-requests.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants