Skip to content
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

Update packages and resurrect Feluda #3

Closed
4 tasks done
Tracked by #2
dennyabrain opened this issue Jan 17, 2024 · 3 comments
Closed
4 tasks done
Tracked by #2

Update packages and resurrect Feluda #3

dennyabrain opened this issue Jan 17, 2024 · 3 comments
Assignees
Labels
level:feature An issue that describes a feature (initiative>feature>ticket)

Comments

@dennyabrain
Copy link
Contributor

dennyabrain commented Jan 17, 2024

Tickets

  • Update packages
  • Server and Store are running but not tested
  • Run Queue and Test it
  • Document the uptodate method to bring up feluda locally
@dennyabrain dennyabrain added the level:feature An issue that describes a feature (initiative>feature>ticket) label Jan 17, 2024
@duggalsu
Copy link

The Feluda packages are old and compatible for Python v3.9 (cp39).

Trying to setup via docker gives the following issues

@duggalsu
Copy link

Docker - RabbitMQ and elasticsearch spin-up successfully.
Flask url does not open - possibly refer - https://www.freecodecamp.org/news/how-to-dockerize-a-flask-app/
Need to setup/start server

@duggalsu
Copy link

duggalsu commented Jan 17, 2024

Moving all operator packages to requirements. These packages are installed during server start, so there is no reason to keep them in separate files.

  • This prevents system-wide root pip install that can damage linux machines. Packages will get installed in venv.
  • This also makes package management easier from one place.
  • Package dependency checks can later be performed to remove unused packages (if that was a reason for keeping operator packages within specific files).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level:feature An issue that describes a feature (initiative>feature>ticket)
Projects
Status: Done
Status: Done
Development

No branches or pull requests

3 participants