Getting started

From an empty account to a deployed app, and what to do with it afterwards.

Sign up

Sign up at Sign up with an email address and password, or with Continue with Google or Continue with GitHub. A password needs at least 16 characters (at most 256); there are no other rules, so a long phrase works well.

With an email address and password, open the verification link Eurobase emails you within 24 hours; Resend email sends a new one. Until then the dashboard stays locked. An email address Google or GitHub has already verified needs no link.

Forgot your password? Select Forgot password? on Log in. Eurobase emails a link that works once for 30 minutes; choosing a new password signs the account out everywhere.

Connect GitHub

Open GitHub in the sidebar and select Connect GitHub: you sign in to GitHub, then install the Eurobase GitHub App. Signing up with GitHub doesn't connect it; you still do this step. On GitHub, give the app access to all repositories or only the ones you select; private repositories work. Manage repositories changes that list later. If you create a project before connecting GitHub, Eurobase takes you here first.

Create a project

  1. In Projects, select New project and enter a Project name: 8 to 24 ASCII letters, digits and single hyphens, starting and ending with a letter or digit. Reserved names are refused, and so is a name still held by a project that is being deleted. The name becomes your address, <name>.eurobase.dev. If another project already uses that address, Eurobase adds words to it, such as customer-api-alpine.eurobase.dev.
  2. Under Configure your first deployment, choose the Repository. The Branch is the repository's default branch. In a repository with several apps, choose the Root directory of the one to deploy.
  3. Check what Eurobase detected and the settings it prefilled. What you can set depends on the runtime; see Workers and Containers and static sites. An app that runs a server can get its first secrets under Startup secrets.
  4. Select Save and Deploy.

What happens on push

  • Every push to the project's branch starts a deployment of that commit. Pushes to other branches are ignored: there are no preview deployments, and Eurobase doesn't post commit statuses to GitHub.
  • A deployment moves through states such as Queued, Building, Deploying and Healthy, or Failed with the reason. Pushes that arrive while another deployment runs are each deployed after it.
  • The new deployment serves your address only after it passes its check. If it fails, the previous deployment keeps serving.
  • Deployments count toward your plan's daily limit. A push over the limit isn't deployed; push again or deploy from the dashboard after the limit resets. See Plans and limits.

Redeploy and roll back

Open a deployment from Deployment history on the project's deployments page. Owners and admins can:

  • Redeploy: build the same commit again. It counts toward the daily limit.
  • Rollback: serve an earlier successful deployment again, without rebuilding. Only recent successful deployments can be rolled back to, and a rollback doesn't count toward the daily limit.
  • Deploy Existing Release (Workers), Deploy Existing Artifact (static sites) or Deploy Existing Image (containers): deploy an earlier build again without rebuilding. It counts toward the daily limit.

Only one deployment per project runs at a time.

Secrets

Open Secrets in the project sidebar, enter a Secret name and Secret value, choose the resources that receive it (your app, functions or containers) and save. Every value is stored encrypted; there are no plain variables. A resource can have up to 64 secrets.

  • Today secrets reach your code when it runs, not during the build.
  • A live Worker is redeployed automatically when you save a secret.
  • Other apps show Redeploy required; the change applies with the next deployment.
  • Containers ask Restart containers?: Restart now applies the change, and Not now leaves them Restart required.
  • HTTP functions receive the new value without a redeploy.

Logs

  • The project's Logs page shows deployment, HTTP request, container, function, storage and Worker logs. It keeps up to 30 days, and at most the newest 10,000 entries of each kind.
  • Each deployment has Build, Deploy, Runtime and Errors tabs.
  • A container app's own output (standard output and error) isn't shown yet.
  • On a Workers project, Requests and logs opens the Worker page with the last 24 hours; see Workers.

Delete a project

In the project's Settings, the project owner can select Delete project under Danger Zone, type the project's address name and select Confirm delete. This can't be undone, and it isn't possible while any deployment work is running. Eurobase then removes the project's deployments, running apps, storage buckets and files. Once that finishes, anyone can create a project with the same address; see Reused addresses.