|
| 1 | +# Domain Migration Plan |
| 2 | + |
| 3 | +This document describes the steps to move the `interuista` project under the |
| 4 | +PythonMilano GitHub organization and configure GitHub Pages with a custom domain. |
| 5 | + |
| 6 | +## Current State |
| 7 | + |
| 8 | +- Repository: `keobox/interuista` |
| 9 | +- GitHub Pages URL: `https://keobox.github.io/interuista` |
| 10 | +- `publishconf.py` SITEURL: `https://keobox.github.io/interuista` |
| 11 | + |
| 12 | +## Phase 1: Transfer repository to PythonMilano |
| 13 | + |
| 14 | +1. Go to `https://github.com/keobox/interuista` -> **Settings** -> **General** |
| 15 | +2. Scroll to **Danger Zone** -> click **Transfer repository** |
| 16 | +3. Select **PythonMilano** as the new owner |
| 17 | +4. Confirm the transfer |
| 18 | + |
| 19 | +After transfer: |
| 20 | +- The repo will be at `https://github.com/PythonMilano/interuista` |
| 21 | +- GitHub automatically redirects the old URL |
| 22 | +- You keep contributor access |
| 23 | + |
| 24 | +## Phase 2: GitHub Pages on the org subpath |
| 25 | + |
| 26 | +After the transfer, GitHub Pages will serve the site as a **project site** under |
| 27 | +the PythonMilano organization. |
| 28 | + |
| 29 | +Since `PythonMilano/pythonmilano.github.io` uses the custom domain `milano.python.it`, |
| 30 | +the site will be available at: `https://milano.python.it/interuista` |
| 31 | + |
| 32 | +Update `publishconf.py`: |
| 33 | + |
| 34 | +```python |
| 35 | +SITEURL = "https://milano.python.it/interuista" |
| 36 | +``` |
| 37 | + |
| 38 | +This is the interim setup until the custom domain is ready. |
| 39 | + |
| 40 | +## Phase 3: Custom domain (`intervistapythonista.com`) |
| 41 | + |
| 42 | +When ready to use the dedicated domain: |
| 43 | + |
| 44 | +### 1. Configure DNS |
| 45 | + |
| 46 | +At your domain registrar for `intervistapythonista.com`, add one of: |
| 47 | + |
| 48 | +**Option A - CNAME (recommended for apex or www):** |
| 49 | + |
| 50 | +| Type | Name | Value | |
| 51 | +|-------|------|----------------------------| |
| 52 | +| CNAME | @ | pythonmilano.github.io | |
| 53 | + |
| 54 | +Note: some registrars don't support CNAME on apex domains. In that case use Option B |
| 55 | +or set up the CNAME on `www` and redirect apex to www. |
| 56 | + |
| 57 | +**Option B - A records (for apex domain):** |
| 58 | + |
| 59 | +| Type | Name | Value | |
| 60 | +|------|------|------------------| |
| 61 | +| A | @ | 185.199.108.153 | |
| 62 | +| A | @ | 185.199.109.153 | |
| 63 | +| A | @ | 185.199.110.153 | |
| 64 | +| A | @ | 185.199.111.153 | |
| 65 | + |
| 66 | +Optionally add a CNAME for `www`: |
| 67 | + |
| 68 | +| Type | Name | Value | |
| 69 | +|-------|------|------------------------------| |
| 70 | +| CNAME | www | pythonmilano.github.io | |
| 71 | + |
| 72 | +### 2. Configure GitHub Pages custom domain |
| 73 | + |
| 74 | +1. Go to `https://github.com/PythonMilano/interuista` -> **Settings** -> **Pages** |
| 75 | +2. Under **Custom domain**, enter `intervistapythonista.com` |
| 76 | +3. Click **Save** (this creates a `CNAME` file in the repo) |
| 77 | +4. Wait for DNS to propagate (can take up to 24-48 hours) |
| 78 | +5. Check **Enforce HTTPS** once the DNS check passes |
| 79 | + |
| 80 | +### 3. Update Pelican configuration |
| 81 | + |
| 82 | +Update `publishconf.py`: |
| 83 | + |
| 84 | +```python |
| 85 | +SITEURL = "https://intervistapythonista.com" |
| 86 | +``` |
| 87 | + |
| 88 | +### 4. Verify |
| 89 | + |
| 90 | +- `https://intervistapythonista.com` serves the site |
| 91 | +- HTTPS works correctly |
| 92 | +- The org site `milano.python.it` is unaffected |
| 93 | + |
| 94 | +## Notes |
| 95 | + |
| 96 | +- Each project repo under an organization can have its own independent custom domain, |
| 97 | + it won't conflict with `milano.python.it` on the org site. |
| 98 | +- If you want a personal fork after the transfer, you can fork it back to your |
| 99 | + personal account from PythonMilano. |
0 commit comments