Is anyone know if is possible to retrieve a web site from pages.dev? We deleted the github repo whic
Is anyone know if is possible to retrieve a web site from pages.dev? We deleted the github repo which contained the actual website.
WYou can restore deleted github repos for 90 days. https://docs.github.com/en/repositories/creating-and-managing-repositories/restoring-a-deleted-repository
SThanks, was deleted more than 1 year ago. The repo was deployed last time 3 years ago 
EYou cant retrieve the source code, best you can do is list the files on the dashboard and then download those files manually
Ldoh! that doesn't sound fun.
Ba direct upload does not count as a build?
Wno
Wit doesn't spin up a build :p
Bso i can build my project on the free plan with a lot of users?
Byou probably don't know enough about it to answer that. but each user will get their own project, we have direct upload, and each will have under 100 subdomains
B@Walshy I'm reading Setup Pages for a SaaS platform and trying to follow it. Does every customer have a CNAME to customers.example.com? If so how is a user directed to a customer's website without a server?
ISo Cloudflare will internally look at the association of sites to pages projects and send the request to the Pages site that has the customer's hostname.
IYou add the customer's hostname to Pages (but then CNAME to the main one, customers.example.com)
IThen Pages knows where to send requests.
I(correct me if I'm wrong though Walshy)
Wso for one project for all customers, they can share a cname e.g.
for one project per-customer best to do their own cname so
customers.example.comfor one project per-customer best to do their own cname so
<customer-name>.customers.example.comyup
Bhow do I add the customer's hostname to pages?
BI am not doing one project for all customers. What is a use-case for doing that?
IYou'll need to use the API probably. If you have 1 or 2 customers you can manually add them in the dashboard but that won't scale to many customers.
Wthere's saas' where they aren't changing much per-customer in the looks department, it's mostly just loading backend data so they can use a Function to handle both of those (rewrite HTML + fetch data)
Wthose can have thousands of customers on a single project
Bi am testing adding a subdomain on the dashboard and got
Verification is in undefined statusnow it is working
B@Walshy I am going to do the approach of a subdomain for each user, so user.customers.example.com, but to test it I tried adding customers.example.com to two different projects and on the second got
That domain is already associated with an existing project. Use a different domain or find the project already using this domain and remove it.Is that expected?
Wso user.customers.example.com, but to test it I tried adding customers.example.com
did you add two distinct user domains or
customersif the latter, then yeah, the error is what it says
BBoth projects have customers.example.com
Wyeah that'll be why, you'd need <user>.customers.
BRight I would expect this error, that's what I was asking about earlier. But the docs you shared suggest this approach I think?
Wit says you can do that, it's mainly setting up a single project there not multiple
Wgoes back to the different way of saasing, one project vs multiple
for you, you'd want a customer domain per-project whereas one project can share
for you, you'd want a customer domain per-project whereas one project can share
Bok I think the docs could be more clear. I'm happy to make a contribution btw
B@Isaac McFadyen I may have misunderstood your messages, if not then I'm not sure we're on the same page about how this works
B@Walshy there is a way I could do it so there is a project per user, and also all users have customers.example.com. But I'd need to add some kind of server code right?
Wyou'd need a worker in front to route based on hostname (or whatever)
Bso this means I'm adding a new DNS record to my website for each customer right? e.g. user1.customers.example.com user2.customers.example.com
Bso at some point I'd reach the limit of DNS records, and it's a bit messy to manage
Wthis is why automation is good :p
Bi'm not worried about automation, just about limits
Wbut sure, you can use a worker instead and not do it that way
Band not really worried about it, just making sure I understand it correctly
Wraising limits is easy
Bso it's true that each user needs one record on my domain
Wif you didn't want to throw a worker in front yeah
Wbut you can also easily throw a worker in front
Wjust means you pay for each request
Byeah i'll avoid it for now
Wpages has multiple dns records per project, trust me dns limits aren't a big deal haha
