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

feat:setup celery for local development #100

Closed
wants to merge 5 commits into from

Conversation

hareshkainthdbt
Copy link
Collaborator

No description provided.

Reorganized application package structure to improve modularity and navigability. Moved files from `fbr` to `app` directory and renamed key modules to better reflect functionality, such as `celery_worker`. Additionally, updated all relevant imports and settings configurations to align with the new structure, including Django settings and task management.
Reorganized application package structure to improve modularity and navigability. Moved files from `fbr` to `app` directory and renamed key modules to better reflect functionality, such as `celery_worker`. Additionally, updated all relevant imports and settings configurations to align with the new structure, including Django settings and task management.
Moved Dockerfile and entry script out of local_deployment for a cleaner structure. Updated docker-compose and Makefile to reflect these changes, using a unified image to leverage caching. Removed Poetry setup in favor of using pip with requirements.txt for dependency management.
Introduce DATABASE_URL environment variable for local PostgreSQL setup in Docker and Makefile. Update `rebuild_cache` task with a specific name and adjust its schedule. Refactor Django settings and Makefile commands for improved database management consistency.
The schedule for the cache rebuild task was incorrectly documented as running at a different time than configured. This change aligns both the actual schedule and the comment to correctly indicate the task runs at 1:00 AM daily.
return Response(response, status=status.HTTP_200_OK)
except Exception as e:
return Response(
data={"message": f"error building csv download response: {e}"},

Check warning

Code scanning / CodeQL

Information exposure through an exception Medium

Stack trace information
flows to this location and may be exposed to an external user.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant