-
-
Notifications
You must be signed in to change notification settings - Fork 15.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix/docker server #1274
base: main
Are you sure you want to change the base?
Bugfix/docker server #1274
Conversation
thanks for the PR @knighttower ! Few question:
|
Hello @HenryHengZJ , Q- "Is it still possible to use the docker-compose way to install Flowise via npm?"
If anyone still wants or need to install extra stuff, they can use the Q- "Is it still possible to use the root level Dockerfile to build & install Flowise locally?" Q- "Does the new method works across different deployments like Render, AWS, DigitalOcean, Azure, GCP - https://docs.flowiseai.com/deployment" Note that once this PR is merged the docs there need to Updated. They seem to be outdated anyway, so this will be a good push to make updates happen at that end. For reference: I updated the Readme files of this repo to reflect the new changes: Let me know if you have any other questions. Thanks! |
Reason we have 2 Dockerfiles, 1 for building image locally, and the other 1 for building via docker-compose using image from dockerhub, is because some cloud services dont support docker-compose like you mentioned Render. Will have to test thoroughly across different deployments to verify if they are still working the same. Plus, we will be merging in this PR which introduces new infrastructure change, so might hold off on this PR for a while |
Fixes
New Features
npm run docker:start
npm run docker:stop
npm run docker:cli
Usage and instructions