- Text Content Generator - http://www.lipsum.com
- Favicon Generator - http://tools.dynamicdrive.com/favicon
- Data Generator - https://mockaroo.com/
- Mobile Mockup Generator - https://mockuphone.com
- Logo Generator - https://www.logaster.com
- UUID Generator - https://www.uuidgenerator.net/
- Hash Generator - https://passwordsgenerator.net/sha256-hash-generator/
- [Recommended] Change to your local mirror first & update your system.
Update is very important for any security patches or bug fixes.
sudo apt update && sudo apt upgrade
Optional Online accounts and setups:
While attempting to explain JavaScript's reduce
method on arrays, conceptually, I came up with the following - hopefully it's helpful; happy to tweak it if anyone has suggestions.
JavaScript Arrays have lots of built in methods on their prototype. Some of them mutate - ie, they change the underlying array in-place. Luckily, most of them do not - they instead return an entirely distinct array. Since arrays are conceptually a contiguous list of items, it helps code clarity and maintainability a lot to be able to operate on them in a "functional" way. (I'll also insist on referring to an array as a "list" - although in some languages, List
is a native data type, in JS and this post, I'm referring to the concept. Everywhere I use the word "list" you can assume I'm talking about a JS Array) This means, to perform a single operation on the list as a whole ("atomically"), and to return a new list - thus making it much simpler to think about both the old list and the new one, what they contain, and
Steps to deploy a Node.js app to Digital Ocean using PM2, NGINX as a reverse proxy and an SSL from LetsEncrypt
If you use the referal link below, you get $10 free (1 or 2 months) https://m.do.co/c/5424d440c63a
I will be using the root user, but would suggest creating a new user
#!/bin/bash | |
# | |
# Script: vmtools-4-arch-and-co.sh | |
# Date: july 31, 2013 | |
# Release: v1 - multi arch distros | |
# Author: Fnux | |
# e-mail: [email protected] | |
# Licence: CC-By-Sa | |
# | |
# Credit: WoodyZ from communities.vmware.com for his help. |
I've figured a few things out I've not seen posted anywhere so I will conclude this thread with a way that works for me. I've seen posts all over with people that gave up on almost any distro with KDE plasma in a VMWare guest.
tl;dr - switch to Wayland. I am not well versed in the merits/deficits of using Wayland but in my case it allows everything to work correctly using KDE (Kubuntu and Manjaro plasma anyway) in a VM guest.
Install the package plasma-wayland-session. Log out. At the bottom of the default log in screen, there's a menu called "Desktop Session". Select Plasma (Wayland) there and login. As a precaution, you should turn off automatic login until you verify it works correctly.
If it all works in the GUI, run Login Screen (SDDM). On the Advanced page change Auto login to reflect the Wayland session.