Symfony hosting · Vallic Cloud
Symfony hosting · Vallic Cloud
Symfony and PHP hosting, with migrations and Messenger handled.
Symfony, or any other PHP application, on machines no other customer shares and deployed from Git: Doctrine migrations once the release is live, Messenger consumers kept running, and Valkey for sessions.
On Vallic Cloud
What runs your PHP site
You choose
Runtime
You can add
Database
Cache
Reverse proxy
Search
Time series
Background work
The default, unless vallic.yaml names another version.
Done for you
Kept between releases
private, so a deploy never loses what the site wrote.
Why here
Plain PHP, with what Symfony needs around it.
Migrations after the release is live
Doctrine’s migrations run on the machine as a deploy step, then the cache. With on_failure: rollback, a deploy that fails puts the previous release back.
DATABASE_URL, as Doctrine reads it
Every container gets one connection string, assembled from the environment’s credentials. There is no glue to write.
Messenger as a worker
messenger:consume runs as a worker the platform keeps alive. With --time-limit set it restarts cleanly, without leaking memory.
Writable where it should be
The release is read-only. The cache and logs go to VALLIC_PRIVATE_DIR, which outlives every release, and uploads to a directory you declare as a mount.
Sessions in Valkey
Past one web server, Symfony’s sessions can live in Valkey, so a visitor stays logged in whichever machine answers.
Support from people who build applications
Our team builds and runs PHP applications for a living, and a ticket reaches them.
Moving a Symfony application here.
Add a vallic.yaml, pin APP_ENV=prod in the committed .env, point the cache and log directories at the private directory as the handbook shows, import the database with vallic db import, and deploy.
Rather we did it? Our team moves applications as part of what it does.
Questions
Is there a Symfony project type?
No. Symfony runs as a PHP project, on the same plain PHP image as any other PHP application, served from public/.
Does it run Symfony’s scheduler?
Not for you. Run the Scheduler transport as a worker, or declare a cron job for anything else.
Do you charge per request or per visit?
No. Machines are billed by the month, and traffic past what a machine includes by the terabyte.
Where can it run?
In any of the platform’s datacentres. The configurator shows each one’s machines and prices before you sign up.
