1
0
mirror of https://github.com/pirate/ArchiveBox.git synced 2025-09-02 19:02:37 +02:00

Updated Docker (markdown)

Nick Sweeting
2019-02-26 20:20:43 -05:00
parent 6374717898
commit 871c5eb61e

@@ -11,7 +11,7 @@ cd /path/to/ArchiveBox
mkdir data && chmod 777 data
docker-compose up -d
```
Then open `http://127.0.0.1:8098` (HTTP, not HTTPS) to view the archive. If you want HTTPS, put a reverse proxy link nginx or caddy in front of `127.0.0.1:8098`.
Then open `http://127.0.0.1:8098` (HTTP, not HTTPS) to view the archive.
To add new URLs, you can use docker-compose just like the normal `./archive` CLI:
```bash
@@ -28,6 +28,8 @@ docker-compose exec archivebox /bin/archive /data/sources/bookmarks.html
To pass in environment variables for configuring ArchiveBox, edit `docker-compose.yml`, create a `.env` file in the project root, or specify an env file when running compose using `docker-compose --env-file=/path/to/config.env ...`.
If you want to access your archive server with HTTPS, put a reverse proxy like Nginx or Caddy in front of `127.0.0.1:8098` to do SSL termination.
# Docker
Docker-compose is the recommended way to run ArchiveBox with docker, as it's a much easier CLI interface and more of the setup is taken care of by docker-compose using the single yaml config file as opposed to CLI flags. The docker-compose setup also provides an nginx webserver to serve the archive right out of the box, whereas you have to set that up manually if you use plain docker.