rm-rf-etc / lektor-remote Goto Github PK

If you have docker installed, you don't need anything else (not even Lektor).

docker-compose up

This is a work in progress. Currently it's been tested only as far as running on localhost with docker-compose.

In lektor-project/ you'll see the output from running lektor quickstart. At the prompt for blog models I said no. Simply overwrite the content of lektor-project/ with your project files.

Ultimately, the goal is to have all manifests necessary to deploy Lektor to a remote server, and login via some auth process, such as basic auth.

In case you're not that familiar with docker, here's some commands to help you out.

To see output path:

docker run -it --mount type=bind,source=$(pwd)/lektor-project,target=/opt/lektor softinstigate/lektor project-info --output-path

To get an interactive bash session:

docker run -it --mount type=bind,source=$(pwd)/lektor-project,target=/opt/lektor --entrypoint bash softinstigate/lektor

And if the container is already running:

docker container ls
docker exec -it <container id> bash

Note, docker-compose is a different animal. And so too is docker swarm. If you're confused, you should be.

I see two images available on docker hub...

• softinstigate/lektor
• mfellner/lektor

Both can work but the lektor root is different, so update your volume path if you change the image.

• Add support for deployments (s3cmd, lektor-s3, other...)
• Need to recommend an approach to separate project files from Lektor container
• Add traefik and basic auth
• Probably other things that will come up once I try deploying to a docker swarm...