aka what i did to get from nothing to done.
note: these are designed to be primarily a re-install guide for myself (writing things down helps me memorize the knowledge), as such don't take any of this on blind faith - some areas are well tested and the docs are very robust, some items, less so). YMMV
| # Build & install Lua on macOS | |
| # We will compile Lua 5.1 because it is compatible with openresty/lapis. | |
| # Replace the variables from line 30 ff to install a diffrent version. | |
| # See: https://www.lua.org/manual/5.1/ | |
| # NOTE: | |
| # We create a dedicated directory for the Lua stuff to putt all the stuff in. |
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
Ubuntu 18.10 and onwards use netplan for the configuration of network interfaces. although im fine with it, it seems Cockpit and some other software dont like it as much.
Let Netplan configure the interface and hand-off further managent to NetworkManager.
notice: NetworkManager is not a X Application, although the name might sound like one.
This script can be used to backup essential configuration files from the Proxmox Virtual Enivronment (PVE) host.
The script will create backups using tar with specified backup prefix and date and time stamp in the file name. Script will also delete backups that are older then number of days specified.
To create backup script that will be executed every day we can create backup script in /etc/cron.daily/ folder. We need to make it writeable by root (creator) only, but readable and executable by everyone:
touch /etc/cron.daily/pvehost-backup
Server-side Blazor is a stateful application framework. Most of the time, your users will maintain an ongoing connection to the server, and their state will be held in the server's memory in what's known as a "circuit". Examples of state held for a user's circuit include:
Occasionally, users may experience a temporary network connection loss, after which Blazor will attempt to reconnect them to their original circuit so they can continue.
| #!/bin/bash | |
| # Simple motd script for any systemd Linux (tested on Debian) | |
| # Inspiration: https://superuser.com/questions/919962/landscape-sysinfo-for-centos | |
| # Inspiration 2: https://github.com/thusoy/headsup/blob/master/headsup.py | |
| os-name=$() | |
| os-kernel=$() | |
| date-today=$() | |
| system-load=$() | |
| processes=$(cat /proc/loadavg | cut -d"/" -f2| cut -d" " -f1) |
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
A DMG Installer is convenient way to provide end-users a simple way to install an application bundle. They are basically a folder with a shortcut to the Applications directory but they can be customized with icons, backgrounds, and layout properties. A DMG file (.dmg) is a Mac OS X Disk Image file and it is used to package files or folders providing compression, encryption, and read-only to the package.
##Creating the DMG file #Disk Utility
| # encoding: utf-8 | |
| # FastCGI-to-WSGI bridge for files/pipes transport (not socket) | |
| # | |
| # Copyright (c) 2002, 2003, 2005, 2006 Allan Saddi <[email protected]> | |
| # Copyright (c) 2011 Ruslan Keba <[email protected]> | |
| # Copyright (c) 2012 Antoine Martin <[email protected]> | |
| # All rights reserved. | |
| # | |
| # Redistribution and use in source and binary forms, with or without |