programming.dev/psql perf updates #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* configure debian docker apt repos * prettier lint
- Internal/external nginx were sending duplicate headers, removed from internal - Opted X-Frame-Options DENY as default - Fixes LemmyNet#143
Environment variable for setting API Key has changed in v0.4.0. This fixes the error: Invalid API Key with the old variable.
* Get dpkg-formatted arch and use it for docker apt repo - Fixes LemmyNet#130 - Tested against amd64/arm64 * Add conditional for dpkg command (Debian/Ubuntu), Adjust GPG path to use standard existing one - Path exists on at least Ubuntu >= 22.04, Debian 10, Debian 11
- Present/enabled in nginx.conf template
- Refs LemmyNet#109 - Co-authored by: Maximilian Praeger
* Fix duplicate headers being sent - Internal/external nginx were sending duplicate headers, removed from internal - Opted X-Frame-Options DENY as default - Fixes LemmyNet#143 * Remove redundant gzip lines - Present/enabled in nginx.conf template
* Remove installation via pip module, use apt - Resolves LemmyNet#152 * Update task name to be more accurate
* Add initial lemmy-almalinux.yml playbook - Supports AlmaLinux 9, RHEL 9, Rocky Linux 9 * Update docker-compose.yml to explicitly point to Docker Hub registry - By default EL9 lists 3x registries and prompts on short names, this allows unattended pulling without modifying registry configuration * Modify uninstall.yml playbook to support AlmaLinux/EL distributions - Add syntax check to lemmy-almalinux.yml playbook w/ woodpecker CI * Run `prettier` on playbooks to make lemmy-ansible upstream CI happy * Add some logic to the uninstall playbook for docker/podman/nginx - Installation starts and enables services, seems wise to offer inverse * Remove unused debug line * Update notes to be consistent with other task * Add distribution & version checks to lemmy-playbook, uninstall playbooks - EL >= 9 (for now?) - Add CentOS to list of targets (CentOS stream, boo hiss) * Revert postgres_password logic to be in-line with main playbook, docs * Update our targets baby! Technically should work on all EL9 spinoffs - But we build for ALmaLinux <3 * Add `always` tag for distribution/version check task * Gather facts for distribution conditionals
Newer OSs ship with python3 by default and not python2. The current raw check will always fail for them, so fix that.
- Rename pictrs.yml to vars.yml - Start moving some variables to vars.yml for easier management and discoverability
- Causes issues with how Ansible resolves variables - `server.com` != `root@server.com`, host_vars/server.com vs. host_vars/root@server.com
…nal.conf - Distribute proxy_params to nginx VM, include it as necessary in config - Resolves LemmyNet#155
Co-authored-by: Dessalines <tyhou13@gmx.com>
…es` user can read it - Refs LemmyNet#183 - Refs comment LemmyNet#183 (comment)
Adjust permissions for the distributed postgresql.conf
…tasks (LemmyNet#188) * Add ansible-core >= 2.11.0 requirement - Adds assertion to gracefully fail instead of an error (ref LemmyNet#177) - Add to README * Remove `become` on `localhost` to `lemmy-almalinux.yml` playbook - Refs LemmyNet#178 * Adjust Ansible -> ansible-core - Add `become: false` to assertion in `lemmy.yml` * Adjust README verbiage * Apparently I really want it to be 2.10.0
* chore: 1.2.1 update docs * chore: prettier * chore: prettier
Redirect "/sitemap.xml" to backend
Include CPU architectures in requirements
Fix installation playbooks running on incompatible OSs
* feat: 0.19.x * chore: upgrade pictrs to 0.4.6 * chore: upgrade pictrs to 0.4.7 * chore: readme upgrade instructions * Update README.md 1.3.1 stuff * fix: remove 1.3.1 - wrong branch * fix: remove placeholder about downtime * fix: prettier thinks this is better... * fix: add back downtime nonsense! * fix: fix command runner * fix: complete docs with estimated downtimes and ways to upgrade pictrs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/.well-known/security.txtto lemmy-ui (Send/.well-known/security.txtto lemmy-ui LemmyNet/lemmy-ansible#133)client_max_body_sizeto external NGINX config (Addclient_max_body_sizeto external NGINX config LemmyNet/lemmy-ansible#135)