├── dashboard.png ├── captive-portal.png ├── docs ├── nvme-step0.png ├── nvme-step1.png ├── nvme-step10.png ├── nvme-step2.png ├── nvme-step3.png ├── nvme-step4.png ├── nvme-step5.png ├── nvme-step6.png ├── nvme-step7.png ├── nvme-step8.png ├── nvme-step9.png ├── rpi-imager-1.png ├── rpi-imager-2.png ├── rpi-imager-3.png ├── Boot from NVMe.md ├── tuto-builder.py └── Kiwix Hotspot Tutorial.md ├── offspot-diagram.png ├── .gitignore ├── README.md └── LICENSE /dashboard.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/dashboard.png -------------------------------------------------------------------------------- /captive-portal.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/captive-portal.png -------------------------------------------------------------------------------- /docs/nvme-step0.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step0.png -------------------------------------------------------------------------------- /docs/nvme-step1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step1.png -------------------------------------------------------------------------------- /docs/nvme-step10.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step10.png -------------------------------------------------------------------------------- /docs/nvme-step2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step2.png -------------------------------------------------------------------------------- /docs/nvme-step3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step3.png -------------------------------------------------------------------------------- /docs/nvme-step4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step4.png -------------------------------------------------------------------------------- /docs/nvme-step5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step5.png -------------------------------------------------------------------------------- /docs/nvme-step6.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step6.png -------------------------------------------------------------------------------- /docs/nvme-step7.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step7.png -------------------------------------------------------------------------------- /docs/nvme-step8.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step8.png -------------------------------------------------------------------------------- /docs/nvme-step9.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/nvme-step9.png -------------------------------------------------------------------------------- /offspot-diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/offspot-diagram.png -------------------------------------------------------------------------------- /docs/rpi-imager-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/rpi-imager-1.png -------------------------------------------------------------------------------- /docs/rpi-imager-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/rpi-imager-2.png -------------------------------------------------------------------------------- /docs/rpi-imager-3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/offspot/overview/HEAD/docs/rpi-imager-3.png -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Byte-compiled / optimized / DLL files 2 | __pycache__/ 3 | *.py[cod] 4 | *$py.class 5 | 6 | # C extensions 7 | *.so 8 | 9 | # Distribution / packaging 10 | .Python 11 | build/ 12 | develop-eggs/ 13 | dist/ 14 | downloads/ 15 | eggs/ 16 | .eggs/ 17 | lib/ 18 | lib64/ 19 | parts/ 20 | sdist/ 21 | var/ 22 | wheels/ 23 | share/python-wheels/ 24 | *.egg-info/ 25 | .installed.cfg 26 | *.egg 27 | MANIFEST 28 | 29 | # PyInstaller 30 | # Usually these files are written by a python script from a template 31 | # before PyInstaller builds the exe, so as to inject date/other infos into it. 32 | *.manifest 33 | *.spec 34 | 35 | # Installer logs 36 | pip-log.txt 37 | pip-delete-this-directory.txt 38 | 39 | # Unit test / coverage reports 40 | htmlcov/ 41 | .tox/ 42 | .nox/ 43 | .coverage 44 | .coverage.* 45 | .cache 46 | nosetests.xml 47 | coverage.xml 48 | *.cover 49 | *.py,cover 50 | .hypothesis/ 51 | .pytest_cache/ 52 | cover/ 53 | 54 | # Translations 55 | *.mo 56 | *.pot 57 | 58 | # Django stuff: 59 | *.log 60 | local_settings.py 61 | db.sqlite3 62 | db.sqlite3-journal 63 | 64 | # Flask stuff: 65 | instance/ 66 | .webassets-cache 67 | 68 | # Scrapy stuff: 69 | .scrapy 70 | 71 | # Sphinx documentation 72 | docs/_build/ 73 | 74 | # PyBuilder 75 | .pybuilder/ 76 | target/ 77 | 78 | # Jupyter Notebook 79 | .ipynb_checkpoints 80 | 81 | # IPython 82 | profile_default/ 83 | ipython_config.py 84 | 85 | # pyenv 86 | # For a library or package, you might want to ignore these files since the code is 87 | # intended to run in multiple environments; otherwise, check them in: 88 | # .python-version 89 | 90 | # pipenv 91 | # According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control. 92 | # However, in case of collaboration, if having platform-specific dependencies or dependencies 93 | # having no cross-platform support, pipenv may install dependencies that don't work, or not 94 | # install all needed dependencies. 95 | #Pipfile.lock 96 | 97 | # poetry 98 | # Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control. 99 | # This is especially recommended for binary packages to ensure reproducibility, and is more 100 | # commonly ignored for libraries. 101 | # https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control 102 | #poetry.lock 103 | 104 | # pdm 105 | # Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control. 106 | #pdm.lock 107 | # pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it 108 | # in version control. 109 | # https://pdm.fming.dev/#use-with-ide 110 | .pdm.toml 111 | 112 | # PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm 113 | __pypackages__/ 114 | 115 | # Celery stuff 116 | celerybeat-schedule 117 | celerybeat.pid 118 | 119 | # SageMath parsed files 120 | *.sage.py 121 | 122 | # Environments 123 | .env 124 | .venv 125 | env/ 126 | venv/ 127 | ENV/ 128 | env.bak/ 129 | venv.bak/ 130 | 131 | # Spyder project settings 132 | .spyderproject 133 | .spyproject 134 | 135 | # Rope project settings 136 | .ropeproject 137 | 138 | # mkdocs documentation 139 | /site 140 | 141 | # mypy 142 | .mypy_cache/ 143 | .dmypy.json 144 | dmypy.json 145 | 146 | # Pyre type checker 147 | .pyre/ 148 | 149 | # pytype static type analyzer 150 | .pytype/ 151 | 152 | # Cython debug symbols 153 | cython_debug/ 154 | 155 | # PyCharm 156 | # JetBrains specific template is maintained in a separate JetBrains.gitignore that can 157 | # be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore 158 | # and can be added to the global gitignore or merged into this file. For a more nuclear 159 | # option (not recommended) you can uncomment the following to ignore the entire idea folder. 160 | #.idea/ 161 | -------------------------------------------------------------------------------- /docs/Boot from NVMe.md: -------------------------------------------------------------------------------- 1 | # Boot from NVMe 2 | 3 | > [!NOTE] 4 | > Kiwix Hotspot supports booting from NVME so you can follow anyother guide online ; this is just a reference. 5 | 6 | By default, all RaspberryPi are configured to boot from SD-card. 7 | 8 | If you want to boot from an NVMe disk or even USB, you need to update the Pi's bootloader. 9 | 10 | > [!IMPORTANT] 11 | > Only Pi5 supports NVMe. 12 | > If you have a Pi4, you can boot off a USB stick in a similar manner though. 13 | 14 | You can do this on a running Pi with `sudo rpi-eeprom-config --edit`. We use `0xf146` for NVMe ➡️ USB ➡️ SD. 15 | 16 | As our use case is to change device bootloader's in batch, we'll describe the rpi-imager method instead. 17 | 18 | [Upstream documentation](https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#nvme-ssd-boot) 19 | 20 | # Flash your NVMe disk 21 | 22 | Flash your image onto the M.2 NVMe disk (via an NVME reader) using rpi-imager. This works the same as for SD-card. 23 | 24 | ## Enable PCI Express Gen.3 25 | 26 | > [!WARNING] 27 | > Only do this is your NVMe HAT supports it (Argon NEO 5 M.2 NVME does) 28 | > Pi5 is certified for Gen 2.0 speeds (5 GT/sec) but can be forced to Gen 3.0 (8.0 GT/s) 29 | > Argon40 [recommends](https://cdn.shopify.com/s/files/1/0556/1660/2177/files/FOR_WEB_INSTRUCTION_MANUAL_NEO_5_M.2_NVMe_20240909.pdf?v=1725870016) enabling it. 30 | 31 | 32 | To enable it, make sure the file `/boot/firmware/config.txt` on the **running system** (those are read at every boot) contains `dtparam=pciex1_gen=3` in the `[all]` section. 33 | 34 | **From the running device**: 35 | 36 | ```sh 37 | ❯ echo "dtparam=pciex1_gen=3" | sudo tee -a /boot/firmware/config.txt 38 | ``` 39 | 40 | It can be disabled the same way. 41 | 42 | > [!TIP] 43 | > You can do this right after imaging your NVMe disk 44 | 45 | 46 | 1. Physically detach the disk as rpi-imager would have unmounted it 47 | 2. Physically attach it again 48 | 3. Run the following command (assuming macOS host) 49 | 50 | 51 | ```sh 52 | ❯ echo "dtparam=pciex1_gen=3" | tee -a /Volumes/bootfs/config.txt 53 | ``` 54 | 55 | Make sure to eject the filesystems before unplugging. 56 | 57 | 58 | # Prepare a bootloader update SD-card 59 | 60 | You only need to do this once. Then you can keep that SD-card aside (or re-do the same process next time you need it). 61 | 62 | You can use the smallest SD-card you have as this takes very minimal space. 63 | 64 | ## Select “Choose OS” 65 | 66 | ![step0](nvme-step0.png) 67 | 68 | ## Find “Misc Utility images” 69 | 70 | ![step1](nvme-step1.png) 71 | 72 | ## Select “Bootloader” 73 | 74 | Choose the one appropriate for your Pi. In our use case, we want NVMe which is only compatible with Pi5. 75 | 76 | ![step2](nvme-step2.png) 77 | 78 | ## Select “NVMe/USB Boot” 79 | 80 | ![step3](nvme-step3.png) 81 | 82 | ## Select “Choose Storage” 83 | 84 | ![step4](nvme-step4.png) 85 | 86 | ## Select your SD-card in list 87 | 88 | Your SD-card (not your NVMe disk) should be attached obviously at this stage). 89 | 90 | ![step5](nvme-step5.png) 91 | 92 | ## Click on “Next” 93 | 94 | ![step6](nvme-step6.png) 95 | 96 | ## Select “YES” to confirm SD-card erasal 97 | ![step7](nvme-step7.png) 98 | 99 | ## Await completion 100 | 101 | Don't cancel verification ; it should all take only a couple minutes at most. 102 | 103 | ![step8](nvme-step8.png) 104 | ![step9](nvme-step9.png) 105 | 106 | ## Eject your SD-card 107 | 108 | Your SD-card is ready 109 | 110 | ![step10](nvme-step10.png) 111 | 112 | 113 | # Update bootloader 114 | 115 | Insert the SD-card into your Pi and **wait 15 seconds**. 116 | 117 | If successful, the **green LED** on the Raspberry Pi **will blink rapidly forever**. 118 | 119 | If the LED is blinking differently, there has been an error. 120 | 121 | If an HDMI display is attached, then the screen will display **green for success** or red if a failure occurs. -------------------------------------------------------------------------------- /docs/tuto-builder.py: -------------------------------------------------------------------------------- 1 | # where to write the resulting YAML file to 2 | YAML_CONFIG_PATH = "conf.yaml" 3 | 4 | # 5 | # SETTINGS 6 | # 7 | # 8 | NAME = "My Hotspot" 9 | # main domain to access your domain: xxx.hotspot. ASCII, numbers and dash 10 | DOMAIN = "my-kiwix" 11 | # SSID: max 32 chars. Forbidden chars: ^ ! # ; + \ / " \t 12 | SSID = "My SSID" 13 | # PASS: max 64 chars. No ASCII control characters. Leave empty for Open network 14 | PASSPHRASE = "" 15 | TIMEZONE = "UTC" 16 | ADMIN_USERNAME = "admin" 17 | ADMIN_PASSWORD = "admin-password" 18 | BRANDING_HORIZONTAL_LOGO_PATH = "" 19 | BRANDING_SQUARE_LOGO_PATH = "" 20 | 21 | # 22 | # CONTENT SELECTION 23 | # 24 | # Title IDs for your ZIM files 25 | ZIM_TITLES = [ 26 | "openZIM:wikipedia_en_climate_change:nopic", 27 | "openZIM:raspberrypi.stackexchange.com_en_all:all", 28 | ] 29 | # Package IDs from 30 | # https:/github.com/offspot/offspot-config/blob/main/src/offspot_config/catalog.json 31 | PACKAGES = [ 32 | "file-manager.offspot.kiwix.org", 33 | ] 34 | # URL to a ZIP file which content will be served in the files-resources app 35 | FILES_APP_ZIP_URL = "" 36 | 37 | # 38 | # OPTIONS 39 | # 40 | # available at metrics.<> and show usage metrics over time. 41 | # useless (and wrong) if you dont have an hardware clock and Pi is offline 42 | ADD_METRICS = True 43 | # available at clock.<> allows you to set time/date of Pi. 44 | # mostly useful if you have an hardware clock and you're offline 45 | ADD_HWCLOCK_MGMT = True 46 | # includes Kiwix readers to the dashboard for downloads 47 | ADD_READERS = True 48 | 49 | ### End of basic configuration 50 | # top-level domain to use for your hotspot's domains (my-kiwix.hotspot) 51 | TLD = "hotspot" 52 | # base image to use. update if theres a newer version available 53 | BASE_IMAGE_URL = "1.2.1" 54 | # the actual rootfs size inside the base image. there's a script to find the value 55 | BASE_IMAGE_ROOTFS_SIZE = 2663383040 56 | KIWIX_ZIM_MIRROR_URL = "https://mirror.download.kiwix.org/zim/" 57 | KIWIX_LIBRARY_URL = "https://library.kiwix.org" 58 | 59 | import datetime 60 | import re 61 | from pathlib import Path 62 | 63 | import requests 64 | import xmltodict 65 | from offspot_config.builder import ( 66 | BRANDING_PATH, 67 | AppPackage, 68 | ConfigBuilder, 69 | FilesPackage, 70 | ) 71 | from offspot_config.catalog import app_catalog 72 | from offspot_config.inputs.base import BaseConfig 73 | from offspot_config.utils.dashboard import Link, Reader 74 | from offspot_config.utils.download import get_online_rsc_size 75 | from offspot_config.utils.misc import b64_encode 76 | from offspot_config.zim import ZimPackage 77 | 78 | 79 | def get_zim_package(ident): 80 | publisher, name, flavour = ident.split(":", 2) 81 | resp = requests.get( 82 | f"{KIWIX_LIBRARY_URL}/catalog/v2/entries", 83 | params={"name": name}, 84 | timeout=30, 85 | ) 86 | resp.raise_for_status() 87 | catalog = xmltodict.parse(resp.content) 88 | 89 | if "feed" not in catalog: 90 | raise ValueError("Malformed OPDS response") 91 | if not int(catalog["feed"]["totalResults"]): 92 | raise OSError("Catalog has no entry; probably misbehaving") 93 | 94 | entries = catalog["feed"]["entry"] 95 | if not isinstance(entries, list): 96 | entries = [entries] 97 | 98 | for entry in entries: 99 | if not entry.get("name"): 100 | continue 101 | 102 | links = {link["@type"]: link for link in entry["link"]} 103 | version = datetime.datetime.fromisoformat( 104 | re.sub(r"[A-Z]$", "", entry["updated"]) 105 | ).strftime("%Y-%m-%d") 106 | flavour_ = entry.get("flavour") or "" 107 | publisher_ = entry.get("publisher", {}).get("name") or "" 108 | name_ = entry["name"] 109 | 110 | if name == name_ and publisher == publisher_ and flavour == flavour_: 111 | if icon_path := links.get("image/png;width=48;height=48;scale=1", {}).get( 112 | "@href", "" 113 | ): 114 | icon_url = f"{KIWIX_LIBRARY_URL}{icon_path}" 115 | else: 116 | icon_url = None 117 | 118 | return ZimPackage( 119 | ident=ident, 120 | kind="zim", 121 | domain="kiwix", 122 | title=entry["title"], 123 | description=entry["summary"], 124 | tags=list(set(entry["tags"].split(";"))), 125 | languages=list(set(entry["language"].split(","))) or ["eng"], 126 | icon_url=icon_url, 127 | name=name, 128 | flavour=flavour, 129 | version=version, 130 | download_url=re.sub( 131 | r".meta4$", "", links["application/x-zim"]["@href"] 132 | ), 133 | download_size=int(links["application/x-zim"]["@length"]), 134 | ) 135 | raise ValueError(f"Unable to find Catalog entry for {ident}") 136 | 137 | 138 | def get_builder(): 139 | builder = ConfigBuilder( 140 | base=BaseConfig( 141 | source=BASE_IMAGE_URL, 142 | rootfs_size=BASE_IMAGE_ROOTFS_SIZE, 143 | ), 144 | name=NAME, 145 | domain=DOMAIN, 146 | welcome_domain="goto.kiwix", 147 | tld=TLD, 148 | ssid=SSID, 149 | passphrase=PASSPHRASE or None, 150 | timezone=TIMEZONE, 151 | environ={ 152 | "ADMIN_USERNAME": ADMIN_USERNAME, 153 | "ADMIN_PASSWORD": ADMIN_PASSWORD, 154 | }, 155 | write_config=True, 156 | kiwix_zim_mirror=KIWIX_ZIM_MIRROR_URL, 157 | ) 158 | 159 | # add branding 160 | if BRANDING_HORIZONTAL_LOGO_PATH: 161 | print(f"> Adding branding file from {BRANDING_HORIZONTAL_LOGO_PATH}") 162 | logo = Path(BRANDING_HORIZONTAL_LOGO_PATH) 163 | builder.add_file( 164 | url_or_content=b64_encode(logo.read_bytes()), 165 | to=str(BRANDING_PATH.joinpath("horizontal-logo-light.png")), 166 | via="base64", 167 | size=logo.stat().st_size, 168 | is_url=False, 169 | ) 170 | del logo 171 | 172 | if BRANDING_SQUARE_LOGO_PATH: 173 | print(f"> Adding branding file from {BRANDING_SQUARE_LOGO_PATH}") 174 | logo = Path(BRANDING_SQUARE_LOGO_PATH) 175 | builder.add_file( 176 | url_or_content=b64_encode(logo.read_bytes()), 177 | to=str(BRANDING_PATH.joinpath("square-logo-light.png")), 178 | via="base64", 179 | size=logo.stat().st_size, 180 | is_url=False, 181 | ) 182 | del logo 183 | 184 | # dashboard links 185 | links = [] 186 | if ADD_METRICS: 187 | links.append(Link("Metrics", "//metrics.${FQDN}")) 188 | 189 | readers = None 190 | if ADD_READERS: 191 | print("> Adding Readers") 192 | readers = [ 193 | Reader( 194 | platform="windows", 195 | download_url="https://mirror.download.kiwix.org/release/kiwix-desktop/kiwix-desktop_windows_x64_2.4.1.zip", 196 | filename="kiwix-desktop_windows_x64_2.4.1.zip", 197 | size=132065749, 198 | ), 199 | Reader( 200 | platform="android", 201 | download_url="https://mirror.download.kiwix.org/release/kiwix-android/kiwix-3.12.0.apk", 202 | filename="kiwix-3.12.0.apk", 203 | size=105761084, 204 | ), 205 | Reader( 206 | platform="macos", 207 | download_url="https://mirror.download.kiwix.org/release/kiwix-macos/kiwix-macos_3.7.1.dmg", 208 | filename="kiwix-macos_3.7.1.dmg", 209 | size=6392295, 210 | ), 211 | Reader( 212 | platform="linux", 213 | download_url="https://mirror.download.kiwix.org/release/kiwix-desktop/kiwix-desktop_x86_64_2.3.1-4.appimage", 214 | filename="kiwix-desktop_x86_64_2.3.1-4.appimage", 215 | size=146629824, 216 | ), 217 | ] 218 | 219 | print("> Adding Dashboard") 220 | builder.add_dashboard(allow_zim_downloads=True, readers=readers, links=links) 221 | print("> Adding Captive Portal") 222 | builder.add_captive_portal() 223 | print("> Adding Reverse-proxy") 224 | builder.add_reverseproxy() 225 | 226 | print("> Adding ZIMs") 227 | for zim_ident in ZIM_TITLES: 228 | print(f"> - Adding {zim_ident}") 229 | builder.add_zim(get_zim_package(zim_ident)) 230 | 231 | print("> Adding Packages") 232 | for package_ident in PACKAGES: 233 | print(f"> - Adding {package_ident}") 234 | package = app_catalog[package_ident] 235 | if isinstance(package, AppPackage): 236 | builder.add_app(package) 237 | elif isinstance(package, FilesPackage): 238 | builder.add_files_package(package) 239 | 240 | if FILES_APP_ZIP_URL and "file-manager.offspot.kiwix.org" in PACKAGES: 241 | print(f"> Adding ZIP from {FILES_APP_ZIP_URL}") 242 | builder.add_file( 243 | url_or_content=FILES_APP_ZIP_URL, 244 | to="${APP_DIR:file-manager.offspot.kiwix.org}", 245 | size=get_online_rsc_size(FILES_APP_ZIP_URL), 246 | via="zip", 247 | is_url=True, 248 | ) 249 | 250 | if ADD_HWCLOCK_MGMT: 251 | print("> Adding Clock") 252 | builder.add_hwclock() 253 | 254 | if ADD_METRICS: 255 | print("> Adding Metrics") 256 | builder.add_metrics() 257 | 258 | return builder 259 | 260 | 261 | def main(): 262 | print("Preparing YAML Config file…") 263 | builder = get_builder() 264 | print("Rendering YAML Config file…") 265 | yaml_text = builder.render() 266 | print(f"Writing YAML to {YAML_CONFIG_PATH}") 267 | Path(YAML_CONFIG_PATH).write_text(yaml_text) 268 | print("Done.") 269 | 270 | 271 | main() 272 | -------------------------------------------------------------------------------- /docs/Kiwix Hotspot Tutorial.md: -------------------------------------------------------------------------------- 1 | # Create your own WiFi knowledge hub with Kiwix Hotspot 2 | 3 | > [!TIP] 4 | > If you're just interested in such an Hotspot but are not into DIY, check-out [Kiwix's Website](https://kiwix.org/en/wifi-hotspot/). 5 | 6 | A *Kiwix Hotspot* is a mini-computer exposing a WiFi network that anyone (or those with its password) can connect to and get prompted with a list of Web-resources replicas to access directly. No Internet access required. Only a Raspberry Pi, it's SD card and a source of power for the Pi. 7 | 8 | > [!WARNING] 9 | > This guide is intended for DIY enthusiasts that are computer savvy. 10 | > You'll be mostly using the command-line and even writing some very simple copy-paste-able code. 11 | > Nothing difficult but you will need to figure out by yourself how to access the tools mentioned. 12 | > This tutorial is not **the only solution** to deploy a Kiwix Hotspot, it is only a recommendation / guide around know-how on how to do this in a straightforward manner. 13 | 14 | 15 | ## Gathering Hardware 16 | 17 | Hardware is very simple but there are a couple of things not to overlook. 18 | 19 | - A **64bits Raspberry Pi** (see table below). That's the only hardware we support. 20 | - Don't use a Pi Zero2W just yet. We don't support it (we will though). 21 | - **Appropriate Power Supply** for your Pi. Using an underated (or poor quality) power supply can lead to very weird issues that you won't be able to diagnose or even link to the power supply. Various Pi models have various requirements. See below. As all are 5V rated, using an higher capacity one is OK. 22 | - **New, good quality SD-card**. In many cases, the SD-card speed will be your bottleneck. SD-card is somewhat fragile and degrades over use. Decent ones are cheap enough for you not to get the cheapest which will lead to trouble. There's no guidance on finding good quality ones but using a popular brand (Sandisk, Samsung) is usually enough. 23 | 24 | | Pi Model | Min. Wattage | Min Amps | 25 | | --------- | ------------ | -------- | 26 | | `Zero2W` | 12.5W | 2.5A | 27 | | `3` | 12.5W | 2.5A | 28 | | `4`/`400` | 15W | 3A | 29 | | `5`/`500` | 27W | 5A | 30 | 31 | > [!NOTE] 32 | > Out of scope for this guide but it's possible to use an SSD instead of an SD-card for better speed and reliability. 33 | > Make sure you master SD-card version first though. 34 | > It is also possible (but less recommended, and out of scope as well) to use an external USB drive plugged into the Pi. 35 | 36 | ## Step 1: identify the content you want to include 37 | 38 | Believe it or not, this is the most tedious and difficult step yet that's the only one we can't really help you with. 39 | 40 | > [!IMPORTANT] 41 | > If following this guide for the first time, just find a couple of small content or use our suggestions. 42 | > Once you have completed all the steps and it's working as expected, you can restart from here with 43 | > your carefuly curated content list. You don't want typos and long downloads to come in the way and lead 44 | > to long and frustrating attempts. 45 | 46 | **Suggestion**: 47 | 48 | ``` 49 | openZIM:wikipedia_en_climate_change:nopic 50 | openZIM:raspberrypi.stackexchange.com_en_all:all 51 | ``` 52 | 53 | The's a notion of *Title ID* in Kiwix Hotspot that's not really exposed anywhere so you'll have to construct them yourself: 54 | 55 | 1. Find your wanted content on https://library.kiwix.org/ and click on it. 56 | 2. Spot the ID part in URL. For https://library.kiwix.org/viewer#archlinux_en_all_nopic_2022-12/A/Main_page it's `archlinux_en_all_nopic_2022-12`. 57 | 3. Change URL to get the `Name`, `Publisher` and `Flavour` metadata with the URLs as https://library.kiwix.org/raw/archlinux_en_all_nopic_2022-12/meta/Name. Change trailing `Name` to `Publisher` and `Flavour` to get them. If `Flavour` URL is 404, it means Flavour is empty. 58 | 4. Construct ID as `{Publisher}:{Name}:{Flavour}` so `Kiwix:archlinux_en_all:nopic` for this one. 59 | 60 | Keep a list of your IDs, you'll need them for next step. 61 | 62 | All of them must be three part, separated by `:`. Last part (flavour) can be empty. 63 | 64 | 65 | ## Step 2: Build the Image's YAML recipe 66 | 67 | That's the scary code-involving step. The approach here is to provide you with a sample source file that constructs an image YAML file 68 | from some variables at the top. This way, you can simply change those variables and you should be good to go. 69 | If you're comfortable with Python, go crazy! 70 | 71 | This step requires a **working Python3** installation. You can use WSL2 on Windows or Docker if you prefer. 72 | 73 | With Docker: 74 | 75 | ```sh 76 | # getting a shell with a working Python setup using Docker 77 | ❯ docker run -v $PWD:/data -it python:3.11-bookworm bash 78 | ``` 79 | 80 | Or if you don't use Docker, make sure to be on an isolated virtualenv: 81 | 82 | ```sh 83 | ❯ python3 -m venv tuto-env && source tuto-env/bin/activate 84 | ``` 85 | 86 | First, install required dependencies: 87 | 88 | ```sh 89 | ❯ pip install offspot-config 90 | ``` 91 | 92 | Now copy the [`tuto-builder.py`](tuto-builder.py) script and edit its variables at the top of the file. 93 | 94 | ```py 95 | # where to write the resulting YAML file to 96 | YAML_CONFIG_PATH = "conf.yaml" 97 | 98 | # 99 | # SETTINGS 100 | # 101 | # 102 | NAME = "My Hotspot" 103 | # main domain to access your domain: xxx.hotspot. ASCII, numbers and dash 104 | DOMAIN = "my-kiwix" 105 | # SSID: max 32 chars. Forbidden chars: ^ ! # ; + \ / " \t 106 | SSID = "My SSID" 107 | # PASS: max 64 chars. No ASCII control characters. Leave empty for Open network 108 | PASSPHRASE = "" 109 | TIMEZONE = "UTC" 110 | ADMIN_USERNAME = "admin" 111 | ADMIN_PASSWORD = "admin-password" 112 | BRANDING_HORIZONTAL_LOGO_PATH = "" 113 | BRANDING_SQUARE_LOGO_PATH = "" 114 | 115 | # 116 | # CONTENT SELECTION 117 | # 118 | # Title IDs for your ZIM files 119 | ZIM_TITLES = [ 120 | "openZIM:wikipedia_en_climate_change:nopic", 121 | "openZIM:raspberrypi.stackexchange.com_en_all:all", 122 | ] 123 | # Package IDs from 124 | # https:/github.com/offspot/offspot-config/blob/main/src/offspot_config/catalog.json 125 | PACKAGES = [ 126 | "file-manager.offspot.kiwix.org", 127 | ] 128 | # URL to a ZIP file which content will be served in the files-resources app 129 | FILES_APP_ZIP_URL = "" 130 | ``` 131 | 132 | Run the file once satisfied: 133 | 134 | ```sh 135 | ❯ python tuto-builder.py 136 | Preparing YAML Config file… 137 | > Adding Readers 138 | > Adding Dashboard 139 | > Adding Captive Portal 140 | > Adding Reverse-proxy 141 | > Adding ZIMs 142 | > - Adding openZIM:wikipedia_en_climate_change:nopic 143 | > - Adding openZIM:raspberrypi.stackexchange.com_en_all:all 144 | > Adding Packages 145 | > - Adding file-manager.offspot.kiwix.org 146 | > Adding Clock 147 | > Adding Metrics 148 | Rendering YAML Config file… 149 | Writing YAML to conf.yaml 150 | Done. 151 | ``` 152 | 153 | Your YAML configuration file is ready for next step. 154 | 155 | ## Step 3: Build the Image (downloads everything) 156 | 157 | ### Check requirements 158 | 159 | This step requires you to be **root on a GNU/Linux machine**. You can use WSL2 on Windows or Docker (`--privileged`) if you don't have access to a Linux machine. 160 | 161 | First, download the lastest version of [`image-creator`](https://github.com/offspot/image-creator) [from the drive](https://drive.offspot.it/image-creator/): `1.1.3` as I'm writing. 162 | 163 | Make sure all requirements are satisfied: 164 | 165 | **Kernel features**: 166 | 167 | - `loop` must be enabled in your kernel or as a module. if running inside a docker-container: `loop` must be enabled in host kernel as well. Container must be run with `--privileged`. 168 | - `ext4` filesystem (most likely enabled in-kernel) 169 | 170 | **Tools:** 171 | 172 | - `losetup`, `mount`, `umoun` (`mount`) 173 | - `parted`, `partprobe` (`parted`) 174 | - `resize2fs` (`e2fsprogs`) 175 | - `qemu-img` (`qemu-utils`) 176 | - `mknod` (`coreutils`) 177 | - `dmsetup` (`dmsetup`) 178 | 179 | **Sample setup (debian)** 180 | 181 | ```sh 182 | sudo modprobe --first-time loop 183 | sudo modprobe --first-time ext4 184 | sudo apt-get install --no-install-recommends coreutils dmsetup mount e2fsprogs qemu-utils parted 185 | ``` 186 | 187 | Any missing requirements will be printed when running `image-creator`. **Sort those out first**! 188 | 189 | ### Build the image 190 | 191 | Now run it referencing **your actual YAML config** from previous step. Make sure to check `--help` also. 192 | 193 | It is recommended to use a cache for content which be downloaded, so that any subsequent attempts to build an image does not require re-downloading everything. But this cache can be [cumbersome to configure](https://github.com/offspot/image-creator?tab=readme-ov-file#cache-policy). And this cache-dir **must be on an ext4** filesystem. 194 | 195 | ```sh 196 | ❯ mkdir -p cache 197 | ❯ printf "enabled: true\nmax_size: 100GiB\n" > cache/policy.yaml 198 | ❯ ./image-creator --cache-dir $(pwd)/cache conf.yaml out.img 199 | 200 | _ _ 201 | (_)_ __ ___ __ _ __ _ ___ ___ _ __ ___ __ _| |_ ___ _ __ 202 | | | '_ ` _ \ / _` |/ _` |/ _ \_____ / __| '__/ _ \/ _` | __/ _ \| '__| 203 | | | | | | | | (_| | (_| | __/_____| (__| | | __/ (_| | || (_) | | 204 | |_|_| |_| |_|\__,_|\__, |\___| \___|_| \___|\__,_|\__\___/|_| 205 | |___/ v1.1.3|py3.11.9 206 | 207 | 208 | [2025-02-10 11:04:05] :: Checking system requirements 209 | [2025-02-10 11:04:05] => Checking uid 210 | [2025-02-10 11:04:05] => Checking binary dependencies 211 | [2025-02-10 11:04:05] => Checking loop-device capability 212 | [2025-02-10 11:04:05] => Checking ext4 support 213 | [2025-02-10 11:04:05] :: Checking config inputs 214 | [2025-02-10 11:04:05] => Reading config from /conf.yaml 215 | [2025-02-10 11:04:05] => Parsing config data 216 | [2025-02-10 11:04:05] => Making sure base and output are different 217 | [2025-02-10 11:04:05] => Checking target path 218 | [2025-02-10 11:04:05] => Testing target location /out.img 219 | [2025-02-10 11:04:05] :: Checking Cache Policy 220 | [2025-02-10 11:04:05] => Checking user_xattr support at /cache 221 | [2025-02-10 11:04:05] => Reading cache policy at /cache/policy.yaml 222 | [2025-02-10 11:04:05] => Preparing cache at /cache 223 | [2025-02-10 11:04:05] :: Enforcing Cache Policy 224 | [2025-02-10 11:04:05] => No entry to evict 225 | [2025-02-10 11:04:05] :: Checking all Sources 226 | [2025-02-10 11:04:05] => Checking https://drive.offspot.it/base/offspot-base-arm64-1.2.1.img 3.23 GiB 227 | [2025-02-10 11:04:05] => Checking https://mirror.download.kiwix.org/release/kiwix-desktop/kiwix-desktop_windows_x64_2.4.1.zip 125.95 MiB 228 | [...] 229 | ``` 230 | 231 | You now have a `.img` file which is your *Raspberry Image File*. 232 | 233 | ## Step 4: Flash the Image onto the SD-card 234 | 235 | This is standard and you can use any tool you'd prefer for this. 236 | 237 | We recommend you [Download](https://www.raspberrypi.com/software/) and use **`rpi-imager`**. 238 | 239 | 1. In *Operating System*, select *Use Custom* at the very end of the list and pick the `.img` file you built in previous step. 240 | 2. In *Storage*, select your SD-card (it must be attached to your computer obviously). 241 | 3. Hit Next 242 | 4. **Don't apply OS customisation**. This is not compatible with Kiwix Hotspot and will prevent it from booting. 243 | 5. Once writing is complete, **don't cancel verify**. It's an essential step in trusting your SD-card. 244 | 245 | ![rpi-imager-1.png](rpi-imager-1.png) 246 | ![rpi-imager-1.png](rpi-imager-2.png) 247 | ![rpi-imager-1.png](rpi-imager-3.png) 248 | 249 | You SD-card is now ready and can be removed from your computer. 250 | 251 | ## Step 5: First-boot and Go 252 | 253 | Insert your SD-card into the Pi and turn it on. You don't need to plug in a keyboard or a screen as the Hotspot is meant to be connected to from other devices over WiFi. 254 | 255 | **Be patient** during first boot as there is a file-system expansion step (so all free space on your SD card is available), a filesytem check, then the device is rebooted and actual first boot happen with containers creation. 256 | 257 | You can then use a phone or laptop to connect to the new WiFi network named after your chosen SSID (in your conf.yaml). You'll be prompted with the captive portal that will take you to the dashboard. **Enjoy!** 258 | 259 | 260 | ### Beyond the tutotial 261 | 262 | All of this is free software available on Github. It's very flexible but barely documented. Feel free to ask questions on the Issue Tracker of this repo though! 263 | 264 | If you wan to gain SSH access to your Hotspot, you'll have to enable it from a running Pi (using a screen and a keyboard). Console credentials are `user` / `raspberry`. Enable SSH with `sudo systemctl enable --now ssh`. 265 | 266 | You can also change the SSID and password among other things by tweaking the `/boot/offspot.yaml` file. Check its [documentation](https://github.com/offspot/offspot-config). 267 | 268 | Check out the `/data` partition content. You can manually add/remove ZIM files into `/data/contents/zims/` and after a reboot, they'll appear on the dashboard. 269 | 270 | Except for the WiFi Access Point (`hostapd`), everything related to Kiwix Hotspot runs as Docker containers so there's little risk for you to break anything. Go wild, it's your machine after all! 271 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Kiwix Hotspot 2 | 3 | `offspot` is a collection of tools and solutions to support **Kiwix Hotspot**. 4 | 5 | A Kiwix Hotspot is a Raspberry Pi computer running a WiFi hotspot and serving content and services over HTTP to the its WiFi clients. 6 | It's a software stack on top of a regular RaspberryPi OS but distributed as an image file. 7 | The resulting system can still be used freely. 8 | 9 | ➡️ **TUTORIAL:** [Create your own WiFi knowledge hub with Kiwix Hotspot](https://github.com/offspot/overview/blob/main/docs/Kiwix%20Hotspot%20Tutorial.md) ⬅️ 10 | 11 | --- 12 | 13 | ![offspot-diagram.png](offspot-diagram.png) 14 | 15 | This diagram demonstates that the Pi OS only runs a couple of services and that all the content and apps are provided via Docker containers. 16 | 17 | Using a dockerized approach is key in offering a clean, reliable and maintainable base-system while allowing all sorts of usages and Web Apps. 18 | 19 | ## Base OS 20 | 21 | Our Base OS is called `base-image` and is built on RaspberryOS Lite. Just like RaspberryOS, it is built using pi-gen. 22 | 23 | [`base-image`](https://github.com/offspot/base-image) is the repository holding our changes and script to build it. Its output is an IMG file. We host our releases at [drive.offspot.it/base/](https://drive.offspot.it/base/). 24 | 25 | You can use it to create a different base image and use it when creating a Kiwix Hotspot. Be sure not to break our key components though. 26 | 27 | ### Main Changes 28 | 29 | - Less packages. A Kiwix Hotspot doesn't need Bluetooth and GPIO for instance. 30 | - Default User: `user` / `raspberry`. 31 | - SSH installed but not started. Connect to console to enable it (`sudo systemctl enable --now ssh`) 32 | - Three partitions layout: `/boot` (`FAT32`), `/` (`ext4`) and `/data` (`ext4`). Root filesystem size is limited ❗ 33 | - Custom initial-boot resize script to expand `/data` partition to use all remaining space on device. 34 | - No SWAP. 35 | - Custom WiFi firmwares to support more AP clients than stock firmware. 36 | - Reduced logs to save I/O 37 | - Docker Stack (balena-engine + Docker Compose) 38 | - Automatic Docker images loading on Start 39 | - Internet-connectivity check timer 40 | - DHCP client service configured for eth0 (`dhcpcd`) 41 | - Persistent firewal (`iptables` restore on start) 42 | - DNS Server (`dnsmasq`) orchestrated by offspot-runtime 43 | - WiFI AP (`hostapd`) orchestrated by offspot-runtime 44 | - Offspot-Runtime service on boot to configure or start DNS/AP/etc 45 | 46 | ## Offspot Runtime 47 | 48 | [`offspot_runtime`](https://github.com/offspot/offspot-config), part of `offspot-config` repository is a collection of scripts that are run on every start via `offspot-runtime.service`. 49 | 50 | It's goal is two fold: 51 | 52 | - Configure the aforementioned tools that are installed on the Host. 53 | - Start those tools. 54 | 55 | The configuration part is meant to be run on first boot but can happen at any boot. We chose to configure those things on boot so the image-creation step (`image-creator` below) doesn't need a working system and can remain a dumb file-copying tool. 56 | 57 | It also allows dynamically changing some settings which users are kin to customize (SSID, password, etc). 58 | 59 | In practice, it is multiple scripts ; each focusing on a *task* (usually operating a single underlying tool) that can be invoked directly, with inputs passed on the CLI. 60 | 61 | It's not used this way in general, as its service runs `offspot-runtime-config-fromfile /boot/firmware/offspot.yaml` 62 | 63 | > [!IMPORTANT] 64 | > This reads that file and calls all scripts individually with the args corresponding to the config file. As those configs are applied, configuration is removed from the file. In a booted, configured machine, that file is thus an empty YAML document. 65 | > The file is thus changed to **request a configuration change**. 66 | 67 | This file is mandatory to configure the Hotspot the first time and the base-image includes a minimnal one. 68 | 69 | This file is purposedly stored on `/boot` partition as this one is FAT32 and can thus be modified on all platforms. 70 | 71 | Documentation for this file is on [`offspot_config`](https://github.com/offspot/offspot-config)'s README. 72 | 73 | ## Offspot Config 74 | 75 | [`offspot-config`](https://github.com/offspot/offspot-config) is a Python library to build Kiwx Hotspot YAML recipe file that is fed to `image-creator`. 76 | 77 | It is used to configure everything as its output is the only input to get a working image file. 78 | 79 | At the moment, it's only code but it's quite easy to use. 80 | 81 | ```py 82 | builder = ConfigBuilder( 83 | base=BaseConfig( 84 | source="1.2.1", 85 | rootfs_size=2663383040, 86 | ), 87 | name="My Hotspot", 88 | domain="my-kiwix", 89 | welcome_domain="goto.kiwix", 90 | tld="hotpot", 91 | ssid="My SSID", 92 | passphrase="", 93 | timezone="UTC", 94 | environ={ 95 | "ADMIN_USERNAME": "admin", 96 | "ADMIN_PASSWORD": "admin-password", 97 | }, 98 | write_config=True 99 | ) 100 | builder.add_dashboard(allow_zim_downloads=True) 101 | builder.add_captive_portal() 102 | builder.add_reverseproxy() 103 | builder.add_zim(get_zim_package("openZIM:wikipedia_en_climate_change:nopic")) 104 | ``` 105 | 106 | Check out our [Hotspot Tutorial](https://github.com/offspot/overview/blob/main/docs/Kiwix%20Hotspot%20Tutorial.md) for more details or look into Imager Service's code. 107 | 108 | 109 | ## Image Creator 110 | 111 | [`image-creator`](https://github.com/offspot/image-creator) is a Linux-only, root-only command-line tool to prepare a Kiwx Hostpo image (IMG) file from an offspot-config-made recipe file. 112 | 113 | > [!NOTE] 114 | > Although Linux-only, it runs fine on macOS via Docker (use `--privileged`) and Windows via WSL2. 115 | 116 | The recipe includes the URL/path to a base image file that is copied, mounted and modified. Then, the tools downloads all files references in the recipe and places them inside the mounted image at their requested location. Once done, it unmounts everything and boom. You have a ready Kiwix Hotspot image! 117 | 118 | The tool includes an [aria2](https://github.com/aria2/aria2) based downloader that ensure files integrity and a flexible Downloads Cache based on `ext4`'s [`user_xatttr`](https://www.man7.org/linux/man-pages/man7/xattr.7.html). 119 | 120 | The recipe YAML format and the Cache Policy YAML format are both documented on [`image-creator`](https://github.com/offspot/image-creator)'s README. 121 | 122 | ## Captive Portal 123 | 124 | The [Captive Portal](https://github.com/offspot/captive-portal) is feature that greatly boosts User Experience for Hotspot Clients. When enabled (we always enable it), upon connecting to a Kiwix Hotspot's network, the user is quickly prompted by his Operating System with a special Web Page. 125 | That webpage includes the Hotspot's logo and name, with a brief description so the User knows what's happening. 126 | He is asked to confirm and upon its click, he is redirected to the hotspot's home page (dashboard). 127 | 128 | That's the goal: allow anyone to arrive to the dashboard, without having to know any URL or face scary prompts. 129 | 130 | > [!WARNING] 131 | > If the hotspot is not connected to the Internet itself (it usually isn't!), some systems (Android, iOS) may tell the user that the network lack Internet connectivity and ask the user to confirm they're OK on this network. That happens post-captive portal though. 132 | 133 | ![captive-portal.png](captive-portal.png) 134 | 135 | Behind the scene, what happens is: 136 | 137 | - *Unregistered* IP's HTTP requests are captured by the firewall and directed to this App. 138 | - This welcome message is presented with an invitation to confirm (*register*) 139 | - Upon confirmation, the client's IP is added to the firewall's list of *registered* IPs 140 | - Traffic for *registered* IPs is not captured and can thus access the hotspot. 141 | - Web browser is directed to the hotspot's home page. 142 | 143 | There's an expiration on that *registration* so that multiple users sharing a single computer can still benefit from this feature. 144 | 145 | ## Dashboard 146 | 147 | The [`dashboard`](https://github.com/offspot/dashboard/) displays a cards/grid view of the content listed in a `home.yaml` file. 148 | 149 | > [!TIP] 150 | > It also offers a special view to download the content for which a download link was supplied. That's very useful to allow users to download ZIM file as well as Kiwix Readers so they can copy from the Hotspot and continue hotspot-less on their Android device for instance 151 | 152 | ![dashboard.png](dashboard.png) 153 | 154 | As other Hotspot App, dashboard is a Docker image. It is composed of: 155 | 156 | - A static web server (`lighttpd`) 157 | - A script that runs on startup and rebuilds the static page 158 | 159 | This allows a somewhat dynamic approach in that one can modify the `home.yaml` file and reboot to get an updated version but still benefit from a static, fast website. 160 | 161 | > [!TIP] 162 | > It also features a ZIM discovery feature that checks the ZIM folder and automatically removes from the dashboard those that are not present anymore and adds any new one not listed in `home.yaml`. It does so by querying the ZIM itself for its metadata. 163 | > This happens at startup as well. 164 | 165 | Documentation for the Home YAML file is on the [`dashboard`](https://github.com/offspot/dashboard/)'s README. 166 | 167 | ## Apps 168 | 169 | Even though it's not a requirement, we usually create dedicated apps for the hotspot so the image are small. 170 | 171 | Our apps are all on [`container-images`](https://github.com/offspot/container-images). 172 | 173 | Some of them are special (reverse-proxy, captive-portal) and their integration is built into `offspot-config`, others are more standard. 174 | 175 | Those are listed in [`catalog.json`](https://github.com/offspot/offspot-config/blob/main/src/offspot_config/catalog.json) with their integration properties. This `catalog.json` is not standardized at all and will certainly change in the future. 176 | 177 | > [!NOTE] 178 | > Some apps in the Catalog are virtual (files packages) as those are simply ZIP files containing an HTML document and support files. 179 | > Those are exposed as individual web-apps to users but it's a single static web server behind the scene. 180 | > We use it for external download content like Android Apps. 181 | 182 | --- 183 | 184 | ## Imager Service 185 | 186 | [Kiwix Imager Service](https://github.com/offspot/imager-service) is a SaaS platform that provides a Web UI to configure a Hotspot, request it, have it done by a worker, be notified via e-mail with a link once ready, etc. 187 | 188 | It's entirely free as the rest of the stack but it's tailored solely to our https://imager.kiwix.org/ needs. Check out its source-code though for samples on how to do those various actions. 189 | 190 | 191 | --- 192 | 193 | ## Repositories 194 | 195 | | Tool | Description | 196 | | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | 197 | | [`base-image`](https://github.com/offspot/base-image) | raspiOS-like _base_ image builder: adds/removes package, adds some configuration, tweaks and tools, installs `offspot_runtime` (part of `offspot_config`) | 198 | | [`offspot_runtime`](https://github.com/offspot/offspot-config) | set of scripts to (re-)configure some stuff on boot: network, WiFi, etc. | 199 | | [`offspot_config`](https://github.com/offspot/offspot-config) | library for parsing/creating offspot YAML config. Include a Config Builder and an App Catalog | 200 | | [`image-creator`](https://github.com/offspot/image-creator) | _somewhat_-generic Image creator taking a YAML config as input. YAML config lists all files to download, and includes a complete docker-compose. This is not user-friendly at all. Linux only, runs as root. | 201 | | [Kiwix Imager Service](https://github.com/offspot/imager-service) | Web UI to select content. Uses the offspot-config builder to produce YAML. Calls image-creator in worker to build image then uploads it. https://imager.kiwix.org | 202 | | Kiwix Imager App | **Not implemented yet**. kiwix-hotspot replacement. UI to select content and configure. Will use offspot-config builder to gen a YAML and call image-creator | 203 | | [`dashboard`](https://github.com/offspot/dashboard) | In-hotspot Web dashboard listing content with metadata and links. Also provides Download of downloadable ones (ZIM files) and Kiwix Readers | 204 | | [`container-images`](https://github.com/offspot/container-images) | Kiwix-Hotspot-optimized OCI Images for our apps ; including the reverse-proxy, kiwix, etc. | 205 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | --------------------------------------------------------------------------------