Domain and deployment

Just quick questions for keeping track of infra things:

• Is this deployed through IPFS or github pages?
• Where's the domain registered? (We should move it to Gandi and DNSimple)

[mikeal]

• github pages
• iwantmyname.com, i can migrate it to whatever we like whenever we decide to do so.

[mikeal]

For the DNS migration, let's do that after DWeb but before we do any kind of public promotion about this resources.

Thanks! Yeah let's definitely do it only after DWeb Summit

[mikeal]

It's after DWeb :)

Let me know when it's a good time to migrate the DNS :)

Cool -- could you give me access to the account so I can just do it in one go, without coordination? If there's anything else in the account, I can also initiate a traditional domain transfer, and you'd give me the token, and later confirm the transfer.

---

Regarding deployment, you can do something like what PeerPad does: https://github.com/ipfs-shipyard/peer-pad/blob/master/ci/Jenkinsfile

The ci/Jenkinsfile triggers the build, and record sets a branch-recordname mapping, i.e. master commits will update /ipns/dev.peerpad.net and production commits will update /ipns/peerpad.net.

Regardless of any branch/record mappings, you get the website built and the link displayed via Github's commit build status.

[mikeal]

It's my personal iwantmyname.com account so I'd prefer to just walk through the transfer in a private channel (Slack?).

RE: Jenkins

I don't have any opinions about the deployment environment. I assume that, given I don't have access to infra, I won't be responsible for maintaining it, so whatever the people doing the work are comfortable with is fine with me. I would just prefer that:

• Master commits deploy to "production."
• Each commit/push gets an IPFS-only content-addressable deploy.

Okay get me a transfer authorization code :)

We'll have to wait until the domain is at least 60 days old: https://www.gandi.net/en/tlds/school/rules

[terichadbourne]

@lgierth @mikeal Is this issue still relevant? If so, has enough time passed for us to make the change and close out this issue?

Note that since this issue was first opened, what used to be a repo within the ipfs-shipyard org became its own org, and there are now additional repos for local chapters, all of which need to be able to deploy using GH pages. I don't understand the context of this issue well enough to know whether this is relevant. We also now use "code" instead of "master" as the main branch of the protoschool.github.io repo because of the way Vue and GitHub pages need to work together to deploy.

Note that we are launching publicly next Monday (Jan 14), so if we need to take any steps that could bring the site down I'd like to avoid that date please. 😂

This can wait, go launch the thing :):)