SupportConsole
llms.txtSign in

Sites

Create sites, point domains, set environment variables and run workers.

Guides

Create a site on your serverPick a site type, a server and a domain, connect a repository and press Create site. SrvYard builds the Linux user, PHP-FPM pool and Nginx configuration for you.Connect a repository and pick a branchPoint a site at a GitHub, GitLab or Bitbucket repository, or at any Git URL, choose the branch that gets deployed and know what changes on the next deployment.Add a domain, a free subdomain and DNS recordsMake a site answer on more than one hostname, choose how www behaves, create the DNS records that point the names at your server and fix a domain that stays on DNS pending.Edit environment variablesEdit a site's .env file in SrvYard, with masked values, a row editor and a text editor, and choose whether to rebuild the config cache, restart queue workers or deploy straight after saving.Run queue workers and the Laravel schedulerAdd a Supervisor-managed queue worker with the options you need, switch on the Laravel scheduler with one click, and keep both running across deployments.Run background processes for a siteKeep any long-running command alive with Supervisor: add a custom process, set its working directory and copies, start, stop and restart it, and read its log when it misbehaves.Add redirects and password protectionSend old URLs to new ones with Nginx redirect rules, import them from a CSV file, and put a username and password in front of a whole site or one path with HTTP Basic authentication.Read site logs and run commandsRead the Nginx, Laravel and PHP logs of a site from the dashboard, then run a one-off command such as artisan or composer as the site user, with a history and a safety prompt for risky commands.Use the Laravel panel for the scheduler, queues, Octane and maintenance modeSwitch on the scheduler, Horizon, Octane, Reverb and Inertia SSR from the site overview, and put a Laravel site into maintenance mode with an optional bypass secret.Adopt a site that is already on your serverScan a server you already run, register its sites in SrvYard without moving or restarting anything, then take things over one at a time. A restore point and a roll back are kept.Delete, rename or move a siteRename a site's label, delete a site and everything SrvYard created for it, and move a site to another server by building it there and switching DNS, with no downtime if you do it in the right order.

Frequently asked

Can I add a repository to a site later?

Not if the site was created without one. The create form warns that this cannot be changed afterwards, so decide before you press Create site. The workaround is a new site with a repository and a domain move. See Create a site on your server.

Do I have to set up DNS for a site?

For your own domain, yes. SrvYard writes the name into Nginx, but you create the DNS record at your registrar or DNS host; the Domains tab shows Points here once it resolves. A site can have up to 25 domains. See Add a domain, a free subdomain and DNS records.

Who can see and edit a site's .env file?

Owners and admins, or a custom role with the environment permission. Everyone else sees a Restricted notice. SrvYard keeps an encrypted copy and writes it to the server for you. See Edit environment variables.

I saved an environment variable, but the app still uses the old value. Why?

The configuration is probably cached, or a queue worker is running with the old environment. Save again with Run php artisan config:cache and Restart queue workers ticked. See Edit environment variables.

How do I keep a queue worker and the scheduler running?

Add the worker on the site's Processes tab, where Supervisor keeps it alive, and switch the scheduler on from the Laravel card. Deploy the site once first, and set QUEUE_CONNECTION to something other than sync. See Run queue workers and the Laravel scheduler.

Can I move a site to another server?

There is no one-click move. You build the site on the new server, check it, then switch DNS, which avoids downtime if you follow the order in the article. Remember to switch off queue workers and the scheduler on the old one. See Delete, rename or move a site.

What does deleting a site remove?

Its files, Nginx configuration and the other things SrvYard created for it. Its databases are not removed; delete them from the server's Databases tab if you want them gone. Take a backup first. See Delete, rename or move a site.

Can I manage a site that was not created in SrvYard?

Yes. A read-only scan finds the sites on a connected server and registers them where they are, without moving or restarting anything. You then take over one capability at a time, and every step can be rolled back. See Adopt a site that is already on your server.