Features
When you run servers yourself, what really eats up time is not the services themselves but the surrounding work, such as installation, connections, addresses, and accounts.
Here, one by one, is what tidoly PaaS takes care of for you.
No burden of installing open source
Even when there's open source you want to use, deploying it takes a lot of preparation. You have to bring up a database first, adjust configuration files, open an access address, and attach a certificate.
With tidoly, you just pick from the list and choose a size.
What it needs is prepared along with it, and when installation finishes you get an address you can open right away. Even if installation fails partway, fix the cause and press again: it skips what's already done and continues.
→ Chapter 4 · Install a bundle at once · Chapter 5 · Install one by one
Build and deploy are one
When deploying an app you built, all you provide is a Git address.
You don't need a separate build server or an image registry. If there is a Dockerfile, it is used as is; if not, one is created automatically based on the language and structure.
You can set it up so that pushing code automatically rebuilds and redeploys.
→ Chapter 6 · Deploy your own app
No credentials to manage
Just because an app uses a database doesn't mean you copy over its address or password. Choose only what to connect to, and the connection details are delivered to the app.
When connection details change, the app picks them up automatically.
And the app doesn't need to know where that database is. Whether it's installed on your server or in the cloud you already use, it attaches the same way, so even if you move it later, you don't change the app code.
→ Chapter 8 · Connect resources (binding)
Domains and certificates take care of themselves
Address issuance, HTTPS certificates, and renewal before expiry are all handled automatically.
When you deploy one more service, its address and certificate are prepared along with it. There's no need to request certificates per service or keep track of renewal dates.
→ Chapter 9 · Certificates and addresses
One account for login
The services you install all open with the same account.
The work of creating an admin account for each service, inviting teammates separately, and managing who can access what in each place goes away.
When people join or leave the team, you only make changes in one place.
→ Chapter 3 · Projects and status
No public IP or domain required
It works even in environments that can't be reached from outside, such as servers on an internal network or home internet lines.
Because the server connects outward, you don't open ports on your router. If you don't have a domain, we issue you an address, and it still opens over HTTPS.
→ Chapter 1 · License and domain
Never install the same thing twice
Things shared by multiple services are kept as a single copy and shared.
If you install them separately per project, multiple copies of the same thing run and just eat memory and disk. What already exists is quietly reused, so you don't need to worry about it when installing.
Databases work the same way. Instead of running one per app, they share one while each gets its own dedicated space.
→ Chapter 5 · Things you install only once
Metrics and logs come included
On an installed service's screen you see CPU, memory, traffic, and logs right away. There's no need to build monitoring separately and connect it to each service.
To dig deeper, use Grafana, which also opens right away without logging in.
So
Prepare your hardware → install tidoly → choose the services you need.
Things like where services are installed, what the database address is, and how certificates are obtained are hidden behind the scenes.
To get started → Chapter 0 · Prepare a server