Token

Netlify uses a personal access token: in Netlify, open User settings › Applications › Personal access tokens (the Create a token link of the form opens this page), and create a new token.

The account is shown with the email of your Netlify user.

Target settings

If no site of your account has this name, a new site is created with it at the first publication, at https://<name>.netlify.app/. The name must be unique across all of Netlify: if it is already taken, choose another one.

Publication

Netlify tells which files it doesn't have yet: only those are sent. Cecil Desktop then waits for Netlify to process the deployment (up to 5 minutes), and shows the URL of the deployment.

Token

In Vercel, open Account settings › Tokens (the Create a token link of the form opens this page), and create a token with access to the team of the project.

The account is shown with the email of your Vercel user.

Target settings

When you save the target, only the access to the account (or to the team) is checked: the project is created at the first publication if it doesn't exist.

Publication

The site is deployed to production, as a static site: Vercel doesn't run any build or install command, the files built by Cecil are published as they are. Only the files Vercel doesn't have yet are sent, then Cecil Desktop waits for the deployment (up to 5 minutes) and shows the URL of the project.

Token

GitHub Pages uses a fine-grained token: in GitHub, open Settings › Developer settings › Personal access tokens › Fine-grained tokens (the Create a token link of the form opens this page), then:

1. under Repository access, choose Only select repositories and pick the repository of the site;
2. under Permissions, give Read and write access to Contents and Pages.

The account is shown with your GitHub login.

Target settings

When you save the target, Cecil Desktop checks that the token can write to the repository.

Publication

Each publication replaces the content of the branch with the built site, in a single commit (Publish with Cecil Desktop):

• the branch is created if it doesn't exist;
• a .nojekyll file is added, so that GitHub doesn't process the site with Jekyll;
• a CNAME file is added if you set a custom domain;
• GitHub Pages is enabled on the branch if needed, or switched to it if it published another branch.

Only the files GitHub doesn't have yet are sent, and the files removed from the site are removed from the branch. If nothing has changed, no commit is made.

Keys

AWS uses the keys (Access key ID and Secret access key) of an IAM user. Create a user dedicated to the publication, with these permissions on the bucket:

• s3:ListBucket
• s3:PutObject
• s3:DeleteObject
• cloudfront:CreateInvalidation, if you use CloudFront

A user limited to its bucket, that can't list the other buckets, is accepted. The account is shown as AWS (ABCD…WXYZ), with the beginning and the end of the access key.

Target settings

Publication

The files are compared with the objects of the bucket (under the prefix):

• only the new and changed files are sent, with their content type;
• the objects that are no longer in the site are deleted;
• HTML pages are sent with cache headers that make browsers check for a new version, the other files are cached for 1 day;
• if a CloudFront distribution is set and something has changed, its cache is invalidated.

After the publication, the target shows the Site URL, or the URL of the index.html file in the bucket.