now that we have the staff response that you can’t, let’s move on to the juicy workaround ideas
remix through the API
the remixing API lets you specify a preferred project domain, and it does a pretty good job. though I suppose this isn’t applicable here because you’re targeting a web workflow.
maybe you could have a server that has its own Glitch login credentials to create the project and subsequently use the API to transfer ownership to the user. but who knows how hard it is to prevent people from abusing such a service?
curious that there’s indeed a route set up in the glitch frontend to read parameters from that
.../preferred-domain/original-project-guid format you mentioned in the first post but that it isn’t hooked up to this API.
and I suppose if you were doing this from a backend area, you could just as easily create one without a preferred domain and record what gets created.
imagine this: you embed an iframe to the remix URL. Glitch remixes it and opens the editor. the editor (as of recently) embeds another iframe with a preview of the app.
what if the preview of the remixed project would do a
postMessage to window.parent.parent to inform your site of the domain that it’s running on? that seems like it could work.
remixed project phones home
supposedly you can specify environment variables to add to the remixed project. maybe what you could do is give a user of your website some unique ID, set that to be added to the remixed project’s environment, then have the template project be designed that when it first boots up, it looks at the environment and uploads something to your site associating that user ID with its project domain. now your site knows that user’s remixed project domain.
I think I might try the middle one myself