Closed kasugaijin closed 1 month ago
Also, you really probably want to also have the docker container launch the javascript / assets process as well. The line in the Procfile that looks like: css: bin/rails dartsass:watch
basically, if you're running a full docker-compose container, you can fully avoid using the Procfile structure (foreman
is quite a bit older than docker, and can be supplanted, it turns out)
That may also address what you were seeing and trying to address with the asset precompile, but there may be some port-mapping things to wrangle....
css: bin/rails dartsass:watch
Ah right thank you for catching that. I have added a SASS container.
@cflipse So I think this is good to go for now until we need to consider configration for deployments, right? I added some instructions for setting up local dev environment to the readme.
@cflipse bump
Dockerizing the app to help lower the barrier to getting up and running for contributors. I opted to just use a dockerfile with docker-compose and rely on docker commands to get up and running - not using a devcontainer for now (I do not use VSCode).
With these changes so far, the app works as expected in Docker. However:
🔗 Issue
✍️ Description
📷 Screenshots/Demos