Project Development URLs
This is a visual layout of the Dashboard
nothing special but useful in seeing the app and has an interactive file structure at the bottom
Privacy Policy
generic needs updated. i just made this since the dashboard has a login page.
Its here if anyone wants to update it or make changes
Project Icons
this set is unique and not copied from anyone. i just made them when creating the app.
here they are in documentation style. they are easy to swap out and not tied to the domain officially
in the dashboard project all of the icons in /PUBLIC making them avaliable via url like so.
and the complete set /docs is here. again easy to swap out i just made something to deploy the app with so the icon/logo would display properly across all devices.
since they are all hosted on github you can easily include them now in any future docs
<link rel="apple-touch-icon" href="https://callaback.github.io/logo/apple-touch-icon.png">
or even render them in a document
Lives on github Here :
any changes here aka “commits” will trigger a deployment its very small but if you look in the bottom right of the page you will see “build version XXXXX” thats the github commit or “version” of the page your looking at. useful for fixing things when they break.
need to impliment something or make a change? edit the file on github and commit the change.
changes to the git trigger an automatic deployment
This is where SUPABASE is connected to manage AUTH and API Calls
NEXT_PUBLIC_SUPABASE_URL=https://zofiafinpuqldixvpiwh.supabase.co
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_DEFAULT_KEY=sb_publishable_6wrrV8o2liTPYuJavzgNqw_Wf2L
project files on git →SUPABSE DB (vercel) → cloudflare authoritive DNS
domain query via dig
callaback.com
vercel.com
Multiple IPs better redundancy Conclusion
direct-IP apex routing
Controlled ingress setups
all controled with a single DNS record.
TXT
no proxy
TTL 10 mins
Labeled on CF
*** DO NOT DELETE ***
Long story short nothing is set in stone. if its dashboard related the entire app sits on github.
the rest of the domain...
it its its cloudflare pages if its its cloudflare workers wrangler is the command line tool for both.
ways to deploy projects on the domain
wrangler command line: “wrangler pages deploy”
from github via the dashboard (this is the most popular as you just import the github url)
by direct file upload also the dashboard
/ PROJECT FOLDER
EXAMPLE #1
You have a project or collection you wish to deploy.
upload it via cloudflare dash board
then if you wanted it to be
you could create a single CNAME record Only CNAME records point to other domains all the others IPs
EXAMPLE #2
You have a project or collection you wish to deploy.
project is on github
if you wanted it to be
you could create a single CNAME record to and never have to upload anything create 1 record from the cloudflare dash to create the subdomain.
Only CNAME records point to other domains all the others IPs
EXAMPLE #3
you wish to deploy to the END of example callaback.com/privacypolicy
then you would create privacypolicy.html
and drop it in the /PUBLIC folder in the app on githhub.
Final note as a reminder because everyone has a different background
one this side will always be a cname record via cloudflare dashboard
photos.callaback.com
on this side will be the /PUBLIC folder in the dashboard app
callaback.com/photos
****if your making changes to the dashboard it has to be compliant with npm run build or bun or pnpm
as each change the app is re compiled at runtime with JS.
everything can be rolled back so go ahead get out there and break stuff...
if its dashboard the files are all .tsx
pages need index.html at root minimum
and workers are index.js
okay im drifiting off topic.....