Set up your website (with CI)
If you use a static site generator like Jekyll, Hugo, or any other similar tool, you can integrate deployment into the Forgejo Actions workflow which builds your site.
To learn how to do this, see our documentation.
Set up your website (without CI)
If you just want to serve plain old hand-made static files, you can also configure a webhook on your repository to deploy changes to Incremental Social Pages.
1Set up your repository
Create a public repository named pages with a branch
called pages to make the site available at the main subdomain.
or
Create a branch pages in a public repository:git switch --orphan pagesgit rm --cached -r .
2Set up deployment
In the Settings for your repository, go to Webhooks and click Add webhook.
Select Forgejo from the drop down list of webhook types.
Set the Target URL to the URL of your website. If you don’t have a custom
domain, that’s
https://, replacing USERNAME with your user or organization name
and REPOSITORY with the name of your repository. (If your
repository is called pages, omit it.) If you have a custom
domain, remember to
configure it with the instructions below.
Set the Branch filter to pages.
Click Add webhook.
3Upload your files and you’re done!
Push your static content, HTML, style, fonts, images or anything else. They will be
accessible at https://.
Custom domain configuration
Add a DNS record on your domain:CNAME pages.incremental.social.
Or for apex domains where CNAME doesn't work:ALIAS pages.incremental.social.
If ALIAS isn't supported, use add the TXT record as described
above, and use A+AAAA as following:
A 217.197.84.141AAAA 2a0a:4580:103f:c0de::2
Then, add a TXT record authorizing the Incremental Social Pages server to deploy your
repository to the server. Add the record to the subdomain _git-pages-repository with the Git HTTPS clone URL of your repository:
TXT https://code.incremental.social/