tahoe-lafs/web-landing-page
4
1
Fork 1
Code Issues 6 Pull requests 3 Actions Activity
Landing page for Tahoe-LAFS project: https://home.of.tahoe-lafs.org/
49 commits 15 branches 0 tags 4.6 MiB
HTML 44%
SCSS 27.3%
Dockerfile 15.6%
Ruby 13.1%
Find a file
Benoit Donneaux a353d9963c
Some checks failed
Jekyll / jekyll (pull_request) Failing after 39s
Details
Debug forge object to filter events 
Signed-off-by: Benoit Donneaux <benoit@leastauthority.com>
2025-08-19 10:51:04 +02:00
.forgejo Debug forge object to filter events 2025-08-19 10:51:04 +02:00
docker/jekyll Enable livereload and adapt the doc accordingly 2025-05-02 09:55:17 +02:00
src Remove post about older release of tahoe-lafs 2025-08-13 20:29:32 +02:00
.gitignore Prepare Jekyll requirements 2024-04-24 00:33:08 +02:00
_config.yml Disable share links from post pages 2024-11-19 17:52:18 +01:00
docker-compose.yml Enable livereload and adapt the doc accordingly 2025-05-02 09:55:17 +02:00
Gemfile Prepare Jekyll requirements 2024-04-24 00:33:08 +02:00
Gemfile.lock Prepare Jekyll requirements 2024-04-24 00:33:08 +02:00
LICENSE Initial landing page based on the existing Wiki home page 2024-05-14 19:02:06 +02:00
README.md Support checks in forked repositories 2025-08-19 10:35:28 +02:00

README.md

Web landing page for the Tahoe-LAFS project

The goal of this web page is to represent the Tahoe-LAFS project to the public.

It gives guidance on getting started for end-users, developers building with Tahoe-LAFS and hackers interested working on Tahoe-LAFS itself alike.

Building

This web page is built and deployed by CI. A preview is also automaticaly genereated for PRs made from branches local to this repository (require push/write permission).

If you want to pre-view your changes on your local machine before pushing commits, you might want to start a development server.

Issuing this command on a system with Docker runs a web server on http://localhost:4000/ that re-builds and refresh the page automatically on source file change:

docker-compose up

Contributing

We welcome contributions! Easiest is to open tickets or pull requests directly. If unsure, join the IRC or ask on the Tahoe-LAFS developer mailing list.

Caveat: because they need access to the repository secrets (e.g. SSH private key), the deployment step will be skipped on forked repositories. Which means preview sites will only be published from local branches pushed by collaborators with permissions to write in this repository.