Is it possible to change my username?

For example when creating a worker, it is using my old username. Which is a company now with a new name.
20 Replies
SuperHelpflare
SuperHelpflare18h ago
Feedback
Feedback has been submitted! Thank you :)
Júlio Mühlbauer
Júlio MühlbauerOP18h ago
[username].workers.dev for example
Chaika
Chaika18h ago
In Compute & AI -> Workers & Pages right side under Account Details -> "Subdomain", a little edit button near it or magic link: https://dash.cloudflare.com/?to=/:account/workers/subdomain
Júlio Mühlbauer
Júlio MühlbauerOP18h ago
nice, thanks a lot! also I am trying to delete a project in pages
delete-all-deployments@1.0.0 start node index.js
Listing next 30 deployments, this may take a while... Failed to list deployments on page 1... retrying (1/5) Failed to list deployments on page 1... retrying (2/5) Failed to list deployments on page 1... retrying (3/5) Failed to list deployments on page 1... retrying (4/5) Failed to list deployments on page 1... retrying (5/5) Failed to list deployments on page 1. Error: Could not fetch deployments for reland at listDeploymentsPerPage (C:\Users\julio\Downloads\delete-all-deployments\index.js:73:11) at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Júlio Mühlbauer
Júlio MühlbauerOP18h ago
Cloudflare Docs
Known issues
Here are some known bugs and issues with Cloudflare Pages:
Júlio Mühlbauer
Júlio MühlbauerOP18h ago
So I need to delete all deployments
Júlio Mühlbauer
Júlio MühlbauerOP18h ago
the project name would be reland, right?
No description
Júlio Mühlbauer
Júlio MühlbauerOP18h ago
it did not work for me oh, I had to put view and edit permissions on cloudflare pages this need to be put in the docs
Chaika
Chaika18h ago
oh yea that is weird it's left out, at least you figured it out, yea an api key by default can't do anything w/o any permissions
Júlio Mühlbauer
Júlio MühlbauerOP12h ago
also, is it possible to change env variables by uploading a .env or with api/cli like vercel? it is a pain in the ass to enter one by one, also I accidenyl put in the workers runtime instead of build, lots some minutes of my life
Chaika
Chaika12h ago
If it's for runtime and not build, you can paste an .env file when adding on the dash, it looks like the Build environment variables don't support that in the dashboard yet though
Júlio Mühlbauer
Júlio MühlbauerOP12h ago
sad 🙁 when using for deploying apps like ts start I need to setup in the build, right? or both? it is strange, because in Vercel and Netlify there is only one way to configure and both support importin .env files
Chaika
Chaika12h ago
Normal Environment variables are available in your code running on the edge, like in process.env (if using nodejs compat) or the env object. Build Environment variables are restricted to the build environment and just exposed as literal enviroment variables (like if your site has to pull down some data from a private api to build, or for naother package, etc) ts is what? tanstack start?
Júlio Mühlbauer
Júlio MühlbauerOP12h ago
tanstack start yeah well, so I have to use the build runtime? because I check with zod all variables in the build and it is failing I have variables with the VITE_ prefix, so I need them in the runtime But also build
Chaika
Chaika12h ago
build runtime? I haven't used tanstack before, so I can only speak to how the platform works. Usually, if you're using server-side rendering or running requests on the server, they should pull from the normal environment variables attached to your Worker. Client-side ones would likely be included at bundle time or passed down from the server if using SSR, I'd imagine. The normal env vars ones can import a .env file, so should be easy to paste them all in there (be sure to properly mark the secrets) and try that way as well
Júlio Mühlbauer
Júlio MühlbauerOP12h ago
What is normal env vars? Are referreing runtime?
Chaika
Chaika12h ago
The normal ones are under Variables and Secrets in the dashboard, available when the worker is running on edge/the actual code The client-side ones should be non-secrets, you could try a proper .env file as well: https://tanstack.com/start/latest/docs/framework/react/environment-variables#file-hierarchy-loaded-in-order, it says it should load those
Júlio Mühlbauer
Júlio MühlbauerOP11h ago
hmm, could not get to work
Júlio Mühlbauer
Júlio MühlbauerOP11h ago
my env.ts
import { z } from "zod";
import dotenv from "dotenv";

dotenv.config();

export const envVariables = z.object({
DATABASE_URL: z.string(),

VITE_POSTHOG_KEY: z.string().optional(),
VITE_POSTHOG_HOST: z.string().optional(),

VITE_GOOGLE_CLIENT_ID: z.string(),
GOOGLE_CLIENT_SECRET: z.string(),
GOOGLE_API_KEY: z.string(),

R2_SECRET_ACCESS_KEY: z.string(),
R2_ACCOUNT_ID: z.string(),
R2_ACCESS_KEY_ID: z.string(),
});

envVariables.parse(process.env);

declare global {
namespace NodeJS {
interface ProcessEnv extends z.infer<typeof envVariables> {}
}
}

declare module "bun" {
interface Env extends z.infer<typeof envVariables> {}
}
import { z } from "zod";
import dotenv from "dotenv";

dotenv.config();

export const envVariables = z.object({
DATABASE_URL: z.string(),

VITE_POSTHOG_KEY: z.string().optional(),
VITE_POSTHOG_HOST: z.string().optional(),

VITE_GOOGLE_CLIENT_ID: z.string(),
GOOGLE_CLIENT_SECRET: z.string(),
GOOGLE_API_KEY: z.string(),

R2_SECRET_ACCESS_KEY: z.string(),
R2_ACCOUNT_ID: z.string(),
R2_ACCESS_KEY_ID: z.string(),
});

envVariables.parse(process.env);

declare global {
namespace NodeJS {
interface ProcessEnv extends z.infer<typeof envVariables> {}
}
}

declare module "bun" {
interface Env extends z.infer<typeof envVariables> {}
}
I simply import this into vite.config.ts And I have this wrangler: { "name": "reland", "compatibility_date": "2025-09-02", "compatibility_flags": ["nodejs_compat"], "main": "@tanstack/react-start/server-entry" }

Did you find this page helpful?