Parts
Web, api, worker, database and cache. Each part comes with the folder it came from, how it will be built and how sure Kule is about it.
webapiworkerdbcache
Feature · Deploy plan
It shows the plan first, then sets it up.
The parts it found, the connections between them and the few values it needs from you, on one page. When you choose Kur ve yayınla (Set up and deploy), it sets everything up on Dokploy step by step, and you watch each step live.
What is in the plan
Parts, connections, variables.
The plan shows what it will set up and why. If something looks wrong, you change it before deploying.
Connections
Kule fills in the database and cache addresses and the api's domain. Session secrets are generated, strong and random.
DATABASE_URLREDIS_URLinternal network
What it asks you for
Only the keys for outside services. You type them in, or fill them from a .env file on your computer.
.envSTRIPE_SECRET_KEYRESEND_API_KEY
Set up and deploy
Step by step, from where it left off.
Each step is saved as soon as it finishes. If a deploy stops halfway, it picks up where it left off, and if you want, it removes everything it created.
projecta project is created on Dokploy
resourcesPostgreSQL, Redison the internal network
codeGitHub deploy key or a folder on this Macthe deploy key is read-only
appsweb, api, worker
addressesgetaktar.com, api.getaktar.complus the DNS record if Cloudflare is connectedSSL
environmentconnections and your values
buildlog lines stream live
healthdo the addresses respondlive
Where it comes from
Three sources, the same plan.
Wherever your code lives, the plan comes out the same way. Web and api parts you don't give a domain open on a free address.
GitHub
This Mac
Addresses
We'll let you know when Kule is out.
People on the list get the first version before anyone else.
You're on the list. You'll be the first to hear when Kule is out.