Quick start
Deploy your first app on Lahyer from a Git repository, a folder or the terminal.
You need an app in a repository on GitHub, GitLab or Bitbucket. No repository yet? Upload a folder or deploy from the terminal instead.
Deploy from a repository
Create an account
Sign up at app.lahyer.com. Every account starts on the Free plan: no card needed, and it is not a time-limited trial.
Connect your Git provider
In the dashboard, choose New project, then connect where your code lives:
- GitHub: install the Lahyer app on your user or organization, for all repositories or only the ones you pick.
- GitLab: authorize Lahyer on gitlab.com for the projects you maintain.
- Bitbucket: authorize Lahyer on bitbucket.org for the repositories you administer.
Import the repository
Pick the repository. Lahyer reads it and fills in the build settings: the framework, the install and build commands and the output directory. Check them, and set the Root directory if the app lives in a subfolder (for example apps/web in a monorepo).
The Slug becomes your address: a project with the slug shop is served at shop.lahyer.app. Choose Create project.
Deploy
On the project page, choose Deploy now. The build log streams as it runs, and most apps are live in about a minute. When the deployment is ready, open the address shown on the project.
After the first deployment
- Every push deploys. A push to the production branch builds a new deployment and, once it is ready, moves your live address to it. A failed build never replaces the version that is live.
- Every pull request gets a preview. Lahyer builds the branch and serves it at
<project>-git-<branch>.lahyer.app(merge requests on GitLab work the same way). The preview closes when the pull request does. - Settings and secrets. Add environment variables on the project's Environment variables tab; they are encrypted and never shown in logs. Connect your own domain from the Domains tab.
Upload a folder
No repository needed: on New project, under Upload a folder, choose the project folder or a .zip of it. Lahyer detects the framework the same way and builds it. When you pick a folder, dependency folders such as node_modules are left out of the upload.
Deploy from the terminal
The Lahyer CLI deploys a repository you have already imported, or uploads a folder as a new project.
npm install -g @lahyer/cli
lahyer login # paste an API key from Settings, API keys
lahyer deploy --dir . # upload this folder; the first run creates the projectInside a clone of an imported repository, lahyer init links the directory to its project (matched by the Git remote), and lahyer deploy deploys the checked-out branch and follows the build. lahyer deploy exits with an error unless the deployment ends ready, so it fits in CI: set LAHYER_TOKEN there instead of running lahyer login.