There is this open issue (which I just closed) on Discourse Docker repo asking Discourse should behave like a standard docker image a docker user excepts to be able to run discourse without a special launcher. to define multiple containers (redis, postgres, discourse,..), links and volumes, dock…

[画像] sam: The thing is you are making an assumption here that our current design is somehow limiting from a deployment perspective. By way of disclaimer, I am not employed or compensated by any hardware vendor, Saas provider, or forum software developers. Think about how many potentially unn…

[画像] pfaffman: ./discourse-setup is for people who don’t know what nano is (and would never be able to figure out how to quit vim ). This is exactly the point many folks have been making in this lengthy thread: Is there a solution for those who do know what nano is and can exit VI / VIM just …

[画像] gkoerk: Is there a solution for those who do know what nano is and can exit VI / VIM just fine? Yes. Create a web_only.yml (there is a sample in discourse_docker) and use that to build your docker image with your plugins. Then add it to your swarm. Everything can be configured via enviro…

Recently I found the commands to fast forward a git clone depth 1: git checkout --detach #avoid tangle with git tree state git fetch --depth 1 -f -origin [branch|commit] git checkout -f [branch|commit] Thanks to archive.org team.

[画像] sam: Internally when we deploy we use a “pre-bootstrapped” image as our base image and then simply run “assets:precompile” and “rake db:migrate” as our only bit of custom bootstrapping code. So would running ./launcher bootstrap mybase that had the bundle exec rake db:migrate; bundle exe…

[画像] sam: Internally when we deploy we use a “pre-bootstrapped” image as our base image and then simply run “assets:precompile” and “rake db:migrate” as our only bit of custom bootstrapping code. This allows us to mostly eliminate the need for an expensive bootstrap on every deploy. Images for o…

We technically pre-compile twice. Once for base image + our changes. Second time when we deploy specific sites with specific plugins. Our setup though is not something you would do unless you were hosting Discourse as a business.

I would really like to use Discourse. But the way these devs are using container technologie really stops me from using it. I have never saw a project that is able to make a container installation non-portable like this. There are much better ways to fix this. To me it seems like this project organi…

[画像] AquaL1te: I have never saw a project that is able to make a container installation non-portable like this. Try looking around in 2014. When the project started, docker-compose wasn’t really a thing. [画像] AquaL1te: And now the project is stuck with this overly complex and non-portab…

[画像] pfaffman: All you need to do is change everything about how to build and launch a container and see that it doesn’t break thousands of functioning sites I know it’s not an easy thing to do. But the purpose of containers is to have a consistent and portable state. So if containers are use…

Discourseはブートストラップ不要な頻繁に配信されるDockerイメージを提供できますか？

開発

トピック		返信	表示
Using a launcher built docker image in docker-compose Development	30	7924	2024 年 9 月 27 日
Container restart - discourse tries to reinstall Self-hosting unsupported-install	24	2962	2020 年 7 月 30 日
Installing on Kubernetes Self-hosting unsupported-install	55	25071	2026 年 2 月 6 日
Community supported official docker image Development	35	8665	2022 年 7 月 22 日
Why does Discourse have to use Docker? Self-hosting docker	36	10335	2018 年 9 月 29 日

Discourseはブートストラップ不要な頻繁に配信されるDockerイメージを提供できますか？

関連トピック