Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Use DNSLink #274

Closed
Stebalien opened this issue Jul 18, 2019 · 5 comments
Closed

Feature: Use DNSLink #274

Stebalien opened this issue Jul 18, 2019 · 5 comments
Labels
enhancement New feature or request future

Comments

@Stebalien
Copy link
Contributor

I'm not sure if this is possible but it would be awesome if proto.school could use DNSLink. I'm preparing for some potentially offline presentations and was able to simply "pin" dag.ipfs.io, explore.ipld.io, and cid.ipfs.io, but not proto.school.

@Stebalien Stebalien added the enhancement New feature or request label Jul 18, 2019
@terichadbourne
Copy link
Member

I don't know a ton about domains, deployment, or DNSLink, but I would guess that this suggestion might be dependent on #18? Does that sound right @mikeal? (We're currently publishing via GitHub Pages, and we need our chapter repos to continue being able to do that.)

@hacdias
Copy link
Member

hacdias commented Nov 13, 2019

@terichadbourne I think this is a must: having ProtoSchool on IPFS itself would be awesome.

If I understand correctly, each chapter can publish to https://proto.school/<city>, right? If so, I think it will be a bit harder to put this on IPFS, otherwise it should be rather simple.

Copy link
Member

Yes that's right @hacdias, and we also have the issue where we're using hash-based routing within the whole Vue SPA, which I know can sometimes make it harder to host on IPFS.

Perhaps another issue would be how localStorage works? If there would be an IPFS-hosted and a "normally"-hosted version of the site, I assume the caching of the user's progress wouldn't be recognized unless they always visited it the same way?

I'm starting to think that this issue might actually be a duplicate of #18 rather than just dependent on it, but I'm not familiar enough with infra stuff to confirm. @hacdias would you mind taking a look? Especially at the discussion starting here: #18 (comment)

If we're really having the same convo in two places, we should consolidate into #18.

@hacdias
Copy link
Member

hacdias commented Nov 15, 2019

@terichadbourne yes, they are kind of related. It seems to me that #18 already encompasses the usage of DNSLink so, yes, I would close one of them in favour of the other.

hash-based routing within the whole Vue SPA, which I know can sometimes make it harder to host on IPFS.

Not sure if I'm understanding correctly, but Web UI also uses hash-based routing and it works perfectly when hosted on IPFS 😃

Perhaps another issue would be how localStorage works? If there would be an IPFS-hosted and a "normally"-hosted version of the site, I assume the caching of the user's progress wouldn't be recognized unless they always visited it the same way?

You are correct!

@terichadbourne
Copy link
Member

Thanks @hacdias! I'll close this one in favor of continuing conversation in #18.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request future
Projects
None yet
Development

No branches or pull requests

3 participants