adamshandB
Assuming you already have a shared calendar system, just setup a shared calendar for whatever resources you need to schedule.
Super interesting, thanks!
r/lostredditors
There’s no technical problem with running a mail server on the same server as websites. The only concern is simply that web applications are much more likely to have bugs and get hacked than your mail server. If a web app does get hacked, all of your mail is potentially compromised. If you don’t care about that, I’d say … go for it.
The answer is, as always, it depends.
Some exploits allow the attacker access to the application (in which case they can do whatever the application allows them to do).
Some exploits allow the attacker to get shell access (in which case they can do anything the permissions of the user allow them to do).
Some exploits allow the attacker to get a root shell (in which case they can do almost anything).
Root exploits are much less common, and typically require much more skill, than application exploits. Getting root almost always requires exploiting an application, and then getting shell first.
This is why security people talk about “defence in depth”.
If your application is exploited, what can you do to make it as hard as possible for the attacker to get a shell. If they get a shell, what can you do to make it as hard as possible for them to get root. If they get root, what can you do to restrict the amount of damage they can do. If they do damage, how do you know what they’ve done and what can you do to repair it.
When people are relying on VPNs for security, they are building what security people refer to as the “crunchy on the outside, chewy on the inside” model. There’s no defence in depth, once the attacker is in … you’re screwed.
In a homelab, part of the fun is that we get to decide how much of this we can be bothered with. :-)
I use N8N and Airtable at work.
We used to use Make.com, and I actually like N8N more, it’s much easier to debug and see what’s happening as you build the workflow.
Airtable is irritating but also amazing.
The main advantage of both is that relatively non-technical people can do useful things. So while I’d often rather write code than use N8N, if I use N8N it means other people I work with can fix/improve it. Same with Airtable.
If you are using bind mounts with your container, there is a really easy way to backup before an update.
- stop the database container
- cp -a bind_mount_dir/ bind_mount_dir.20231019
Then pull the latest database image and restart database container. If it works, yay, you’re done.
If it doesn’t work, reverse the steps:
- stop the container
- mv bind_mount_dir/ bind_mount_dir.broken
- mv bind_mount_dir.20231019 bind_mount_dir
Restart container and you’re back to exactly where you were before the upgrade.
It’s mostly just preference. If you are already familiar with MySQL or Postgres, use what you know. If you just want simple and lightweight, use it with SQLite (no external database).
You need to make up your mind about the licensing.
README.md says:
The code in this repository is licensed under a personal, non-production source-available license. Visit https://etcha.dev/pricing/ for additional licensing options.
LICENSE.md says:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions …