dsds10
dsds10
Explore posts from servers
CDCloudflare Developers
Created by dsds10 on 8/7/2024 in #workers-for-platforms
I'm confused a bit, is "cloudflare for
got it, thank you! 🙂
8 replies
CDCloudflare Developers
Created by dsds10 on 8/7/2024 in #workers-for-platforms
I'm confused a bit, is "cloudflare for
@Chaika one last thing: Is there anyway to offer customers to route their main domain to my service? They might require to set an A record. As of https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/ I would need to contact CF in order to obtain IPs. Is this an enterprise feature?
8 replies
CDCloudflare Developers
Created by dsds10 on 8/7/2024 in #workers-for-platforms
I'm confused a bit, is "cloudflare for
Makes sense, thank you for the clarification 😉
8 replies
CDCloudflare Developers
Created by dsds10 on 8/7/2024 in #workers-for-platforms
I'm confused a bit, is "cloudflare for
@Chaika ahh now I understand, wasn't aware that Worker Routes see the actual url. That makes sense, but only the */* variant works, the other one suggests to set Worker: None – how is CF then supposed to know where to route to? It says "only routes custom hostname traffic to the Worker", but what Worker? It is set to "none", and the fallback origin is using 100::
8 replies
DTDrizzle Team
Created by dsds10 on 10/20/2023 in #help
Planetscale db:push has issues with default values
This was very helpful, thank you very much! Now it passes at least. But still gives me these update statements on every run again:
Warning You are about to execute current statements:

ALTER TABLE `follows` MODIFY COLUMN `created_at` timestamp DEFAULT CURRENT_TIMESTAMP;
ALTER TABLE `media` MODIFY COLUMN `metadata` json DEFAULT ('{}');
ALTER TABLE `posts` MODIFY COLUMN `published` boolean;
ALTER TABLE `posts` MODIFY COLUMN `published` boolean DEFAULT false;
ALTER TABLE `users` MODIFY COLUMN `is_creator` boolean NOT NULL;
ALTER TABLE `users` MODIFY COLUMN `is_creator` boolean NOT NULL DEFAULT false;
ALTER TABLE `users` MODIFY COLUMN `gender` text NOT NULL DEFAULT ('other');
ALTER TABLE `users` MODIFY COLUMN `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;
ALTER TABLE `users` MODIFY COLUMN `updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

[✓] Changes applied
Warning You are about to execute current statements:

ALTER TABLE `follows` MODIFY COLUMN `created_at` timestamp DEFAULT CURRENT_TIMESTAMP;
ALTER TABLE `media` MODIFY COLUMN `metadata` json DEFAULT ('{}');
ALTER TABLE `posts` MODIFY COLUMN `published` boolean;
ALTER TABLE `posts` MODIFY COLUMN `published` boolean DEFAULT false;
ALTER TABLE `users` MODIFY COLUMN `is_creator` boolean NOT NULL;
ALTER TABLE `users` MODIFY COLUMN `is_creator` boolean NOT NULL DEFAULT false;
ALTER TABLE `users` MODIFY COLUMN `gender` text NOT NULL DEFAULT ('other');
ALTER TABLE `users` MODIFY COLUMN `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;
ALTER TABLE `users` MODIFY COLUMN `updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

[✓] Changes applied
Is it caching the metadata or is drizzle just wrongly detecting the urge to change the schema?
4 replies
CDCloudflare Developers
Created by quambo on 6/28/2023 in #pages-help
wrangler pages dev --no-bundle causing EPERM: operation not permitted, scandir
having the same issue :/ did you solve it somehow?
3 replies