...and if I'm not lazy, for Windows
Aseprite, according to Wikipedia, is a proprietary, source-available image editor designed primarily for pixel art drawing and animation.
If there is enough demand, I might make a guide for Windows as well.
...and if I'm not lazy, for Windows
Aseprite, according to Wikipedia, is a proprietary, source-available image editor designed primarily for pixel art drawing and animation.
If there is enough demand, I might make a guide for Windows as well.
Go to the following link: https://github.com/ActivityWatch/activitywatch/releases/latest
Click the Appimage file to download it.
Locate the downloaded app and put it in the following location: /home/[USERNAME]/bin/, whereas [USERNAME] is your Linux username.
Rename the Appimage file to activitywatch.
I hereby claim:
{
"body": {
"key": {Running Frappe's ERPNext using a Docker Compose .yaml file is a confusing and, for me, a frustrating endeavour.
What I hope this gist will acheive is to enlighten others as well on how to run said wonderful software in their own servers.
In this example, we will be using Portainer to run the docker compose file, and store Frappe's data in the base directory /root/data-program/frappe.
This method requires running a bit of shell script, which is risky. But the script is easily readable and is only a few short lines. Feel free to poke around though, as it is highly encouraged, for your own sake as well.
| sudo sed -i -e "s/#PermitRootLogin prohibit-password/PermitRootLogin yes/" /etc/ssh/sshd_config | |
| sudo chattr -f +i /etc/ssh/sshd_config | |
| sudo systemctl restart sshd | |
| mkdir -p /home/lyra/.config/systemd/user/ | |
| cat <<EOM >/opt/startup.sh | |
| #!/bin/sh | |
| sudo systemctl restart sshd | |
| EOM | |
| sudo chmod u+x /opt/startup.sh | |
| sudo cat <<EOM >/etc/systemd/system/startup.service |
| # Mount partitions | |
| sudo mount /dev/nvme0n1p5 /mnt | |
| sudo mount /dev/nvme0n1p1 /mnt/boot/efi | |
| # Mount virtual filesystems | |
| sudo mount -o bind /dev /mnt/dev | |
| sudo mount -o bind /proc /mnt/proc | |
| sudo mount -o bind /sys /mnt/sys | |
| sudo mount -o bind /run /mnt/run | |
| sudo mount -o bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars | |
| # chroot into system |
| echo "hello world!" |
The inevitable has come yet again. I have destroyed my system, cuz' pamac's a bitch.
This gist exist as I reinstall Arch Linux every so often, and I want an easy way to install applications and set configurations.
This init script almost do not need user interactions except for other programs that do not have an option to not prompt the user.