We were talking about this internally today, and someone reminded me of Andrew Brown's great series of posts about self-hosting.
forem.dev/andrewbrown/how-to-creat... might be a useful guide (the rest of the series he wrote is good, but this specific post covers separating out the template/view changes you'd like to make from the underlying forem code).
Building your own image, and putting it in an accessible repository, like dockerhub or quay.io, are required steps before you call foremimg and foremctl update to load the modified code - that's covered a bit in forem.dev/andrewbrown/how-to-keep-... but the default forem latest image is downloaded there (you'd need to point at your images, instead of forem:latest).
We were talking about this internally today, and someone reminded me of Andrew Brown's great series of posts about self-hosting.
forem.dev/andrewbrown/how-to-creat... might be a useful guide (the rest of the series he wrote is good, but this specific post covers separating out the template/view changes you'd like to make from the underlying forem code).
Building your own image, and putting it in an accessible repository, like dockerhub or quay.io, are required steps before you call
foremimgandforemctl updateto load the modified code - that's covered a bit in forem.dev/andrewbrown/how-to-keep-... but the default forem latest image is downloaded there (you'd need to point at your images, instead of forem:latest).Thanks a lot Dan - those posts are very instructive, and we'll dig into them/test as we work out what route to take forward. Really appreciate it.