[feature request] Describe a way to self-host Markwhen / Dockerize Markwhen

[asitemade4u]

Hi, And bravo for the great work: Markwhen is outstanding. The title says it all: do you intend to make Markwhen self-hostable? Or is it already self-hostable via a bit of tinkering. Please, keep us posted. S.

[juliennicouleaud]

Hi! Same question here, self-hosting would be great :)

[Fenisu]

Hi! I am here for the same reason. Does anybody managed to dockerize it?

[ItsNoted]

Yes please.

[kochrt]

I don't have much experience with docker but the general flow for running is something like

> git clone [email protected]:mark-when/markwhen.git
> cd markwhen
> npm i
> npm run build

and then the assets in /dist can be statically hosted. Node v16.15.0 is expected.

[aaparmeggiani]

Add development Docker support https://github.com/mark-when/markwhen/pull/108

[aaparmeggiani]

Thinking of a self-host/production dockerized version, what would be the requirements?

• do we need a http server in front of it? (despite that wouldn't be necessary behind an ingress in the cloud)
• how should data be persisted, aiming for a stateless container?

[accforgithubtest]

self-host/production dockerized version

I am just looking for this when I discovered this project on reddit. My list for minimum requirements would be -

1. A single docker image that includes the visualizations (no multiple containers please).
2. Clear documentation on a docker compose set up with details for ports mappings, volumes, environment variables, etc.
3. Support for reverse proxying with https (using caddy, traefik, etc)

Looking from comments on other issues, it seems like right now there are separate components that are needed to fully selfhost this.

Would be great to have them all as part of a single container image.