Docker image #47

StrangeGirlMurph commented 2025年03月24日 18:20:36 +01:00 (Migrated from github.com)

How is it going with the announced docker image to deploy LumeCMS?

How is it going with the [announced](https://lume.land/blog/posts/lume-cms/#hosting-a-full-featured-cms) docker image to deploy LumeCMS?

oscarotero commented 2025年03月24日 18:46:35 +01:00

There's some progress here: https://github.com/lumeland/cms-deploy/tree/main
You can see the compose.yml and Dockerfile, but I'm not really expert in Docker, so any help here is welcome.

In this repo there's also an install script which is what I'm using currently for my projects. My goal is to simplify this process as much as possible.

There's some progress here: https://github.com/lumeland/cms-deploy/tree/main You can see the compose.yml and Dockerfile, but I'm not really expert in Docker, so any help here is welcome. In this repo there's also an install script which is what I'm using currently for my projects. My goal is to simplify this process as much as possible.

RickCogley commented 2025年03月31日 09:24:48 +02:00 (Migrated from github.com)

I recently set up a deno environment in Github Codespaces, for helping my colleagues working on sites with me, so they don't have to struggle setting up a local dev environment.

My understanding is that it's using Docker.

If you haven't used devcontainers, you fire it up from the green button in a github repo, it loads a vscode in a new browser tab, then you can run lume serve (and presumably lume cms but I have not tested) in vscode's built-in terminal.

When you do and once the usual localhost:3000 message appears, vscode pops up a message asking if you want to open in the browser. When you click that, another tab opens with some sort of unique URL that proxies the localhost:3000.

I wonder, might this be an option? Even on the free level of github, you still get some hours per month.

Here are the key files if you want to try it:

https://github.com/eSolia/blog.esolia.pro/blob/main/.devcontainer/devcontainer.json
https://github.com/eSolia/blog.esolia.pro/blob/main/setup.sh

I'm still shaky on whether the setup.sh is enough, but as I test with more people I'll know more. I wanted to have a decent prompt so I am loading starship, and also loading lume cli, to make things easier for the user.

One final thing, I learned that this docker that gets set up is per user. So when I run it, it sets up under my account, and the same thing for others who run it.

I recently set up a deno environment in Github Codespaces, for helping my colleagues working on sites with me, so they don't have to struggle setting up a local dev environment. My understanding is that it's using Docker. If you haven't used devcontainers, you fire it up from the green button in a github repo, it loads a vscode in a new browser tab, then you can run `lume serve` (and presumably `lume cms` but I have not tested) in vscode's built-in terminal. When you do and once the usual `localhost:3000` message appears, vscode pops up a message asking if you want to open in the browser. When you click that, another tab opens with some sort of unique URL that proxies the `localhost:3000`. I wonder, might this be an option? Even on the free level of github, you still get some hours per month. Here are the key files if you want to try it: https://github.com/eSolia/blog.esolia.pro/blob/main/.devcontainer/devcontainer.json https://github.com/eSolia/blog.esolia.pro/blob/main/setup.sh I'm still shaky on whether the `setup.sh` is enough, but as I test with more people I'll know more. I wanted to have a decent prompt so I am loading starship, and also loading lume cli, to make things easier for the user. One final thing, I learned that this docker that gets set up is per user. So when I run it, it sets up under my account, and the same thing for others who run it.