Getting started
What you choose when you create a project, and in what order.
Vallic Cloud docs
What the platform does, and why it does it that way. Written by the people who wrote the code.
Explore
What you choose when you create a project, and in what order.
Teams, projects, environments, variables, backups, billing and support — what each button will and will not do.
vallic.yaml, the software stacks, the settings each service takes, and changing a version.
Connecting a repository and deploying on push, your own domains, the edge in front of every environment, and the CDN.
Machine types and resizing, autoscale, buying more room, and giving a service or your own containers a machine of their own.
Logs, metrics, availability and notifications — what your application is doing, and who hears about it.
The command line, shell access, the API the console and CI call, and asking an assistant.
Drupal, WordPress, Laravel, Symfony, Django, Rails, Python and Node — what each needs to run here.
Runtimes, web servers, databases, caches, search, queues and mail, with the versions on offer.
How it fits together
version: 1
type: drupal
runtime:
php: '8.4'
memory_limit: 512M
services:
- mariadb: '11.8'
- valkey: '8'
deploy:
steps:
- 'drush deploy'
on_failure: rollback
health:
path: /health
Apps and services
Open a ticket from Support in the console. We answer on the ticket.