BranchesTags

Repository files navigation

Payload Cloudflare Template

Deploy to Cloudflare

This can only be deployed on Paid Workers right now due to size limits. This template comes configured with the bare minimum to get started on anything you need.

Quick start

This template can be deployed directly to Cloudflare Workers by clicking the button to take you to the setup screen.

From there you can connect your code to a git provider such Github or Gitlab, name your Workers, D1 Database and R2 Bucket as well as attach any additional environment variables or services you need.

Quick Start - local setup

To spin up this template locally, follow these steps:

Clone

After you click the Deploy button above, you'll want to have standalone copy of this repo on your machine. Cloudflare will connect your app to a git provider such as Github and you can access your code from there.

Local Development

How it works

Out of the box, using Wrangler will automatically create local bindings for you to connect to the remote services and it can even create a local mock of the services you're using with Cloudflare.

We've pre-configured Payload for you with the following:

Collections

See the Collections docs for details on how to extend this functionality.

  • Users (Authentication)

    Users are auth-enabled collections that have access to the admin panel.

    For additional help, see the official Auth Example or the Authentication docs.

  • Media

    This is the uploads enabled collection.

Image Storage (R2)

Images will be served from an R2 bucket which you can then further configure to use a CDN to serve for your frontend directly.

D1 Database

The Worker will have direct access to a D1 SQLite database which Wrangler can connect locally to, just note that you won't have a connection string as you would typically with other providers.

You can enable read replicas by adding readReplicas: 'first-primary' in the DB adapter and then enabling it on your D1 Cloudflare dashboard. Read more about this feature on our docs.

Working with Cloudflare

Firstly, after installing dependencies locally you need to authenticate with Wrangler by running:

pnpm wrangler login

This will take you to Cloudflare to login and then you can use the Wrangler CLI locally for anything, use pnpm wrangler help to see all available options.

Wrangler is pretty smart so it will automatically bind your services for local development just by running pnpm dev.

Deployments

When you're ready to deploy, first make sure you have created your migrations:

pnpm payload migrate:create

Then run the following command:

pnpm run deploy

This will spin up Wrangler in production mode, run any created migrations, build the app and then deploy the bundle up to Cloudflare.

That's it! You can if you wish move these steps into your CI pipeline as well.

Enabling logs

By default logs are not enabled for your API, we've made this decision because it does run against your quota so we've left it opt-in. But you can easily enable logs in one click in the Cloudflare panel, see docs.

Known issues

GraphQL

We are currently waiting on some issues with GraphQL to be fixed upstream in Workers so full support for GraphQL is not currently guaranteed when deployed.

Worker size limits

We currently recommend deploying this template to the Paid Workers plan due to bundle size limits of 3mb. We're actively trying to reduce our bundle footprint over time to better meet this metric.

This also applies to your own code, in the case of importing a lot of libraries you may find yourself limited by the bundle.

Questions

If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.

About

No description, website, or topics provided.

Resources

Readme
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
BranchesTags
Repository files navigation
Payload Cloudflare Template
Deploy to Cloudflare
This can only be deployed on Paid Workers right now due to size limits. This template comes configured with the bare minimum to get started on anything you need.
Quick start
This template can be deployed directly to Cloudflare Workers by clicking the button to take you to the setup screen.
From there you can connect your code to a git provider such Github or Gitlab, name your Workers, D1 Database and R2 Bucket as well as attach any additional environment variables or services you need.
Quick Start - local setup
To spin up this template locally, follow these steps:
Clone
After you click the Deploy button above, you'll want to have standalone copy of this repo on your machine. Cloudflare will connect your app to a git provider such as Github and you can access your code from there.
Local Development
How it works
Out of the box, using Wrangler will automatically create local bindings for you to connect to the remote services and it can even create a local mock of the services you're using with Cloudflare.
We've pre-configured Payload for you with the following:
Collections
See the Collections docs for details on how to extend this functionality.
  • Users (Authentication)
    Users are auth-enabled collections that have access to the admin panel.
    For additional help, see the official Auth Example or the Authentication docs.
  • Media
    This is the uploads enabled collection.
Image Storage (R2)
Images will be served from an R2 bucket which you can then further configure to use a CDN to serve for your frontend directly.
D1 Database
The Worker will have direct access to a D1 SQLite database which Wrangler can connect locally to, just note that you won't have a connection string as you would typically with other providers.
You can enable read replicas by adding readReplicas: 'first-primary' in the DB adapter and then enabling it on your D1 Cloudflare dashboard. Read more about this feature on our docs.
Working with Cloudflare
Firstly, after installing dependencies locally you need to authenticate with Wrangler by running:
pnpm wrangler login
This will take you to Cloudflare to login and then you can use the Wrangler CLI locally for anything, use pnpm wrangler help to see all available options.
Wrangler is pretty smart so it will automatically bind your services for local development just by running pnpm dev.
Deployments
When you're ready to deploy, first make sure you have created your migrations:
pnpm payload migrate:create
Then run the following command:
pnpm run deploy
This will spin up Wrangler in production mode, run any created migrations, build the app and then deploy the bundle up to Cloudflare.
That's it! You can if you wish move these steps into your CI pipeline as well.
Enabling logs
By default logs are not enabled for your API, we've made this decision because it does run against your quota so we've left it opt-in. But you can easily enable logs in one click in the Cloudflare panel, see docs.
Known issues
GraphQL
We are currently waiting on some issues with GraphQL to be fixed upstream in Workers so full support for GraphQL is not currently guaranteed when deployed.
Worker size limits
We currently recommend deploying this template to the Paid Workers plan due to bundle size limits of 3mb. We're actively trying to reduce our bundle footprint over time to better meet this metric.
This also applies to your own code, in the case of importing a lot of libraries you may find yourself limited by the bundle.
Questions
If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Payload Cloudflare Template
Deploy to Cloudflare
This can only be deployed on Paid Workers right now due to size limits. This template comes configured with the bare minimum to get started on anything you need.
Quick start
This template can be deployed directly to Cloudflare Workers by clicking the button to take you to the setup screen.
From there you can connect your code to a git provider such Github or Gitlab, name your Workers, D1 Database and R2 Bucket as well as attach any additional environment variables or services you need.
Quick Start - local setup
To spin up this template locally, follow these steps:
Clone
After you click the Deploy button above, you'll want to have standalone copy of this repo on your machine. Cloudflare will connect your app to a git provider such as Github and you can access your code from there.
Local Development
How it works
Out of the box, using Wrangler will automatically create local bindings for you to connect to the remote services and it can even create a local mock of the services you're using with Cloudflare.
We've pre-configured Payload for you with the following:
Collections
See the Collections docs for details on how to extend this functionality.
  • Users (Authentication)
    Users are auth-enabled collections that have access to the admin panel.
    For additional help, see the official Auth Example or the Authentication docs.
  • Media
    This is the uploads enabled collection.
Image Storage (R2)
Images will be served from an R2 bucket which you can then further configure to use a CDN to serve for your frontend directly.
D1 Database
The Worker will have direct access to a D1 SQLite database which Wrangler can connect locally to, just note that you won't have a connection string as you would typically with other providers.
You can enable read replicas by adding readReplicas: 'first-primary' in the DB adapter and then enabling it on your D1 Cloudflare dashboard. Read more about this feature on our docs.
Working with Cloudflare
Firstly, after installing dependencies locally you need to authenticate with Wrangler by running:
pnpm wrangler login
This will take you to Cloudflare to login and then you can use the Wrangler CLI locally for anything, use pnpm wrangler help to see all available options.
Wrangler is pretty smart so it will automatically bind your services for local development just by running pnpm dev.
Deployments
When you're ready to deploy, first make sure you have created your migrations:
pnpm payload migrate:create
Then run the following command:
pnpm run deploy
This will spin up Wrangler in production mode, run any created migrations, build the app and then deploy the bundle up to Cloudflare.
That's it! You can if you wish move these steps into your CI pipeline as well.
Enabling logs
By default logs are not enabled for your API, we've made this decision because it does run against your quota so we've left it opt-in. But you can easily enable logs in one click in the Cloudflare panel, see docs.
Known issues
GraphQL
We are currently waiting on some issues with GraphQL to be fixed upstream in Workers so full support for GraphQL is not currently guaranteed when deployed.
Worker size limits
We currently recommend deploying this template to the Paid Workers plan due to bundle size limits of 3mb. We're actively trying to reduce our bundle footprint over time to better meet this metric.
This also applies to your own code, in the case of importing a lot of libraries you may find yourself limited by the bundle.
Questions
If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Payload Cloudflare Template
Deploy to Cloudflare
This can only be deployed on Paid Workers right now due to size limits. This template comes configured with the bare minimum to get started on anything you need.
Quick start
This template can be deployed directly to Cloudflare Workers by clicking the button to take you to the setup screen.
From there you can connect your code to a git provider such Github or Gitlab, name your Workers, D1 Database and R2 Bucket as well as attach any additional environment variables or services you need.
Quick Start - local setup
To spin up this template locally, follow these steps:
Clone
After you click the Deploy button above, you'll want to have standalone copy of this repo on your machine. Cloudflare will connect your app to a git provider such as Github and you can access your code from there.
Local Development
How it works
Out of the box, using Wrangler will automatically create local bindings for you to connect to the remote services and it can even create a local mock of the services you're using with Cloudflare.
We've pre-configured Payload for you with the following:
Collections
See the Collections docs for details on how to extend this functionality.
  • Users (Authentication)
    Users are auth-enabled collections that have access to the admin panel.
    For additional help, see the official Auth Example or the Authentication docs.
  • Media
    This is the uploads enabled collection.
Image Storage (R2)
Images will be served from an R2 bucket which you can then further configure to use a CDN to serve for your frontend directly.
D1 Database
The Worker will have direct access to a D1 SQLite database which Wrangler can connect locally to, just note that you won't have a connection string as you would typically with other providers.
You can enable read replicas by adding readReplicas: 'first-primary' in the DB adapter and then enabling it on your D1 Cloudflare dashboard. Read more about this feature on our docs.
Working with Cloudflare
Firstly, after installing dependencies locally you need to authenticate with Wrangler by running:
pnpm wrangler login
This will take you to Cloudflare to login and then you can use the Wrangler CLI locally for anything, use pnpm wrangler help to see all available options.
Wrangler is pretty smart so it will automatically bind your services for local development just by running pnpm dev.
Deployments
When you're ready to deploy, first make sure you have created your migrations:
pnpm payload migrate:create
Then run the following command:
pnpm run deploy
This will spin up Wrangler in production mode, run any created migrations, build the app and then deploy the bundle up to Cloudflare.
That's it! You can if you wish move these steps into your CI pipeline as well.
Enabling logs
By default logs are not enabled for your API, we've made this decision because it does run against your quota so we've left it opt-in. But you can easily enable logs in one click in the Cloudflare panel, see docs.
Known issues
GraphQL
We are currently waiting on some issues with GraphQL to be fixed upstream in Workers so full support for GraphQL is not currently guaranteed when deployed.
Worker size limits
We currently recommend deploying this template to the Paid Workers plan due to bundle size limits of 3mb. We're actively trying to reduce our bundle footprint over time to better meet this metric.
This also applies to your own code, in the case of importing a lot of libraries you may find yourself limited by the bundle.
Questions
If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
BranchesTags
Repository files navigation
Payload Cloudflare Template
Deploy to Cloudflare
This can only be deployed on Paid Workers right now due to size limits. This template comes configured with the bare minimum to get started on anything you need.
Quick start
This template can be deployed directly to Cloudflare Workers by clicking the button to take you to the setup screen.
From there you can connect your code to a git provider such Github or Gitlab, name your Workers, D1 Database and R2 Bucket as well as attach any additional environment variables or services you need.
Quick Start - local setup
To spin up this template locally, follow these steps:
Clone
After you click the Deploy button above, you'll want to have standalone copy of this repo on your machine. Cloudflare will connect your app to a git provider such as Github and you can access your code from there.
Local Development
How it works
Out of the box, using Wrangler will automatically create local bindings for you to connect to the remote services and it can even create a local mock of the services you're using with Cloudflare.
We've pre-configured Payload for you with the following:
Collections
See the Collections docs for details on how to extend this functionality.
  • Users (Authentication)
    Users are auth-enabled collections that have access to the admin panel.
    For additional help, see the official Auth Example or the Authentication docs.
  • Media
    This is the uploads enabled collection.
Image Storage (R2)
Images will be served from an R2 bucket which you can then further configure to use a CDN to serve for your frontend directly.
D1 Database
The Worker will have direct access to a D1 SQLite database which Wrangler can connect locally to, just note that you won't have a connection string as you would typically with other providers.
You can enable read replicas by adding readReplicas: 'first-primary' in the DB adapter and then enabling it on your D1 Cloudflare dashboard. Read more about this feature on our docs.
Working with Cloudflare
Firstly, after installing dependencies locally you need to authenticate with Wrangler by running:
pnpm wrangler login
This will take you to Cloudflare to login and then you can use the Wrangler CLI locally for anything, use pnpm wrangler help to see all available options.
Wrangler is pretty smart so it will automatically bind your services for local development just by running pnpm dev.
Deployments
When you're ready to deploy, first make sure you have created your migrations:
pnpm payload migrate:create
Then run the following command:
pnpm run deploy
This will spin up Wrangler in production mode, run any created migrations, build the app and then deploy the bundle up to Cloudflare.
That's it! You can if you wish move these steps into your CI pipeline as well.
Enabling logs
By default logs are not enabled for your API, we've made this decision because it does run against your quota so we've left it opt-in. But you can easily enable logs in one click in the Cloudflare panel, see docs.
Known issues
GraphQL
We are currently waiting on some issues with GraphQL to be fixed upstream in Workers so full support for GraphQL is not currently guaranteed when deployed.
Worker size limits
We currently recommend deploying this template to the Paid Workers plan due to bundle size limits of 3mb. We're actively trying to reduce our bundle footprint over time to better meet this metric.
This also applies to your own code, in the case of importing a lot of libraries you may find yourself limited by the bundle.
Questions
If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Payload Cloudflare Template
Deploy to Cloudflare
This can only be deployed on Paid Workers right now due to size limits. This template comes configured with the bare minimum to get started on anything you need.
Quick start
This template can be deployed directly to Cloudflare Workers by clicking the button to take you to the setup screen.
From there you can connect your code to a git provider such Github or Gitlab, name your Workers, D1 Database and R2 Bucket as well as attach any additional environment variables or services you need.
Quick Start - local setup
To spin up this template locally, follow these steps:
Clone
After you click the Deploy button above, you'll want to have standalone copy of this repo on your machine. Cloudflare will connect your app to a git provider such as Github and you can access your code from there.
Local Development
How it works
Out of the box, using Wrangler will automatically create local bindings for you to connect to the remote services and it can even create a local mock of the services you're using with Cloudflare.
We've pre-configured Payload for you with the following:
Collections
See the Collections docs for details on how to extend this functionality.
  • Users (Authentication)
    Users are auth-enabled collections that have access to the admin panel.
    For additional help, see the official Auth Example or the Authentication docs.
  • Media
    This is the uploads enabled collection.
Image Storage (R2)
Images will be served from an R2 bucket which you can then further configure to use a CDN to serve for your frontend directly.
D1 Database
The Worker will have direct access to a D1 SQLite database which Wrangler can connect locally to, just note that you won't have a connection string as you would typically with other providers.
You can enable read replicas by adding readReplicas: 'first-primary' in the DB adapter and then enabling it on your D1 Cloudflare dashboard. Read more about this feature on our docs.
Working with Cloudflare
Firstly, after installing dependencies locally you need to authenticate with Wrangler by running:
pnpm wrangler login
This will take you to Cloudflare to login and then you can use the Wrangler CLI locally for anything, use pnpm wrangler help to see all available options.
Wrangler is pretty smart so it will automatically bind your services for local development just by running pnpm dev.
Deployments
When you're ready to deploy, first make sure you have created your migrations:
pnpm payload migrate:create
Then run the following command:
pnpm run deploy
This will spin up Wrangler in production mode, run any created migrations, build the app and then deploy the bundle up to Cloudflare.
That's it! You can if you wish move these steps into your CI pipeline as well.
Enabling logs
By default logs are not enabled for your API, we've made this decision because it does run against your quota so we've left it opt-in. But you can easily enable logs in one click in the Cloudflare panel, see docs.
Known issues
GraphQL
We are currently waiting on some issues with GraphQL to be fixed upstream in Workers so full support for GraphQL is not currently guaranteed when deployed.
Worker size limits
We currently recommend deploying this template to the Paid Workers plan due to bundle size limits of 3mb. We're actively trying to reduce our bundle footprint over time to better meet this metric.
This also applies to your own code, in the case of importing a lot of libraries you may find yourself limited by the bundle.
Questions
If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Payload Cloudflare Template
Deploy to Cloudflare
This can only be deployed on Paid Workers right now due to size limits. This template comes configured with the bare minimum to get started on anything you need.
Quick start
This template can be deployed directly to Cloudflare Workers by clicking the button to take you to the setup screen.
From there you can connect your code to a git provider such Github or Gitlab, name your Workers, D1 Database and R2 Bucket as well as attach any additional environment variables or services you need.
Quick Start - local setup
To spin up this template locally, follow these steps:
Clone
After you click the Deploy button above, you'll want to have standalone copy of this repo on your machine. Cloudflare will connect your app to a git provider such as Github and you can access your code from there.
Local Development
How it works
Out of the box, using Wrangler will automatically create local bindings for you to connect to the remote services and it can even create a local mock of the services you're using with Cloudflare.
We've pre-configured Payload for you with the following:
Collections
See the Collections docs for details on how to extend this functionality.
  • Users (Authentication)
    Users are auth-enabled collections that have access to the admin panel.
    For additional help, see the official Auth Example or the Authentication docs.
  • Media
    This is the uploads enabled collection.
Image Storage (R2)
Images will be served from an R2 bucket which you can then further configure to use a CDN to serve for your frontend directly.
D1 Database
The Worker will have direct access to a D1 SQLite database which Wrangler can connect locally to, just note that you won't have a connection string as you would typically with other providers.
You can enable read replicas by adding readReplicas: 'first-primary' in the DB adapter and then enabling it on your D1 Cloudflare dashboard. Read more about this feature on our docs.
Working with Cloudflare
Firstly, after installing dependencies locally you need to authenticate with Wrangler by running:
pnpm wrangler login
This will take you to Cloudflare to login and then you can use the Wrangler CLI locally for anything, use pnpm wrangler help to see all available options.
Wrangler is pretty smart so it will automatically bind your services for local development just by running pnpm dev.
Deployments
When you're ready to deploy, first make sure you have created your migrations:
pnpm payload migrate:create
Then run the following command:
pnpm run deploy
This will spin up Wrangler in production mode, run any created migrations, build the app and then deploy the bundle up to Cloudflare.
That's it! You can if you wish move these steps into your CI pipeline as well.
Enabling logs
By default logs are not enabled for your API, we've made this decision because it does run against your quota so we've left it opt-in. But you can easily enable logs in one click in the Cloudflare panel, see docs.
Known issues
GraphQL
We are currently waiting on some issues with GraphQL to be fixed upstream in Workers so full support for GraphQL is not currently guaranteed when deployed.
Worker size limits
We currently recommend deploying this template to the Paid Workers plan due to bundle size limits of 3mb. We're actively trying to reduce our bundle footprint over time to better meet this metric.
This also applies to your own code, in the case of importing a lot of libraries you may find yourself limited by the bundle.
Questions
If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
BranchesTags
Repository files navigation
Payload Cloudflare Template
Deploy to Cloudflare
This can only be deployed on Paid Workers right now due to size limits. This template comes configured with the bare minimum to get started on anything you need.
Quick start
This template can be deployed directly to Cloudflare Workers by clicking the button to take you to the setup screen.
From there you can connect your code to a git provider such Github or Gitlab, name your Workers, D1 Database and R2 Bucket as well as attach any additional environment variables or services you need.
Quick Start - local setup
To spin up this template locally, follow these steps:
Clone
After you click the Deploy button above, you'll want to have standalone copy of this repo on your machine. Cloudflare will connect your app to a git provider such as Github and you can access your code from there.
Local Development
How it works
Out of the box, using Wrangler will automatically create local bindings for you to connect to the remote services and it can even create a local mock of the services you're using with Cloudflare.
We've pre-configured Payload for you with the following:
Collections
See the Collections docs for details on how to extend this functionality.
  • Users (Authentication)
    Users are auth-enabled collections that have access to the admin panel.
    For additional help, see the official Auth Example or the Authentication docs.
  • Media
    This is the uploads enabled collection.
Image Storage (R2)
Images will be served from an R2 bucket which you can then further configure to use a CDN to serve for your frontend directly.
D1 Database
The Worker will have direct access to a D1 SQLite database which Wrangler can connect locally to, just note that you won't have a connection string as you would typically with other providers.
You can enable read replicas by adding readReplicas: 'first-primary' in the DB adapter and then enabling it on your D1 Cloudflare dashboard. Read more about this feature on our docs.
Working with Cloudflare
Firstly, after installing dependencies locally you need to authenticate with Wrangler by running:
pnpm wrangler login
This will take you to Cloudflare to login and then you can use the Wrangler CLI locally for anything, use pnpm wrangler help to see all available options.
Wrangler is pretty smart so it will automatically bind your services for local development just by running pnpm dev.
Deployments
When you're ready to deploy, first make sure you have created your migrations:
pnpm payload migrate:create
Then run the following command:
pnpm run deploy
This will spin up Wrangler in production mode, run any created migrations, build the app and then deploy the bundle up to Cloudflare.
That's it! You can if you wish move these steps into your CI pipeline as well.
Enabling logs
By default logs are not enabled for your API, we've made this decision because it does run against your quota so we've left it opt-in. But you can easily enable logs in one click in the Cloudflare panel, see docs.
Known issues
GraphQL
We are currently waiting on some issues with GraphQL to be fixed upstream in Workers so full support for GraphQL is not currently guaranteed when deployed.
Worker size limits
We currently recommend deploying this template to the Paid Workers plan due to bundle size limits of 3mb. We're actively trying to reduce our bundle footprint over time to better meet this metric.
This also applies to your own code, in the case of importing a lot of libraries you may find yourself limited by the bundle.
Questions
If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.
About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages