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.

Sign up for GitHub

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

Update README to reference second glitch project #102

Merged
merged 1 commit into from
Sep 21, 2022
Merged

Update README to reference second glitch project #102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,12 +26,17 @@ We have couple of test domains, that all resolve to `privacy-test-pages.glitch.m
- `good.third-party.site` - non-tracking third party, it's not on our blocklist and will not be blocked by our clients
- `broken.third-party.site` - tracking third party that we can't block (e.g. due to brekage), it's on our blocklist, but it will not be blocked by our clients
- `bad.third-party.site` - tracking third party that's on our blocklist and our clients will block

We also have additional test domains that resolve to `ad-attribution-test-pages.glitch.me`, specifically for the Ad Attribution tests hosted [here](https://www.search-company.site):

- `www.search-company.site` - Simulated search provider
- `convert.ad-company.site` - Simulated ad provider conversion ping
- `www.ad-company.site` - Simulated ad provider non-conversion ping
- `www.payment-company.site` - Simulated payment provider
- `www.publisher-company.site`- Simulated publisher website

The ad attribution test domains resolve to a separate glitch project due to glitch domain limits (i.e., 5 domains per project). Otherwise the projects are identical.

### How to test it locally

If you are working on a simple page you can start any local server (e.g. `python -m SimpleHTTPServer 8000`) in the main folder of the project.
Expand Down Expand Up @@ -85,4 +90,4 @@ This will generate two files (`first-party.example+11-key.pem` and `first-party.

## How to deploy it?

After PR is merged test pages are automatically deployed to glitch ([code](https://glitch.com/edit/#!/privacy-test-pages)) and github pages (legacy).
After PR is merged test pages are automatically deployed to glitch ([privacy-test-pages](https://glitch.com/edit/#!/privacy-test-pages) and [ad-attribution-test-pages](https://glitch.com/edit/#!/ad-attribution-test-pages)) and github pages (legacy).