* add docker-compose with development dependencies
* delete old runtime.txt file
* specify specific group for postgres deps
* replace makefile with taskfile with new features
* drop template.env file in favor of defaults within taskfile
* use with github actions
* update docs for taskfile changes
* update task.json for vscode
* add taskfile to devcontainer.json
* pre-install taskfile so startup command works
* remove run command and fix desc for ui
* change node-> python->py for consistency
* WIP: proof of concept
* basic meta tag injection
* add support for scraping public/private links
* make tests go brrrrr
* cleanup initialization
* rewrite build config
* remove recipe meta on frontend
* make type checker happy
* remove other deployment methods
* fix issue with JSON response on un-authenticated request
* docs updates
* update tivy scanner
* fix linter stuff
* change registry tag
* build fixes
* fix same mistake I always make
* update dev docker poetry install
* Forward/Report IP through front and backend.
* Add fail2ban docs
* fix option name and iproute2 in omni entry
* Fix entry scripts -> gunicorn setting respected
* gunicorn off
* xfwd in nuxt proxy and handle multiple IPs
* Update docker-compose.yml
ERROR: The Compose file './docker-compose.yml' is invalid because:
services.mealie.environment.WEB_GUNICORN contains true, which is an invalid type, it should be a string, number, or a null
* Update docker-compose.yml
Also fix SMTP settings, since they aren't in array format as in mealie-frontend.
* Once more, ironing out a few minor issues.
Server status reported this, I think this is the correct value, but I'm happy to revert and/or update the value as needed.
* Revert previous two commits
Per https://github.com/hay-kot/mealie/pull/2109#pullrequestreview-1294610637
* Stray newline
Missed a stray newline that was inadvertently added.
* Corrected if statement to check if a results was returned by the LDAP search. And decoded the user_attributes from binary data to string
* removed trailing spaces
* Revert asserts in LDAP unit test back
Since an empty tuple is still a result, an user is created and the result should not be false.
* Simplified code
* Extended the LDAP implementation
* fix ldap authentication and user creation
* modified docs to include new LDAP environment variables
* update tests and linting
* add libldap-2.4-2 as runtime dependency for the api
---------
Co-authored-by: Erik Landkroon <eriklandkroon@gmail.com>
