const groupBy = key => array =>
array.reduce((objectsByKeyValue, obj) => {
const value = obj[key];
objectsByKeyValue[value] = (objectsByKeyValue[value] || []).concat(obj);
return objectsByKeyValue;
# More info here: http://wiki.nginx.org/HttpProxyModule | |
# Source from Centos Web Panel | |
proxy_buffering off; | |
proxy_connect_timeout 59s; | |
proxy_send_timeout 600; | |
proxy_read_timeout 600; | |
proxy_buffer_size 64k; | |
proxy_buffers 16 32k; | |
proxy_busy_buffers_size 64k; |
# Service worker Yii Queue | |
# Artikel: https://dutainformasi.net/2019/05/22/implementasi-yii2-queue | |
# Guide: https://github.com/yiisoft/yii-queue/blob/master/docs/guide/worker.md | |
# Author Yusuf Ayuba | |
[Unit] | |
Description=Yii Queue Worker | |
After=network.target | |
# Enable the following two lines only apply if your queue backend is mysql | |
# replace this with the service that powers your backend |
#!/bin/bash | |
# Backup database postgres (SIAKAD AKPER Luwuk) | |
# Author Yusuf Ayuba (hello@yusufayuba.net) | |
# inisial variabel | |
tgl=$(date +'%H:%M:%S_%d-%m-%Y') | |
username=<username database> | |
dbname=<db name> | |
folderBackup=<folder temporary backup> | |
fileBackup="backup_"$tgl".sql.gz" |
# Add these three lines to CORSify your server for everyone. | |
Header set Access-Control-Allow-Origin "*" | |
Header set Access-Control-Allow-Methods "GET,PUT,POST,DELETE" | |
Header set Access-Control-Allow-Headers "Content-Type, Authorization" |
/** | |
* Marlin 3D Printer Firmware | |
* Copyright (C) 2016 MarlinFirmware [https://github.com/MarlinFirmware/Marlin] | |
* | |
* Based on Sprinter and grbl. | |
* Copyright (C) 2011 Camiel Gubbels / Erik van der Zalm | |
* | |
* This program is free software: you can redistribute it and/or modify | |
* it under the terms of the GNU General Public License as published by | |
* the Free Software Foundation, either version 3 of the License, or |
source: https://www.mysterydata.com/how-to-enable-http-2-on-cwp7-centos-web-panel/
HTTP/2 will make our applications faster, simpler, and more robust — a rare combination — by allowing us to undo many of the HTTP/1.1 workarounds previously done within our applications and address these concerns within the transport layer itself. Even better, it also opens up a number of entirely new opportunities to optimize our applications and improve performance!
[link]How to Enable IPv6 on CWP Centos WebPanel[/link]
[link]Apache HTTP to HTTPS htaccess redirect on CWP – Centos WebPanel[/link]
The primary goals for HTTP/2 are to reduce latency by enabling full request and response multiplexing, minimize protocol overhead via efficient compression of HTTP header fields, and add support for request prioritization and server push. To implement these requirements, there is a large supporting cast of other protocol enhancements, such as new flow control, error handling, and upgrade mechanisms, but these are the most importan