flask-unchained
flask-unchained copied to clipboard
briancappello
Docker
Hi, on hub.docker.com it's possible to build github tags. Latest tagged version has a versionconflict with py-meta-utils. Is current master ready to get a new version tag? Here is a dockerfile, mainly from your flask-unchained-react-spa project. I would like to work on a kubernetes configuration file next. Is kubernetes on your TODO.md list or is aws, gcp something else?
Nice, this looks good! I haven't had a chance to test it yet, hopefully tonight. Assuming it works I'm happy to merge. I haven't put any effort into this docker stuffs in probably a year, so some of this is starting to get old (eg PostgreSQL is at 11.1 these days). If you're feeling up to it, might be good to try to get that upgraded (probably you have to change the version of Alpine we're building atop)
@chriamue Started playing around with this. Just to clarify if I'm understanding how this is supposed to work, what I've been trying is this command from the flask-unchained directory:
docker build -t briancappello/flask-unchained .
Followed by this command from the project-under-development:
docker run -d --name PROJECT -p 5000:5000 -v "$(pwd)":/flask/src briancappello/flask-unchained
And this seems to work, at least if no bundles are installed :) I think the problem is, and I'm not sure what the best way to fix it would be, but I think somehow the container needs to get built with the requirements listed for the project-under-development.
Does that make sense? Or perhaps I'm just mis-understanding how this is supposed to be used :)
I think that should be used as an intermediate container like it is with node.
FROM flask-unchained
USER root
COPY .requirements.txt requirements.txt
RUN pip install -r requirements.txt
COPY requirements-dev.txt requirements-dev.txt
RUN pip install -r requirements-dev.txt
USER flask
COPY --chown=flask . /flask/src/
@chriamue I accidentally made a commit to this brach that didn't belong; feel free to force-push if you need to.