https://wiki.its-treason.com/api.php?action=feedcontributions&feedformat=atom&user=TimonTimon's Wiki - User contributions [en]2026-06-12T14:05:21ZUser contributionsMediaWiki 1.44.0https://wiki.its-treason.com/index.php?title=Death_Stranding&diff=76Death Stranding2025-10-05T15:57:57Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Gratitude'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High-Density: 400)<br />
|-<br />
|'''The Elder'''<br />
|<br />
|<br />
|Resins (High-Density: 320)<br />
|-<br />
|'''Timefall Farm'''<br />
|<br />
|<br />
|Resins (Lightweight: 800)<br />
|-<br />
|'''Weather Station'''<br />
|<br />
|<br />
|Metals (Lightweight: 1000)<br />
|-<br />
|'''Junk Dealer'''<br />
|<br />
|<br />
|Custom Chiral Ladder<br />
|-<br />
|'''Chiral Artist's Studio'''<br />
|<br />
|<br />
|Chiral Boots<br />
|-<br />
|'''Craftsman'''<br />
|<br />
|<br />
|Custom Hemantic Grenate<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|'''Zip-Line'''<br />
|<br />
|<br />
* 240 Chemicals<br />
* 480 Special Alloys<br />
|<br />
* 300 Chiral Crystals<br />
* 1440 Chemicals<br />
* 1440 Special Alloys<br />
|-<br />
|Timefall Shelter<br />
|<br />
|<br />
* 32 Chiral Crystal<br />
* 400 Metal<br />
|<br />
|}<br />
<br />
== Memory Chips ==<br />
{| class="wikitable"<br />
|+<br />
!#<br />
!Tip<br />
|-<br />
|4<br />
|On the foundation of the white ball shaped building near the weather station.<br />
|-<br />
|5<br />
|In a small cave left of Mama's lab (Under the highway sign).<br />
|-<br />
|6<br />
|On the hood of a truck at the Distribution Center Noth of Mountain Knot City.<br />
|-<br />
|9<br />
|Near the beach lying on some rubble.<br />
|-<br />
|11<br />
|Inside a small cave slightly above the most nothern river.<br />
|-<br />
|17<br />
|On a rock next to the big cryptobiotes nest.<br />
|-<br />
|19<br />
|On the west pillar of the broken Bridge.<br />
|-<br />
|21<br />
|Inside the big Mule tent.<br />
|-<br />
|23<br />
|Inside the small Tent in the East of the Mule Camp.<br />
|-<br />
|24<br />
|On top the Timefall farmer House. Can easly be climbed from the back.<br />
|-<br />
|28<br />
|Lying on a elevated position at east of the Tower. Ladder or Gravity gloves needed for pickup.<br />
|-<br />
|31<br />
|At the bottom of the hill, inside a small cave.<br />
|-<br />
|33<br />
|Inside the broken down Barn, in a shelf on the Catwalk.<br />
|-<br />
|46<br />
|Lying on the ground right next to a big black rock.<br />
|-<br />
|48<br />
|At the bottom of the vog gas filled ravine. TODO: Strat<br />
|-<br />
|51<br />
|On top of the Mountain, under the Torii.<br />
|-<br />
|55<br />
|Under the Highway cossing next to a rusted pickup truck.<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Abcde&diff=75Abcde2025-05-28T15:04:54Z<p>Timon: </p>
<hr />
<div>{{DISPLAYTITLE:abcde}}<br />
<br />
'''abcde''' ('''a''' '''b'''etter '''CD''' '''e'''ncoder) is a Linux terminal program for ripping CD's. It can automagically search for Music Metadata and encode the Music in various different formats.<br />
<br />
=== Install (Debian) ===<br />
abcde is available in the official Repository. The <code>--no-install-recommends</code> should be used, because x11 will otherwise be installed.<br />
<br />
A package for the target codec should also be installed<br />
<br />
* <code>vorbis-tools</code> for OGG. This is the default.<br />
* <code>flac</code> for FLAC files.<br />
* <code>lame</code> for MP3 files.<br />
<syntaxhighlight lang="shell"><br />
apt install abcde flac --no-install-recommends<br />
</syntaxhighlight><br />
<br />
=== Usage ===<br />
<br />
==== Config ====<br />
The config file for abcde is located under <code>~/.abcde.conf</code>.<br />
<br />
Example Config for FLAC. Extracted music will be used under <code>~/Music</code> grouped by Album name.<syntaxhighlight><br />
OUTPUTTYPE=flac<br />
OUTPUTFORMAT='./Music/${ALBUMFILE}/${ARTISTFILE} - ${TRACKFILE}'<br />
VAOUTPUTFORMAT='./Music/${ALBUMFILE}/${ARTISTFILE} - ${TRACKFILE}'<br />
FLACOPTS='-8'<br />
PADTRACKS=y<br />
<br />
# Eject CD after reading is complete<br />
EJECTCD=y<br />
</syntaxhighlight><br />
<br />
==== Ripping CD's ====<br />
After the config file is created <code>abcde</code> can be executed and will automatically start ripping the currently inserted Disk. abcde uses "CD Paranoia" to extract the Music and displaying the progress bar. You can see here: https://www.xiph.org/paranoia/faq.html#progbar what the different symbols mean.<br />
<br />
The <code>-N</code> can be used to make the process non-interactive, abcde will always use the first option for Metadata information.<br />
<br />
==== Moving "cover.jpg" back into the extraction folder ====<br />
If abcde found a Cover to the CD online, it will apply it to all extracted Tracks and will then create an "albumart_backup" folder inside the target folder. For Jellyfin and other Applications, it is useful to have the cover inside the target folder directly. This can be fixed with a script.<syntaxhighlight lang="bash"><br />
#!/bin/bash<br />
<br />
# Set the base directory where your music albums are stored<br />
MUSIC_DIR="./Music"<br />
<br />
# Find all albumart_backup directories<br />
find "$MUSIC_DIR" -type d -name "albumart_backup" | while read -r backup_dir; do<br />
# Get the parent album directory<br />
album_dir=$(dirname "$backup_dir")<br />
<br />
# Check if cover.jpg exists in the backup directory<br />
if [ -f "$backup_dir/cover.jpg" ]; then<br />
echo "Moving cover from $backup_dir to $album_dir"<br />
<br />
# Move the cover.jpg to the album directory<br />
mv "$backup_dir/cover.jpg" "$album_dir/"<br />
<br />
# Check if the move was successful<br />
if [ $? -eq 0 ]; then<br />
echo "Successfully moved cover.jpg to $album_dir"<br />
<br />
# Remove the now-empty albumart_backup directory<br />
rm -rf "$backup_dir"<br />
echo "Removed $backup_dir"<br />
else<br />
echo "Failed to move cover.jpg from $backup_dir to $album_dir"<br />
fi<br />
else<br />
echo "No cover.jpg found in $backup_dir"<br />
# Remove the directory anyway if it's empty or doesn't have cover.jpg<br />
rm -rf "$backup_dir"<br />
echo "Removed $backup_dir"<br />
fi<br />
<br />
echo "-----------------------------------"<br />
done<br />
<br />
echo "All album art processing completed."<br />
</syntaxhighlight>{{DEFAULTSORT:abcde}}<br />
[[Category:Linux]]</div>Timonhttps://wiki.its-treason.com/index.php?title=Abcde&diff=73Abcde2025-05-28T14:54:23Z<p>Timon: Created page with "{{DISPLAYTITLE:abcde}} '''abcde''' ('''a''' '''b'''etter '''CD''' '''e'''ncoder) is a Linux terminal program for ripping CD's. It can automagically search for Music Metadata and encode the Music in various different formats. === Install (Debian) === abcde is available in the official Repository. The <code>--no-install-recommends</code> should be used, because x11 will otherwise be installed. A package for the target codec should also be installed * <code>vorbis-tools..."</p>
<hr />
<div>{{DISPLAYTITLE:abcde}}<br />
<br />
'''abcde''' ('''a''' '''b'''etter '''CD''' '''e'''ncoder) is a Linux terminal program for ripping CD's. It can automagically search for Music Metadata and encode the Music in various different formats.<br />
<br />
=== Install (Debian) ===<br />
abcde is available in the official Repository. The <code>--no-install-recommends</code> should be used, because x11 will otherwise be installed.<br />
<br />
A package for the target codec should also be installed<br />
<br />
* <code>vorbis-tools</code> for OGG. This is the default.<br />
* <code>flac</code> for FLAC files.<br />
* <code>lame</code> for MP3 files.<br />
<syntaxhighlight lang="shell"><br />
apt install abcde flac --no-install-recommends<br />
</syntaxhighlight><br />
<br />
=== Usage ===<br />
<br />
==== Config ====<br />
The config file for abcde is located under <code>~/.abcde.conf</code>.<br />
<br />
Example Config for FLAC. Extracted music will be used under <code>~/Music</code> grouped by Album name.<syntaxhighlight><br />
OUTPUTTYPE=flac<br />
OUTPUTFORMAT='./Music/${ALBUMFILE}/${ARTISTFILE} - ${TRACKFILE}'<br />
VAOUTPUTFORMAT='./Music/${ALBUMFILE}/${ARTISTFILE} - ${TRACKFILE}'<br />
FLACOPTS='-8'<br />
PADTRACKS=y<br />
</syntaxhighlight><br />
<br />
==== Ripping CD's ====<br />
After the config file is created <code>abcde</code> can be executed and will automatically start ripping the currently inserted Disk. abcde uses "CD Paranoia" to extract the Music and displaying the progress bar. You can see here: https://www.xiph.org/paranoia/faq.html#progbar what the different symbols mean.<br />
<br />
==== Moving "cover.jpg" back into the extraction folder ====<br />
If abcde found a Cover to the CD online, it will apply it to all extracted Tracks and will then create an "albumart_backup" folder inside the target folder. For Jellyfin and other Applications, it is useful to have the cover inside the target folder directly. This can be fixed with a script.<syntaxhighlight lang="bash"><br />
#!/bin/bash<br />
<br />
# Set the base directory where your music albums are stored<br />
MUSIC_DIR="./Music"<br />
<br />
# Find all albumart_backup directories<br />
find "$MUSIC_DIR" -type d -name "albumart_backup" | while read -r backup_dir; do<br />
# Get the parent album directory<br />
album_dir=$(dirname "$backup_dir")<br />
<br />
# Check if cover.jpg exists in the backup directory<br />
if [ -f "$backup_dir/cover.jpg" ]; then<br />
echo "Moving cover from $backup_dir to $album_dir"<br />
<br />
# Move the cover.jpg to the album directory<br />
mv "$backup_dir/cover.jpg" "$album_dir/"<br />
<br />
# Check if the move was successful<br />
if [ $? -eq 0 ]; then<br />
echo "Successfully moved cover.jpg to $album_dir"<br />
<br />
# Remove the now-empty albumart_backup directory<br />
rm -rf "$backup_dir"<br />
echo "Removed $backup_dir"<br />
else<br />
echo "Failed to move cover.jpg from $backup_dir to $album_dir"<br />
fi<br />
else<br />
echo "No cover.jpg found in $backup_dir"<br />
# Remove the directory anyway if it's empty or doesn't have cover.jpg<br />
rm -rf "$backup_dir"<br />
echo "Removed $backup_dir"<br />
fi<br />
<br />
echo "-----------------------------------"<br />
done<br />
<br />
echo "All album art processing completed."<br />
</syntaxhighlight>{{DEFAULTSORT:abcde}}<br />
[[Category:Linux]]</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=72Death Stranding2025-05-11T02:49:29Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Gratitude'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High-Density: 400)<br />
|-<br />
|'''The Elder'''<br />
|<br />
|<br />
|Resins (High-Density: 320)<br />
|-<br />
|'''Timefall Farm'''<br />
|<br />
|<br />
|Resins (Lightweight: 800)<br />
|-<br />
|'''Weather Station'''<br />
|<br />
|<br />
|Metals (Lightweight: 1000)<br />
|-<br />
|'''Junk Dealer'''<br />
|<br />
|<br />
|Custom Chiral Ladder<br />
|-<br />
|'''Chiral Artist's Studio'''<br />
|<br />
|<br />
|Chiral Boots<br />
|-<br />
|'''Craftsman'''<br />
|<br />
|<br />
|Custom Hemantic Grenate<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|'''Zip-Line'''<br />
|<br />
|<br />
* 240 Chemicals<br />
* 480 Special Alloys<br />
|<br />
* 300 Chiral Crystals<br />
* 1440 Chemicals<br />
* 1440 Special Alloys<br />
|-<br />
|Timefall Shelter<br />
|<br />
|<br />
* 32 Chiral Crystal<br />
* 400 Metal<br />
|<br />
|}<br />
<br />
== Memory Chips ==<br />
<br />
=== Central Region ===<br />
{| class="wikitable"<br />
|+<br />
!#<br />
!Tip<br />
|-<br />
|4<br />
|On the foundation of the white ball shaped building near the weather station.<br />
|-<br />
|5<br />
|In a small cave left of Mama's lab (Under the highway sign).<br />
|-<br />
|9<br />
|Near the beach lying on some rubble.<br />
|-<br />
|11<br />
|Inside a small cave slightly above the most nothern river.<br />
|-<br />
|17<br />
|On a rock next to the big cryptobiotes nest.<br />
|-<br />
|19<br />
|On the west pillar of the broken Bridge.<br />
|-<br />
|21<br />
|Inside the big Mule tent.<br />
|-<br />
|23<br />
|Inside the small Tent in the East of the Mule Camp.<br />
|-<br />
|24<br />
|On top the Timefall farmer House. Can easly be climbed from the back.<br />
|-<br />
|28<br />
|Lying on a elevated position at east of the Tower. Ladder or Gravity gloves needed for pickup.<br />
|-<br />
|31<br />
|At the bottom of the hill, inside a small cave.<br />
|-<br />
|33<br />
|Inside the broken down Barn. Inside a shelf on the Catwalk.<br />
|-<br />
|46<br />
|Lying on the ground right next to a big black rock.<br />
|-<br />
|48<br />
|At the bottom of the vog gas filled ravine. TODO: Strat<br />
|-<br />
|51<br />
|On top of the Mountain, under the Torii.<br />
|-<br />
|55<br />
|Under the Highway cossing next to a rusted pickup truck.<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=71Death Stranding2025-04-27T22:42:41Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Gratitude'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High-Density: 400)<br />
|-<br />
|'''The Elder'''<br />
|<br />
|<br />
|Resins (High-Density: 320)<br />
|-<br />
|'''Timefall Farm'''<br />
|<br />
|<br />
|Resins (Lightweight: 800)<br />
|-<br />
|'''Weather Station'''<br />
|<br />
|<br />
|Metals (Lightweight: 1000)<br />
|-<br />
|'''Junk Dealer'''<br />
|<br />
|<br />
|Custom Chiral Ladder<br />
|-<br />
|'''Chiral Artist's Studio'''<br />
|<br />
|<br />
|Chiral Boots<br />
|-<br />
|'''Craftsman'''<br />
|<br />
|<br />
|Custom Hemantic Grenate<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|'''Zip-Line'''<br />
|<br />
|<br />
* 240 Chemicals<br />
* 480 Special Alloys<br />
|<br />
* 300 Chiral Crystals<br />
* 1440 Chemicals<br />
* 1440 Special Alloys<br />
|-<br />
|Timefall Shelter<br />
|<br />
|<br />
* 32 Chiral Crystal<br />
* 400 Metal<br />
|<br />
|}<br />
<br />
== Memory Chips ==<br />
<br />
=== Central Region ===<br />
{| class="wikitable"<br />
|+<br />
!#<br />
!Tip<br />
|-<br />
|4<br />
|On the foundation of the white ball shaped building near the weather station.<br />
|-<br />
|5<br />
|In a small cave left of Mama's lab (Under the highway sign).<br />
|-<br />
|9<br />
|Near the beach lying on some rubble.<br />
|-<br />
|19<br />
|On the west pillar of the broken Bridge.<br />
|-<br />
|23<br />
|Inside the small Tent in the East of the Mule Camp.<br />
|-<br />
|24<br />
|On top the Timefall farmer House. Can easly be climbed from the back.<br />
|-<br />
|28<br />
|Lying on a elevated position at east of the Tower. Ladder or Gravity gloves needed for pickup.<br />
|-<br />
|31<br />
|At the bottom of the hill, inside a small cave.<br />
|-<br />
|33<br />
|Inside the broken down Barn. Inside a shelf on the Catwalk.<br />
|-<br />
|46<br />
|Lying on the ground right next to a big black rock.<br />
|-<br />
|51<br />
|On top of the Mountain, under the Torii.<br />
|-<br />
|55<br />
|Under the Highway cossing next to a rusted pickup truck.<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=70Death Stranding2025-04-27T21:42:49Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Gratitude'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High-Density: 400)<br />
|-<br />
|'''The Elder'''<br />
|<br />
|<br />
|Resins (High-Density: 320)<br />
|-<br />
|'''Timefall Farm'''<br />
|<br />
|<br />
|Resins (Lightweight: 800)<br />
|-<br />
|'''Weather Station'''<br />
|<br />
|<br />
|Metals (Lightweight: 1000)<br />
|-<br />
|'''Junk Dealer'''<br />
|<br />
|<br />
|Custom Chiral Ladder<br />
|-<br />
|'''Chiral Artist's Studio'''<br />
|<br />
|<br />
|Chiral Boots<br />
|-<br />
|'''Craftsman'''<br />
|<br />
|<br />
|Custom Hemantic Grenate<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|'''Zip-Line'''<br />
|<br />
|<br />
* 240 Chemicals<br />
* 480 Special Alloys<br />
|<br />
* 300 Chiral Crystals<br />
* 1440 Chemicals<br />
* 1440 Special Alloys<br />
|-<br />
|Timefall Shelter<br />
|<br />
|<br />
* 32 Chiral Crystal<br />
* 400 Metal<br />
|<br />
|}<br />
<br />
== Memory Chips ==<br />
<br />
=== Central Region ===<br />
{| class="wikitable"<br />
|+<br />
!#<br />
!Tip<br />
|-<br />
|4<br />
|On the foundation of the white ball shaped building near the weather station.<br />
|-<br />
|19<br />
|On the west pillar of the broken Bridge.<br />
|-<br />
|23<br />
|Inside the small Tent in the East of the Mule Camp.<br />
|-<br />
|24<br />
|On top the Timefall farmer House. Can easly be climbed from the back.<br />
|-<br />
|31<br />
|At the bottom of the hill, inside a small cave.<br />
|-<br />
|33<br />
|Inside the broken down Barn. Inside a shelf on the Catwalk.<br />
|-<br />
|46<br />
|Lying on the ground right next to a big black rock.<br />
|-<br />
|51<br />
|On top of the Mountain, under the Torii.<br />
|-<br />
|<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=69Death Stranding2025-04-27T20:55:00Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Gratitude'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High-Density: 400)<br />
|-<br />
|'''The Elder'''<br />
|<br />
|<br />
|Resins (High-Density: 320)<br />
|-<br />
|'''Timefall Farm'''<br />
|<br />
|<br />
|Resins (Lightweight: 800)<br />
|-<br />
|'''Weather Station'''<br />
|<br />
|<br />
|Metals (Lightweight: 1000)<br />
|-<br />
|'''Junk Dealer'''<br />
|<br />
|<br />
|Custom Chiral Ladder<br />
|-<br />
|'''Chiral Artist's Studio'''<br />
|<br />
|<br />
|Chiral Boots<br />
|-<br />
|'''Craftsman'''<br />
|<br />
|<br />
|Custom Hemantic Grenate<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|'''Zip-Line'''<br />
|<br />
|<br />
* 240 Chemicals<br />
* 480 Special Alloys<br />
|<br />
* 300 Chiral Crystals<br />
* 1440 Chemicals<br />
* 1440 Special Alloys<br />
|-<br />
|Timefall Shelter<br />
|<br />
|<br />
* 32 Chiral Crystal<br />
* 400 Metal<br />
|<br />
|}<br />
<br />
== Data Chips ==<br />
<br />
=== Central Region ===<br />
{| class="wikitable"<br />
|+<br />
!#<br />
!Tip<br />
|-<br />
|23<br />
|Inside the small Tent in the East of the Mule Camp.<br />
|-<br />
|24<br />
|On top the Timefall farmer House. Can easly be climbed from the back.<br />
|-<br />
|33<br />
|Inside the broken down Barn. Inside a shelf on the Catwalk.<br />
|-<br />
|51<br />
|On top of the Mountain, under the Torii.<br />
|-<br />
|<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=68Death Stranding2025-04-27T02:19:20Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Gratitude'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High-Density: 400)<br />
|-<br />
|'''The Elder'''<br />
|<br />
|<br />
|Resins (High-Density: 320)<br />
|-<br />
|'''Timefall Farm'''<br />
|<br />
|<br />
|Resins (Lightweight: 800)<br />
|-<br />
|'''Weather Station'''<br />
|<br />
|<br />
|Metals (Lightweight: 1000)<br />
|-<br />
|'''Junk Dealer'''<br />
|<br />
|<br />
|Custom Chiral Ladder<br />
|-<br />
|'''Chiral Artist's Studio'''<br />
|<br />
|<br />
|Chiral Boots<br />
|-<br />
|'''Craftsman'''<br />
|<br />
|<br />
|Custom Hemantic Grenate<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|'''Zip-Line'''<br />
|<br />
|<br />
* 240 Chemicals<br />
* 480 Special Alloys<br />
|<br />
* 300 Chiral Crystals<br />
* 1440 Chemicals<br />
* 1440 Special Alloys<br />
|-<br />
|Timefall Shelter<br />
|<br />
|<br />
* 32 Chiral Crystal<br />
* 400 Metal<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=67Death Stranding2025-04-26T20:53:31Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Gratitude'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High-Density: 400)<br />
|-<br />
|'''The Elder'''<br />
|<br />
|<br />
|Resins (High-Density: 320)<br />
|-<br />
|'''Timefall Farm'''<br />
|<br />
|<br />
|Resins (Lightweight: 800)<br />
|-<br />
|'''Weather Station'''<br />
|<br />
|<br />
|Metals (Lightweight: 1000)<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|'''Zip-Line'''<br />
|<br />
|<br />
* 240 Chemicals<br />
* 480 Special Alloys<br />
|<br />
* 300 Chiral Crystals<br />
* 1440 Chemicals<br />
* 1440 Special Alloys<br />
|-<br />
|Timefall Shelter<br />
|<br />
|<br />
* 32 Chiral Crystal<br />
* 400 Metal<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=66Death Stranding2025-04-26T15:23:25Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Gratitude'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High-Density: 400)<br />
|-<br />
|'''The Elder'''<br />
|<br />
|<br />
|Resins (High-Density: 320)<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|'''Zip-Line'''<br />
|<br />
|<br />
* 240 Chemicals<br />
* 480 Special Alloys<br />
|<br />
* 300 Chiral Crystals<br />
* 1440 Chemicals<br />
* 1440 Special Alloys<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=65Death Stranding2025-04-26T14:58:17Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Gratitude'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High-Density: 400)<br />
|-<br />
|'''The Elder'''<br />
|<br />
|<br />
|Resins (High-Density: 320)<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=64Death Stranding2025-04-26T14:47:55Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Appreciation'''<br />
|-<br />
|'''Film Director'''<br />
|<br />
|<br />
|Metals (High Density: 400)<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|'''Generator'''<br />
|<br />
|<br />
* 400 Metals<br />
|<br />
* 400 Metals<br />
* 100 Chiral Crystals<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=63Death Stranding2025-04-26T14:46:45Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Appreciation'''<br />
|-<br />
|Film Director<br />
|<br />
|<br />
|Metals (High Density: 400)<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Structures ==<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Level 1<br />
!Level 2<br />
!Level 3<br />
|-<br />
|Generator<br />
|<br />
|400 Metals<br />
|400 Metals<br />
100 Chiral Crystals<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=62Death Stranding2025-04-26T14:19:14Z<p>Timon: </p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Appreciation'''<br />
|-<br />
|Film Director<br />
|<br />
|<br />
|Metals (High Density: 400)<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Death_Stranding&diff=61Death Stranding2025-04-26T14:14:01Z<p>Timon: Created page with "== Prepper Rewards == {| class="wikitable" !Prepper !Initial !Ranks !'''Token of Appreciation''' |- |Film Director | | |Metals (Hight Density: 400) |- | | | | |- | | | | |}"</p>
<hr />
<div>== Prepper Rewards ==<br />
{| class="wikitable"<br />
!Prepper<br />
!Initial<br />
!Ranks<br />
!'''Token of Appreciation'''<br />
|-<br />
|Film Director<br />
|<br />
|<br />
|Metals (Hight Density: 400)<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Main_Page&diff=60Main Page2025-04-06T11:51:29Z<p>Timon: </p>
<hr />
<div>My Personal Wiki<br />
<br />
[[Special:Categories]]<br />
<br />
[[Special:AllPages]]</div>Timonhttps://wiki.its-treason.com/index.php?title=Main_Page&diff=59Main Page2025-02-23T14:22:51Z<p>Timon: </p>
<hr />
<div>My Personal Wiki<br />
<br />
[[Special:Categories|Categories]]<br />
<br />
[[Special:AllPages]]</div>Timonhttps://wiki.its-treason.com/index.php?title=Docker&diff=58Docker2025-01-02T12:38:07Z<p>Timon: </p>
<hr />
<div>== Multi-arch Build ==<br />
<br />
=== Builder Setup ===<br />
Install QEMOU to allow emulation of different arches. Using emulation is not the most efficient way to build an image. See [https://docs.docker.com/build/building/multi-platform/#qemu Docker docs] for more other ways.<syntaxhighlight lang="shell"><br />
docker run --privileged --rm tonistiigi/binfmt --install all<br />
</syntaxhighlight>Creating the new builder:<syntaxhighlight lang="shell"><br />
docker buildx create --name <Name> --bootstrap --use<br />
</syntaxhighlight>Replace <code><Name></code> with a different name. The Flag <code>--use</code> will automaticity select the builder as default. Running <code>docker buildx ls</code> should show your new builder, with available platforms.<br />
<br />
=== Building an Image ===<br />
Edit your Dockerfile to select the arch depending on the build argument.<syntaxhighlight lang="diff"><br />
- FROM alpine:latest<br />
+ ARG ARCH=<br />
+ FROM ${ARCH}alpine:latest<br />
</syntaxhighlight>Now you can build your image using<syntaxhighlight lang="shell"><br />
docker buildx build --push --platform linux/arm64/v8,linux/amd64/v3 --tag OWNER/IMAGE:VERSION .<br />
</syntaxhighlight>This will build the image in the current directory for arm64 & amd64 and push it into the registry to <code>OWNER/IMAGE:VERSION</code>.</div>Timonhttps://wiki.its-treason.com/index.php?title=Docker&diff=57Docker2024-10-27T17:19:28Z<p>Timon: </p>
<hr />
<div>== Multi-arch Build ==<br />
<br />
=== Builder Setup ===<br />
Install QEMOU to allow emulation of different arches. Using emulation is not the most efficient way to build an image. See [https://docs.docker.com/build/building/multi-platform/#qemu Docker docs] for more other ways.<syntaxhighlight lang="shell"><br />
docker run --privileged --rm tonistiigi/binfmt --install all<br />
</syntaxhighlight>Creating the new builder:<syntaxhighlight lang="shell"><br />
docker buildx create --name <Name> --bootstrap --use<br />
</syntaxhighlight>Replace <code><Name></code> with a different name. The Flag <code>--use</code> will automaticity select the builder as default. Running <code>docker buildx ls</code> should show your new builder with all kind of platforms available.<br />
<br />
=== Building an Image ===<br />
Edit your Dockerfile to select the arch depending on the build argument.<syntaxhighlight lang="diff"><br />
- FROM alpine:latest<br />
+ ARG ARCH=<br />
+ FROM ${ARCH}alpine:latest<br />
</syntaxhighlight>Now you can build your image using<syntaxhighlight lang="shell"><br />
docker buildx build --push --platform linux/arm64/v8,linux/amd64/v3 --tag OWNER/IMAGE:VERSION .<br />
</syntaxhighlight>This will build the image in the current directory for arm64 & amd64 and push it into the registry to <code>OWNER/IMAGE:VERSION</code>.</div>Timonhttps://wiki.its-treason.com/index.php?title=Main_Page&diff=56Main Page2024-07-21T14:13:03Z<p>Timon: </p>
<hr />
<div>My Personal Wiki.<br />
<br />
[[Special:Categories|Categories]]<br />
<br />
[[Special:AllPages]]</div>Timonhttps://wiki.its-treason.com/index.php?title=Main_Page&diff=55Main Page2024-07-21T14:12:56Z<p>Timon: </p>
<hr />
<div>My Personal Wiki. Test<br />
<br />
[[Special:Categories|Categories]]<br />
<br />
[[Special:AllPages]]</div>Timonhttps://wiki.its-treason.com/index.php?title=Fstab&diff=54Fstab2024-05-07T09:50:48Z<p>Timon: </p>
<hr />
<div>== Structure ==<br />
Values are separated by one or more spaces.<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Value<br />
|-<br />
|Filesystem<br />
|The Filesystem / Partition to be mounted. <br />
Can be a the path to a partition e.g. <code>/dev/sdb2</code> or a UUID e.g. <code>PARTUUID=65561b67-2aee-4c48-8a67-2ea71f5f4ba</code><br />
|-<br />
|Mount Point<br />
|Path to the mountpoint. Should be an existing empty folder. Value <code>none</code> can be used for Swap-Partitions<br />
|-<br />
|FS-Type<br />
|Type of the file system e.g <code>ext4</code> or <code>ntfs</code><br />
|-<br />
|Options<br />
|Mounting options. e.g. <code>defaults,nofail</code> -> Default settings, allow booting when mounting the partition fails<br />
|-<br />
|Dump<br />
|Weather to create a Dump before mounting. <code>0</code> don't create dump. <code>1</code> create dump<br />
|-<br />
|Check Fsck<br />
|Check file system before mounting them. <code>0</code> don't check anything should be used for Windows / NTFS Partitions. <code>1</code> For root file system (Except if type is <code>btfs</code>or <code>XFS</code>). <code>2</code> Check the filesystem before mounting.<br />
|}<br />
Example <code>fstab</code> file:<syntaxhighlight lang="text"><br />
# This is the default fstab of a rpi with an external harddrive<br />
proc /proc proc defaults 0 0<br />
PARTUUID=0a70b801-01 /boot vfat defaults,flush 0 2<br />
PARTUUID=0a70b801-02 / ext4 defaults,noatime 0 1<br />
# a swapfile is not a swap partition, no line here<br />
# use dphys-swapfile swap[on|off] for that<br />
<br />
PARTUUID=6b8fd307-ae27-4222-b81c-926eaa800dbc /data ext4 defaults,nofail 0 2<br />
<br />
</syntaxhighlight><br />
<br />
== Options ==<br />
For all list of all options, see: [https://man.archlinux.org/man/ext4.5#MOUNT_OPTIONS Ext file system options] and [https://man.archlinux.org/man/mount.8#FILESYSTEM-INDEPENDENT_MOUNT_OPTIONS File system independent Options]. Note that changing owner or permissions is only really needed for file system that don't support UNIX permissions, e.g <code>NTFS</code>. <code>ext4</code> and others will save all permissions.<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Description<br />
|-<br />
|defaults<br />
|Commen Default settings. These include: <code>rw</code>,<code>suid</code>,<code>dev</code>,<code>exec</code>,<code>auto</code>,<code>nouser</code>,<code>async</code>,<code>realtime</code><br />
|-<br />
|ro<br />
|Mount the file system in readonly mode<br />
|-<br />
|rw<br />
|Mount the file system in Read-Write mode (In defaults)<br />
|-<br />
|nofail<br />
|Skip the file system if it can't be found. Very usefull for thumb-drives. If this options is not set, the system will wait for the filesystem to be connected before booting<br />
|-<br />
|umask=PERMS<br />
|Set the Permissions for all files and directories. Important: This is a umask so its disallows permissions e.g. <code>000</code> becomes <code>777</code>, <code>022</code>becomes<code>755</code>.<br />
|-<br />
|uid=UID<br />
|Set the owner of all files. Can be the users UID or username.<br />
|-<br />
|gid=GID<br />
|Set the owner group of all files. Can be the groups GID or groupname.<br />
|-<br />
|windows_names<br />
|Only for NTFS: Prevent the creating of files with characters that are not allowed within Windows e.g. <code><nowiki>" * < > / | \</nowiki></code> and some <br />
|}<br />
<br />
== Determine file system types and UUID ==<br />
To list all partitions with their UUID execute:<syntaxhighlight lang="shell"><br />
sudo blkid -s UUID<br />
</syntaxhighlight><br />
<br />
== Validating fstab ==<br />
Executing <code>mount -fav</code> will try to mount all file systems without actually making a system call. <br />
<br />
* <code>-a</code> Try to auto mount everything inside <code>fstab</code>.<br />
* <code>-f</code> Fake, don't make any system calls. <br />
* <code>-v</code> Verbose print more debug output.<br />
<br />
Alternative <code>findmnt --verify --verbose</code> can print nice information and detailed error messages.<br />
<br />
Output without any errors:<syntaxhighlight lang="text"><br />
# findmnt --verify --verbose<br />
/proc<br />
[ ] target exists<br />
[ ] do not check proc source (pseudo/net)<br />
[ ] do not check proc FS type (pseudo/net)<br />
/boot<br />
[ ] target exists<br />
[ ] FS options: flush<br />
[ ] PARTUUID=0a70b801-01 translated to /dev/mmcblk0p1<br />
[ ] source /dev/mmcblk0p1 exists<br />
[ ] FS type is vfat<br />
/<br />
[ ] target exists<br />
[ ] VFS options: noatime<br />
[ ] PARTUUID=0a70b801-02 translated to /dev/mmcblk0p2<br />
[ ] source /dev/mmcblk0p2 exists<br />
[ ] FS type is ext4<br />
/data<br />
[ ] target exists<br />
[ ] userspace options: nofail<br />
[ ] PARTUUID=6b8fd307-ae27-4222-b81c-926eaa800dbc translated to /dev/sda1<br />
[ ] source /dev/sda1 exists<br />
[ ] FS type is ext4<br />
Success, no errors or warnings detected<br />
</syntaxhighlight>Output with wrong <code>PARTUUID</code> value:<syntaxhighlight lang="text"><br />
# findmnt --verify --verbose<br />
/proc<br />
[ ] target exists<br />
...<br />
[ ] source /dev/mmcblk0p2 exists<br />
[ ] FS type is ext4<br />
/data<br />
[ ] target exists<br />
[ ] userspace options: nofail<br />
[E] unreachable on boot required source: PARTUUID=6b8fd307-ae27-4222-b81c-926eaa800db<br />
<br />
0 parse errors, 1 error, 0 warnings<br />
</syntaxhighlight></div>Timonhttps://wiki.its-treason.com/index.php?title=Docker&diff=53Docker2024-01-24T00:22:51Z<p>Timon: </p>
<hr />
<div>== Multi-arch Build ==<br />
<br />
=== Builder Setup ===<br />
Install QEMOU to allow emulation of different arches. Using emulation is not the most efficient way to build an image. See [https://docs.docker.com/build/building/multi-platform/#qemu Docker docs] for more other ways.<syntaxhighlight lang="shell"><br />
docker run --privileged --rm tonistiigi/binfmt --install all<br />
</syntaxhighlight>Creating the new builder:<syntaxhighlight lang="shell"><br />
docker buildx create --name <Name> --bootstrap --use<br />
</syntaxhighlight>Replace <code><Name></code> with a different name. The Flag <code>--use</code> will automaticity select the builder as default. Running <code>docker buildx ls</code> should show your new builder with all kind of platforms available.<br />
<br />
=== Building an Image ===<br />
Edit your Dockerfile to select the arch depending on the build argument.<syntaxhighlight lang="diff"><br />
- FROM alpine:latest<br />
+ ARG ARCH=<br />
+ FROM ${ARCH}alpine:latest<br />
</syntaxhighlight>Now you can build your image using<syntaxhighlight lang="shell"><br />
docker buildx build --push --platform linux/arm64/v8,linux/amd64/v3 --tag OWNER/IMAGE:VERSION .<br />
</syntaxhighlight>This will build the image in the current directory for arm64 & amd64 and push it into the registry to <code>OWNER/IMAGE:VERSION</code>.</div>Timonhttps://wiki.its-treason.com/index.php?title=Mise&diff=52Mise2024-01-24T00:19:11Z<p>Timon: </p>
<hr />
<div>Mise (pronounced "meez") is a development environment setup tool. It can install and manage dev tools/runtimes like node, python, or php.<br />
<br />
== Runtimes ==<br />
<br />
=== PHP ===<br />
Debian dependencies<syntaxhighlight lang="text"><br />
build-essentetials cpp unzip locate autoconf bison re2c pkg-config libxml2-dev libsqlite3-dev zlib1g-dev libcurl4-openssl-dev libgd-dev libonig-dev libpq-dev libreadline-dev libzip-dev<br />
</syntaxhighlight></div>Timonhttps://wiki.its-treason.com/index.php?title=Docker&diff=51Docker2024-01-24T00:17:05Z<p>Timon: Created page with "== Multi-arch Build == === Builder Setup === Install QEMOU to allow emulation of different arches. Using emulation is not the most efficient way to build an image. See [https://docs.docker.com/build/building/multi-platform/#qemu Docker docs] for more other ways.<syntaxhighlight lang="shell"> docker run --privileged --rm tonistiigi/binfmt --install all </syntaxhighlight>Creating the new builder:<syntaxhighlight lang="shell"> docker buildx create --name <Name> --bootstra..."</p>
<hr />
<div>== Multi-arch Build ==<br />
<br />
=== Builder Setup ===<br />
Install QEMOU to allow emulation of different arches. Using emulation is not the most efficient way to build an image. See [https://docs.docker.com/build/building/multi-platform/#qemu Docker docs] for more other ways.<syntaxhighlight lang="shell"><br />
docker run --privileged --rm tonistiigi/binfmt --install all<br />
</syntaxhighlight>Creating the new builder:<syntaxhighlight lang="shell"><br />
docker buildx create --name <Name> --bootstrap --use<br />
</syntaxhighlight>Replace <code><Name></code> with a different name. The Flag <code>--use</code> will automaticity select the builder as default. Running <code>docker buildx ls</code> should show your new builder with all kind of platforms available.<br />
<br />
=== Building an Image ===<br />
Edit your Dockerfile to select the arch depending on the build argument.<syntaxhighlight lang="diff"><br />
- FROM alpine:latest<br />
+ ARG ARCH=<br />
+ FROM ${ARCH}alpine:latest<br />
</syntaxhighlight>Now you can build your image using</div>Timonhttps://wiki.its-treason.com/index.php?title=Mise&diff=50Mise2024-01-05T00:07:19Z<p>Timon: Created page with "Mise (pronounced "meez") is a development environment setup tool. It can install and manage dev tools/runtimes like node, python, or php. == Runtimes == === PHP === Debian dependencies<syntaxhighlight> build-essentetials cpp unzip locate autoconf bison re2c pkg-config libxml2-dev libsqlite3-dev zlib1g-dev libcurl4-openssl-dev libgd-dev libonig-dev libpq-dev libreadline-dev libzip-dev </syntaxhighlight>"</p>
<hr />
<div>Mise (pronounced "meez") is a development environment setup tool. It can install and manage dev tools/runtimes like node, python, or php.<br />
<br />
== Runtimes ==<br />
<br />
=== PHP ===<br />
Debian dependencies<syntaxhighlight><br />
build-essentetials cpp unzip locate autoconf bison re2c pkg-config libxml2-dev libsqlite3-dev zlib1g-dev libcurl4-openssl-dev libgd-dev libonig-dev libpq-dev libreadline-dev libzip-dev<br />
</syntaxhighlight></div>Timonhttps://wiki.its-treason.com/index.php?title=File:Logo_senate_round.png&diff=49File:Logo senate round.png2023-12-18T22:34:14Z<p>Timon: Timon uploaded a new version of File:Logo senate round.png</p>
<hr />
<div></div>Timonhttps://wiki.its-treason.com/index.php?title=File:Logo_senate_round.png&diff=48File:Logo senate round.png2023-12-18T22:06:33Z<p>Timon: </p>
<hr />
<div></div>Timonhttps://wiki.its-treason.com/index.php?title=Raspberry_Pi&diff=47Raspberry Pi2023-07-23T20:47:35Z<p>Timon: /* SSH-Key authorization */</p>
<hr />
<div>=== Watchdog setup ===<br />
The Watchdog will ensure that the Raspberry Pi will restart in case it freezes.<br />
<br />
Ensure the watchdog is installed as a Kernel module: <code>ls -al /dev/watchdog*</code> should show one or more files.<br />
<br />
The watchdog must then be enabled in <code>systemd</code>. Edit the <code>/etc/systemd/system.conf</code> config file. Under the <code>[Manager]</code> section, add the following:<syntaxhighlight lang="toml"><br />
RuntimeWatchdogSec=10<br />
ShutdownWatchdogSec=10min<br />
</syntaxhighlight>Reboot the system to apply all changes. <code>dmesg</code> should now log watchdog being started.<syntaxhighlight lang="shell"><br />
$ dmesg | grep -i watchdog<br />
[ 0.596574] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer<br />
[ 2.336190] systemd[1]: Using hardware watchdog 'Broadcom BCM2835 Watchdog timer', version 0, device /dev/watchdog<br />
[ 2.336229] systemd[1]: Set hardware watchdog to 10s.<br />
</syntaxhighlight>To test the watchdog, you can start a fork bomb to freeze the system, the watchdog should detect the freeze and automatically reboot. This fork bomb can be executed inside your shell: <code>:(){ :|:& };:</code> '''This will freeze your system! Make sure nothing important is running in the background. It can take a few minutes before reboot.'''<br />
<br />
=== SSH key authorization ===<br />
By depositing the public key on the Raspberry Pi, you can connect using SSH without using a password.<br />
<br />
Ensure that you already created an SSH key, if not follow these instructions: [https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key Generation a new SSH key]. Execute <code>ssh-copy-id <username>@<host></code> this will collect your local SSH key and ask for a password. When the password was correct, the Public key will be copied to <code>~/.ssh/authorized_keys</code> and SSH will not ask for a password the next time connecting.</div>Timonhttps://wiki.its-treason.com/index.php?title=Raspberry_Pi&diff=46Raspberry Pi2023-07-23T13:43:12Z<p>Timon: Add ssh-key auth</p>
<hr />
<div>=== Watchdog setup ===<br />
The Watchdog will ensure that the Raspberry Pi will restart in case it freezes.<br />
<br />
Ensure the watchdog is installed as a Kernel module: <code>ls -al /dev/watchdog*</code> should show one or more files.<br />
<br />
The watchdog must then be enabled in <code>systemd</code>. Edit the <code>/etc/systemd/system.conf</code> config file. Under the <code>[Manager]</code> section, add the following:<syntaxhighlight lang="toml"><br />
RuntimeWatchdogSec=10<br />
ShutdownWatchdogSec=10min<br />
</syntaxhighlight>Reboot the system to apply all changes. <code>dmesg</code> should now log watchdog being started.<syntaxhighlight lang="shell"><br />
$ dmesg | grep -i watchdog<br />
[ 0.596574] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer<br />
[ 2.336190] systemd[1]: Using hardware watchdog 'Broadcom BCM2835 Watchdog timer', version 0, device /dev/watchdog<br />
[ 2.336229] systemd[1]: Set hardware watchdog to 10s.<br />
</syntaxhighlight>To test the watchdog, you can start a fork bomb to freeze the system, the watchdog should detect the freeze and automatically reboot. This fork bomb can be executed inside your shell: <code>:(){ :|:& };:</code> '''This will freeze your system! Make sure nothing important is running in the background. It can take a few minutes before reboot.'''<br />
<br />
=== SSH-Key authorization ===<br />
By depositing the public key on the Raspberry Pi, you can connect using SSH without using a password.<br />
<br />
Ensure that you already created an SSH key, if not follow these instructions: [https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key Generation a new SSH key]. Execute <code>ssh-copy-id <username>@<host></code> this will collect your local SSH key and ask for a password. When the password was correct, the Public key will be copied to <code>~/.ssh/authorized_keys</code> and SSH will not ask for a password the next time connecting.</div>Timonhttps://wiki.its-treason.com/index.php?title=Main_Page&diff=45Main Page2023-05-31T12:54:24Z<p>Timon: </p>
<hr />
<div>My Personal Wiki.<br />
<br />
[[Special:Categories|Categories]]<br />
<br />
[[Special:AllPages]]</div>Timonhttps://wiki.its-treason.com/index.php?title=WSL2&diff=44WSL22023-05-31T12:47:46Z<p>Timon: Created page with "== Reclaiming disk space == All data of WSL2 Distros and Docker is stored in <code>.vhdx</code> files under the current user's “AppData” directory. The problem is that the virtual hard disk files size will not shrink when disk space in freed on the WSL2 distro. This issue has already been discussed on GitHub: https://github.com/microsoft/WSL/issues/4699 but currently the only solution is to manually optimize the virtual hard disk to reclaim disk space. === Locating..."</p>
<hr />
<div>== Reclaiming disk space ==<br />
All data of WSL2 Distros and Docker is stored in <code>.vhdx</code> files under the current user's “AppData” directory. The problem is that the virtual hard disk files size will not shrink when disk space in freed on the WSL2 distro. This issue has already been discussed on GitHub: https://github.com/microsoft/WSL/issues/4699 but currently the only solution is to manually optimize the virtual hard disk to reclaim disk space.<br />
<br />
=== Locating the virtual hard disk files ===<br />
[[File:Windirstat virtual disk wsl2.png|thumb|Example with “DinDirStat” the two virtual hard disks are clearly visible in purple.]]<br />
The easiest way to locate them is to use “WinDirStat” it will show the files clearly and allows copying and pasting the path.<br />
<br />
Without “WinDirStat” the files can be found under <code>C:\Users\<User>\AppData\Local\Docker\wsl\data\ext4.vhdx</code> for docker and <code>C:\Users\<User>\AppData\Local\Packages\<Distro>\LocalState\ext4.vhdx</code>.<br />
<br />
=== Reclaiming space ===<br />
First, be sure to shut down all WSL2 distros by running <code>wsl --shutdown</code> inside a PowerShell. After that, executing <code>wsl --list --running</code> should print out <code>There are no running distributions.</code>.<br />
<br />
After shutting down all WSL2 distros, you can run <code>optimize-vhd -Path <Path> -Mode full</code> in a PowerShell with administrator privileges. The optimization process will take a few minutes to complete.</div>Timonhttps://wiki.its-treason.com/index.php?title=File:Windirstat_virtual_disk_wsl2.png&diff=43File:Windirstat virtual disk wsl2.png2023-05-31T12:31:50Z<p>Timon: </p>
<hr />
<div>Screenshot of “WinDirStat” with clearly visible virtual disks.</div>Timonhttps://wiki.its-treason.com/index.php?title=Debian_Packaging&diff=42Debian Packaging2023-05-24T20:54:04Z<p>Timon: </p>
<hr />
<div>==Debian folder==<br />
The "debian"-Folder should be in the root of the project. It contains all Metadata and scripts for creating the final package.<br />
<br />
===Required Files===<br />
These files are the bare minimum to create a Debian package<br />
<br />
==== control ====<br />
The "control" file contains metadata about the package like version and dependencies, mostly used by package managers like apt. Full specification at: https://www.debian.org/doc/debian-policy/ch-controlfields.html<br />
<br />
==Building the package==<br />
<br />
==Backports==<br />
Packages are typical first build for "sid" ("unstable") and after a few days also released for the current testing distribution (Currently code name "bookworm"). Older Stable distributions only get package updates for bug fixes. New features are only distributed with "backports". Backports are packages original build for a newer distribution, e.g. sid and are rebuilt for older distributions to provide new features.<br />
<br />
===Naming===<br />
The Version of a backported package should end with <code>~bpoDISTRO+BACKPORT_REVISION</code> with "DISTRO" being replaces with the target distribution number, e.g. 10 for "buster" and "BACKPORT_REVISION" is the package revision number starting at 1. <br />
<br />
<code>dch --bpo</code> will automatically create the correct changelog entry for the backport.<br />
{| class="wikitable"<br />
|+Distribution list with Examples<br />
!Codename<br />
!Number<br />
!Example<br />
|-<br />
|Bullseye<br />
|11<br />
|<code>1.2.3-4~bpo11+1</code><br />
|-<br />
|Buster<br />
|10<br />
|<code>1.2.3-4~bpo10+1</code><br />
|-<br />
|Jammy<br />
|22.04<br />
|<code>1.2.3-4~bpo22.04+1</code><br />
|-<br />
|Focal<br />
|20.04<br />
|<code>1.2.3-4~bpo20.04+1</code><br />
|}<br />
Packages are only backported to the last 2 Distributions.</div>Timonhttps://wiki.its-treason.com/index.php?title=Debian_Packaging&diff=41Debian Packaging2023-05-03T21:33:03Z<p>Timon: </p>
<hr />
<div>==Debian folder==<br />
The "debian"-Folder should be in the root of the project. It contains all Metadata and scripts for creating the final package.<br />
<br />
===Required Files===<br />
These files are the bare minimum to create a Debian package<br />
<br />
==== control ====<br />
The "control" file contains metadata about the package like version and dependencies, mostly used by package managers like apt. Full specification at: https://www.debian.org/doc/debian-policy/ch-controlfields.html<br />
<br />
==Building the package==<br />
<br />
==Backports==<br />
Packages are typical first build for "sid" ("unstable") and after a few days also released for the current testing distribution (Currently code name "bookworm"). Older Stable distributions only get package updates for bug fixes. New features are only distributed with "backports". Backports are packages original build for a newer distribution, e.g. sid and are rebuilt for older distributions to provide new features.<br />
<br />
===Naming===<br />
The Version of a backported package should end with <code>~bpoDISTRO+BACKPORT_REVISION</code> with "DISTRO" being replaces with the target distribution number, e.g. 10 for "buster" and "BACKPORT_REVISION" is the package revision number starting at 1. <br />
<br />
<code>dch --bpo</code> will automatically create the correct changelog entry for the backport.<br />
{| class="wikitable"<br />
|+Distribution list with Examples<br />
!Codename<br />
!Number<br />
!Example<br />
|-<br />
|Bullseye<br />
|11<br />
|<code>1.2.3-4~bpo11+1</code><br />
|-<br />
|Buster<br />
|10<br />
|<code>1.2.3-4~bpo10+1</code><br />
|-<br />
|Focal<br />
|22.04<br />
|<code>1.2.3-4~bpo22.04+1</code><br />
|-<br />
|Bionic<br />
|20.04<br />
|<code>1.2.3-4~bpo20.04+1</code><br />
|}<br />
Packages are only backported to the last 2 Distributions.</div>Timonhttps://wiki.its-treason.com/index.php?title=Debian_Packaging&diff=40Debian Packaging2023-05-03T12:49:55Z<p>Timon: </p>
<hr />
<div>==Debian folder==<br />
The "debian"-Folder should be in the root of the project. It contains all Metadata and scripts for creating the final package.<br />
<br />
===Required Files===<br />
These files are the bare minimum to create a Debian package<br />
<br />
==Building the package==<br />
<br />
==Backports==<br />
Packages are typical first build for "sid" ("unstable") and after a few days also released for the current testing distribution (Currently code name "bookworm"). Older Stable distributions only get package updates for bug fixes. New features are only distributed with "backports". Backports are packages original build for a newer distribution, e.g. sid and are rebuilt for older distributions to provide new features.<br />
<br />
===Naming===<br />
The Version of a backported package should end with <code>~bpoDISTRO+BACKPORT_REVISION</code> with "DISTRO" being replaces with the target distribution number, e.g. 10 for "buster" and "BACKPORT_REVISION" is the package revision number starting at 1. <br />
<br />
<code>dch --bpo</code> will automatically create the correct changelog entry for the backport.<br />
{| class="wikitable"<br />
|+Distribution list with Examples<br />
!Codename<br />
!Number<br />
!Example<br />
|-<br />
|Bullseye<br />
|11<br />
|<code>1.2.3-4~bpo11+1</code><br />
|-<br />
|Buster<br />
|10<br />
|<code>1.2.3-4~bpo10+1</code><br />
|-<br />
|Focal<br />
|22.04<br />
|<code>1.2.3-4~bpo22.04+1</code><br />
|-<br />
|Bionic<br />
|20.04<br />
|<code>1.2.3-4~bpo20.04+1</code><br />
|}<br />
Packages are only backported to the last 2 Distributions.</div>Timonhttps://wiki.its-treason.com/index.php?title=Debian_Packaging&diff=39Debian Packaging2023-05-03T12:46:02Z<p>Timon: </p>
<hr />
<div>==Debian folder==<br />
The "debian"-Folder should be in the root of the project. It contains all Metadata and scripts for creating the final package.<br />
<br />
===Required Files===<br />
These files are the bare minimum to create a Debian package<br />
<br />
==Building the package==<br />
<br />
==Backports==<br />
Packages are typical first build for "sid" ("unstable") and after a few days also released for the current testing distribution (Currently code name "bookworm"). Older Stable distributions only get updated packages for bug fixes. New features are only distributed with "backports". Backports are packages original build for a newer distribution, e.g. sid and are rebuilt for older distributions to provide new features.<br />
<br />
===Naming===<br />
The Version of a backported package should end with <code>~bpoDISTRO+BACKPORT_REVISION</code> with "DISTRO" being replaces with the target distribution number, e.g. 10 for "buster" and "BACKPORT_REVISION" is the package revision number starting at 1.<br />
{| class="wikitable"<br />
|+Distribution list with Examples<br />
!Codename<br />
!Number<br />
!Example<br />
|-<br />
|Bullseye<br />
|11<br />
|<code>1.2.3-4~bpo11+1</code><br />
|-<br />
|Buster<br />
|10<br />
|<code>1.2.3-4~bpo10+1</code><br />
|-<br />
|Focal<br />
|22.04<br />
|<code>1.2.3-4~bpo22.04+1</code><br />
|-<br />
|Bionic<br />
|20.04<br />
|<code>1.2.3-4~bpo20.04+1</code><br />
|}</div>Timonhttps://wiki.its-treason.com/index.php?title=Debian_Packaging&diff=38Debian Packaging2023-05-03T11:49:07Z<p>Timon: Created blank page</p>
<hr />
<div></div>Timonhttps://wiki.its-treason.com/index.php?title=Fstab&diff=37Fstab2023-03-18T16:12:51Z<p>Timon: </p>
<hr />
<div>== Structure ==<br />
Values are separated by one or more spaces.<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Value<br />
|-<br />
|Filesystem<br />
|The Filesystem / Partition to be mounted. <br />
Can be a the path to a partition e.g. <code>/dev/sdb2</code> or a UUID e.g. <code>PARTUUID=65561b67-2aee-4c48-8a67-2ea71f5f4ba</code><br />
|-<br />
|Mount Point<br />
|Path to the mountpoint. Should be an existing empty folder. Value <code>none</code> can be used for Swap-Partitions<br />
|-<br />
|FS-Type<br />
|Type of the file system e.g <code>ext4</code> or <code>ntfs</code><br />
|-<br />
|Options<br />
|Mounting options. e.g. <code>defaults,nofail</code> -> Default settings, allow booting when mounting the partition fails<br />
|-<br />
|Dump<br />
|Weather to create a Dump before mounting. <code>0</code> don't create dump. <code>1</code> create dump<br />
|-<br />
|Check Fsck<br />
|Check file system before mounting them. <code>0</code> don't check anything should be used for Windows / NTFS Partitions. <code>1</code> For root file system (Except if type is <code>btfs</code>or <code>XFS</code>). <code>2</code> Check the filesystem before mounting.<br />
|}<br />
Example <code>fstab</code> file:<syntaxhighlight lang="text"><br />
# This is the default fstab of a rpi with an external harddrive<br />
proc /proc proc defaults 0 0<br />
PARTUUID=0a70b801-01 /boot vfat defaults,flush 0 2<br />
PARTUUID=0a70b801-02 / ext4 defaults,noatime 0 1<br />
# a swapfile is not a swap partition, no line here<br />
# use dphys-swapfile swap[on|off] for that<br />
<br />
PARTUUID=6b8fd307-ae27-4222-b81c-926eaa800dbc /data ext4 defaults,nofail 0 2<br />
<br />
</syntaxhighlight><br />
<br />
== Options ==<br />
For all list of all options, see: [https://man.archlinux.org/man/ext4.5#MOUNT_OPTIONS Ext file system options] and [https://man.archlinux.org/man/mount.8#FILESYSTEM-INDEPENDENT_MOUNT_OPTIONS File system independent Options]. Note that changing owner or permissions is only really needed for file system that don't support UNIX permissions, e.g <code>NTFS</code>. <code>ext4</code> and others will save all permissions.<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Description<br />
|-<br />
|defaults<br />
|Commen Default settings. These include: <code>rw</code>,<code>suid</code>,<code>dev</code>,<code>exec</code>,<code>auto</code>,<code>nouser</code>,<code>async</code>,<code>realtime</code><br />
|-<br />
|ro<br />
|Mount the file system in readonly mode<br />
|-<br />
|rw<br />
|Mount the file system in Read-Write mode (In defaults)<br />
|-<br />
|nofail<br />
|Skip the file system if it can't be found. Very usefull for thumb-drives. If this options is not set, the system will wait for the filesystem to be connected before booting<br />
|-<br />
|umask=PERMS<br />
|Set the Permissions for all files and directories. Important: This is a umask so its disallows permissions e.g. <code>000</code> becomes <code>777</code>, <code>022</code>becomes<code>755</code>.<br />
|-<br />
|uid=UID<br />
|Set the owner of all files. Can be the users UID or username.<br />
|-<br />
|gid=GID<br />
|Set the owner group of all files. Can be the groups GID or groupname.<br />
|-<br />
|windows_names<br />
|Only for NTFS: Prevent the creating of files with characters that are not allowed within Windows e.g. <code><nowiki>" * < > / | \</nowiki></code> and some <br />
|}<br />
<br />
== Determine file system types and UUID ==<br />
<br />
== Validating fstab ==<br />
Executing <code>mount -fav</code> will try to mount all file systems without actually making a system call. <br />
<br />
* <code>-a</code> Try to auto mount everything inside <code>fstab</code>.<br />
* <code>-f</code> Fake, don't make any system calls. <br />
* <code>-v</code> Verbose print more debug output.<br />
<br />
Alternative <code>findmnt --verify --verbose</code> can print nice information and detailed error messages.<br />
<br />
Output without any errors:<syntaxhighlight lang="text"><br />
# findmnt --verify --verbose<br />
/proc<br />
[ ] target exists<br />
[ ] do not check proc source (pseudo/net)<br />
[ ] do not check proc FS type (pseudo/net)<br />
/boot<br />
[ ] target exists<br />
[ ] FS options: flush<br />
[ ] PARTUUID=0a70b801-01 translated to /dev/mmcblk0p1<br />
[ ] source /dev/mmcblk0p1 exists<br />
[ ] FS type is vfat<br />
/<br />
[ ] target exists<br />
[ ] VFS options: noatime<br />
[ ] PARTUUID=0a70b801-02 translated to /dev/mmcblk0p2<br />
[ ] source /dev/mmcblk0p2 exists<br />
[ ] FS type is ext4<br />
/data<br />
[ ] target exists<br />
[ ] userspace options: nofail<br />
[ ] PARTUUID=6b8fd307-ae27-4222-b81c-926eaa800dbc translated to /dev/sda1<br />
[ ] source /dev/sda1 exists<br />
[ ] FS type is ext4<br />
Success, no errors or warnings detected<br />
</syntaxhighlight>Output with wrong <code>PARTUUID</code> value:<syntaxhighlight lang="text"><br />
# findmnt --verify --verbose<br />
/proc<br />
[ ] target exists<br />
...<br />
[ ] source /dev/mmcblk0p2 exists<br />
[ ] FS type is ext4<br />
/data<br />
[ ] target exists<br />
[ ] userspace options: nofail<br />
[E] unreachable on boot required source: PARTUUID=6b8fd307-ae27-4222-b81c-926eaa800db<br />
<br />
0 parse errors, 1 error, 0 warnings<br />
</syntaxhighlight></div>Timonhttps://wiki.its-treason.com/index.php?title=Raspberry_Pi&diff=35Raspberry Pi2023-03-18T13:20:46Z<p>Timon: Created page with "=== Watchdog setup === Be sure the watchdog is installed as a Kernel module: <code>ls -al /dev/watchdog*</code> should show one or more files. The watchdog must then be enabled in <code>systemd</code>. Edit the <code>/etc/systemd/system.conf</code> config file. Under the <code>[Manager]</code> section, add the following:<syntaxhighlight lang="toml"> RuntimeWatchdogSec=10 ShutdownWatchdogSec=10min </syntaxhighlight>Reboot the system to apply all changes. <code>dmesg</cod..."</p>
<hr />
<div>=== Watchdog setup ===<br />
Be sure the watchdog is installed as a Kernel module: <code>ls -al /dev/watchdog*</code> should show one or more files.<br />
<br />
The watchdog must then be enabled in <code>systemd</code>. Edit the <code>/etc/systemd/system.conf</code> config file. Under the <code>[Manager]</code> section, add the following:<syntaxhighlight lang="toml"><br />
RuntimeWatchdogSec=10<br />
ShutdownWatchdogSec=10min<br />
</syntaxhighlight>Reboot the system to apply all changes. <code>dmesg</code> should now log watchdog being started.<syntaxhighlight lang="shell"><br />
$ dmesg | grep -i watchdog<br />
[ 0.596574] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer<br />
[ 2.336190] systemd[1]: Using hardware watchdog 'Broadcom BCM2835 Watchdog timer', version 0, device /dev/watchdog<br />
[ 2.336229] systemd[1]: Set hardware watchdog to 10s.<br />
</syntaxhighlight>To test the watchdog, you can start a fork bomb to freeze the system, the watchdog should detect the freeze and automatically reboot. This fork bomb can be executed inside your shell: <code>:(){ :|:& };:</code> '''This will freeze your system! Make sure nothing important is running in the background. It can take a few minutes before reboot.'''</div>Timonhttps://wiki.its-treason.com/index.php?title=Fstab&diff=33Fstab2023-03-18T12:29:43Z<p>Timon: Created page with "== Structure == Values are separated by one or more spaces. {| class="wikitable" |+ !Name !Value |- |Filesystem |The Filesystem / Partition to be mounted. Can be a the path to a partition e.g. <code>/dev/sdb2</code> or a UUID e.g. <code>PARTUUID=65561b67-2aee-4c48-8a67-2ea71f5f4ba</code> |- |Mount Point |Path to the mountpoint. Should be an existing empty folder. Value <code>none</code> can be used for Swap-Partitions |- |FS-Type |Type of the file system e.g <code>ext4<..."</p>
<hr />
<div>== Structure ==<br />
Values are separated by one or more spaces.<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Value<br />
|-<br />
|Filesystem<br />
|The Filesystem / Partition to be mounted. <br />
Can be a the path to a partition e.g. <code>/dev/sdb2</code> or a UUID e.g. <code>PARTUUID=65561b67-2aee-4c48-8a67-2ea71f5f4ba</code><br />
|-<br />
|Mount Point<br />
|Path to the mountpoint. Should be an existing empty folder. Value <code>none</code> can be used for Swap-Partitions<br />
|-<br />
|FS-Type<br />
|Type of the file system e.g <code>ext4</code> or <code>ntfs</code><br />
|-<br />
|Options<br />
|Mounting options. e.g. <code>defaults,nofail</code> -> Default settings, allow booting when mounting the partition fails<br />
|-<br />
|Dump<br />
|Weather to create a Dump before mounting. <code>0</code> don't create dump. <code>1</code> create dump<br />
|-<br />
|Check Fsck<br />
|Check file system before mounting them. <code>0</code> don't check anything should be used for Windows / NTFS Partitions. <code>1</code> For root file system (Except if type is <code>btfs</code>or <code>XFS</code>). <code>2</code> Check the filesystem before mounting.<br />
|}<br />
Example <code>fstab</code> file:<syntaxhighlight lang="text"><br />
# This is the default fstab of a rpi with an external harddrive<br />
proc /proc proc defaults 0 0<br />
PARTUUID=0a70b801-01 /boot vfat defaults,flush 0 2<br />
PARTUUID=0a70b801-02 / ext4 defaults,noatime 0 1<br />
# a swapfile is not a swap partition, no line here<br />
# use dphys-swapfile swap[on|off] for that<br />
<br />
PARTUUID=6b8fd307-ae27-4222-b81c-926eaa800dbc /data ext4 defaults,nofail 0 2<br />
<br />
</syntaxhighlight><br />
<br />
== Options ==<br />
For all list of all options, see: [https://man.archlinux.org/man/ext4.5#MOUNT_OPTIONS Ext file system options] and [https://man.archlinux.org/man/mount.8#FILESYSTEM-INDEPENDENT_MOUNT_OPTIONS File system independent Options]. Note that changing owner or permissions is only really needed for file system that don't support UNIX permissions, e.g <code>NTFS</code>. <code>ext4</code> and others will save all permissions.<br />
{| class="wikitable"<br />
|+<br />
!Name<br />
!Description<br />
|-<br />
|defaults<br />
|Commen Default settings. These include: <code>rw</code>,<code>suid</code>,<code>dev</code>,<code>exec</code>,<code>auto</code>,<code>nouser</code>,<code>async</code>,<code>realtime</code><br />
|-<br />
|ro<br />
|Mount the file system in readonly mode<br />
|-<br />
|rw<br />
|Mount the file system in Read-Write mode (In defaults)<br />
|-<br />
|nofail<br />
|Skip the file system if it can't be found. Very usefull for thumb-drives. If this options is not set, the system will wait for the filesystem to be connected before booting<br />
|-<br />
|umask=PERMS<br />
|Set the Permissions for all files and directories. Important: This is a umask so its disallows permissions e.g. <code>000</code> becomes <code>777</code>, <code>022</code>becomes<code>755</code>.<br />
|-<br />
|uid=UID<br />
|Set the owner of all files. Can be the users UID or username.<br />
|-<br />
|gid=GID<br />
|Set the owner group of all files. Can be the groups GID or groupname.<br />
|-<br />
|windows_names<br />
|Only for NTFS: Prevent the creating of files with characters that are not allowed within Windows e.g. <code><nowiki>" * < > / | \</nowiki></code> and some <br />
|}<br />
<br />
== Determine file system types and UUID ==<br />
<br />
== Validating fstab ==<br />
Executing <code>mount -fav</code> will try to mount all file systems without actually making a system call. <br />
<br />
* <code>-a</code> Try to auto mount everything inside <code>fstab</code>.<br />
* <code>-f</code> Fake, don't make any system calls. <br />
* <code>-v</code> Verbose print more debug output.<br />
<br />
Alternative <code>findmnt --verify --verbose</code> can print nice information and detailed error messages.<br />
<br />
Output without any errors:<syntaxhighlight lang="text"><br />
# findmnt --verify --verbose<br />
/proc<br />
[ ] target exists<br />
[ ] do not check proc source (pseudo/net)<br />
[ ] do not check proc FS type (pseudo/net)<br />
/boot<br />
[ ] target exists<br />
[ ] FS options: flush<br />
[ ] PARTUUID=0a70b801-01 translated to /dev/mmcblk0p1<br />
[ ] source /dev/mmcblk0p1 exists<br />
[ ] FS type is vfat<br />
/<br />
[ ] target exists<br />
[ ] VFS options: noatime<br />
[ ] PARTUUID=0a70b801-02 translated to /dev/mmcblk0p2<br />
[ ] source /dev/mmcblk0p2 exists<br />
[ ] FS type is ext4<br />
/data<br />
[ ] target exists<br />
[ ] userspace options: nofail<br />
[ ] PARTUUID=6b8fd307-ae27-4222-b81c-926eaa800dbc translated to /dev/sda1<br />
[ ] source /dev/sda1 exists<br />
[ ] FS type is ext4<br />
Success, no errors or warnings detected<br />
</syntaxhighlight>Output with wrong <code>PARTUUID</code> value:<syntaxhighlight><br />
# findmnt --verify --verbose<br />
/proc<br />
[ ] target exists<br />
...<br />
[ ] source /dev/mmcblk0p2 exists<br />
[ ] FS type is ext4<br />
/data<br />
[ ] target exists<br />
[ ] userspace options: nofail<br />
[E] unreachable on boot required source: PARTUUID=6b8fd307-ae27-4222-b81c-926eaa800db<br />
<br />
0 parse errors, 1 error, 0 warnings<br />
</syntaxhighlight></div>Timonhttps://wiki.its-treason.com/index.php?title=Certbot&diff=32Certbot2023-01-29T15:06:48Z<p>Timon: typo</p>
<hr />
<div>The Certbot is used the issue LetsEncrypt SSL-Certificates.<br />
<br />
== Install ==<br />
<br />
=== Snap Store ===<br />
This is the install method advised by LetsEncrypt.<br />
<br />
Make sure the certbot is not installed using Apt: <code>sudo apt remove certbot</code>.<br />
<br />
Ensure the latest Snap version is installed: <code>sudo snap install core; sudo snap refresh core</code>.<br />
<br />
Install the Certbot, make sure to use the <code>--classic</code> flag: <code>sudo snap install --classic certbot</code>.<br />
<br />
Link the certbot binary to a path thats in the $PATH variabel: <code>sudo ln -s /snap/bin/certbot /usr/bin/certbot</code>. Depending on your environment this might not be necessary.<br />
<br />
=== Apt & Apk ===<br />
The certbot is also available in the officiall Debian, Ubuntu & Alpine repositories, but the version might be outdated.<br />
<br />
* Ubuntu & Debian: <code>apt install certbot</code><br />
* Alpine: <code>apk install certbot</code><br />
<br />
== Retrieving a Certificate ==<br />
To create an Certificate for <code>example.com</code> <br />
<br />
<code>sudo certbot certonly --nginx --agree-tos -n -d example.com</code><br />
<br />
* <code>--nginx</code>: Use Local installed nginx for the Authentication-Challange, see Challanges for other ways to authenticate<br />
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option<br />
* <code>-n</code>: Non-Interactive, do not prompt for anything<br />
* <code>-d <DOMAIN></code>: Domain to create the Certificate for<br />
<br />
The Certificate will be saved under:<br />
<br />
* <code>/etc/letsencrypt/live/<DOMAIN>/fullchain.pem</code>: Certificate<br />
* <code>/etc/letsencrypt/live/<DOMAIN>/privkey.pem</code>: Private key<br />
<br />
== Renewing Certificates ==<br />
To renew all Certificates use:<br />
<br />
<code>sudo certbot renew --nginx --agree-tos -n</code><br />
<br />
* <code>--nginx</code>: Use a locally installed nginx for the authentication challange. See [[Certbot#Challenges|Challenges]] for other ways to authenticate<br />
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option<br />
* <code>-n</code>: Non-Interactive, do not prompt for anything<br />
* <code>-d <DOMAIN></code>: Optional, Domain to renew the Certificate for<br />
<br />
Certificates will be updated if there expire in less than 30 days<br />
<br />
== Challenges ==<br />
To validate that you own a Domain you must complete a challange using one of the following method:<br />
<br />
=== Nginx ===<br />
If a Nginx is running localy and serving for your domain you can simply use the <code>--nginx</code> option and certbot will use Nginx for the Challange and should complete it without stopping the Nginx.<br />
<br />
=== Apache ===<br />
If a Apache is running localy and serving for your domain you can simply use the <code>--apache</code> option and certbot will use Apache for the Challange and should complete it without stopping the Apache server.<br />
<br />
=== Standalone ===<br />
Certbot will start a Webserver on Port 80 and will try to serve a file containg a verification code. If the Certbot can find that file, the challange will be completed.<br />
<br />
=== Webroot ===<br />
Using the <code>--webroot <Path></code> the Certbot will put files under the given directory und the given directory and try to access them.</div>Timonhttps://wiki.its-treason.com/index.php?title=Certbot&diff=31Certbot2023-01-29T15:06:25Z<p>Timon: Add Apt & Apk install and also fix spelling</p>
<hr />
<div>The Certbot is used the issue LetsEncrypt SSL-Certificates.<br />
<br />
== Install ==<br />
<br />
=== Snap-Store ===<br />
This is the install method advised by LetsEncrypt.<br />
<br />
Make sure the certbot is not installed using Apt: <code>sudo apt remove certbot</code>.<br />
<br />
Ensure the latest Snap version is installed: <code>sudo snap install core; sudo snap refresh core</code>.<br />
<br />
Install the Certbot, make sure to use the <code>--classic</code> flag: <code>sudo snap install --classic certbot</code>.<br />
<br />
Link the certbot binary to a path thats in the $PATH variabel: <code>sudo ln -s /snap/bin/certbot /usr/bin/certbot</code>. Depending on your environment this might not be necessary.<br />
<br />
=== Apt & Apk ===<br />
The certbot is also available in the officiall Debian, Ubuntu & Alpine repositories, but the version might be outdated.<br />
<br />
* Ubuntu & Debian: <code>apt install certbot</code><br />
* Alpine: <code>apk install certbot</code><br />
<br />
== Retrieving a Certificate ==<br />
To create an Certificate for <code>example.com</code> <br />
<br />
<code>sudo certbot certonly --nginx --agree-tos -n -d example.com</code><br />
<br />
* <code>--nginx</code>: Use Local installed nginx for the Authentication-Challange, see Challanges for other ways to authenticate<br />
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option<br />
* <code>-n</code>: Non-Interactive, do not prompt for anything<br />
* <code>-d <DOMAIN></code>: Domain to create the Certificate for<br />
<br />
The Certificate will be saved under:<br />
<br />
* <code>/etc/letsencrypt/live/<DOMAIN>/fullchain.pem</code>: Certificate<br />
* <code>/etc/letsencrypt/live/<DOMAIN>/privkey.pem</code>: Private key<br />
<br />
== Renewing Certificates ==<br />
To renew all Certificates use:<br />
<br />
<code>sudo certbot renew --nginx --agree-tos -n</code><br />
<br />
* <code>--nginx</code>: Use a locally installed nginx for the authentication challange. See [[Certbot#Challenges|Challenges]] for other ways to authenticate<br />
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option<br />
* <code>-n</code>: Non-Interactive, do not prompt for anything<br />
* <code>-d <DOMAIN></code>: Optional, Domain to renew the Certificate for<br />
<br />
Certificates will be updated if there expire in less than 30 days<br />
<br />
== Challenges ==<br />
To validate that you own a Domain you must complete a challange using one of the following method:<br />
<br />
=== Nginx ===<br />
If a Nginx is running localy and serving for your domain you can simply use the <code>--nginx</code> option and certbot will use Nginx for the Challange and should complete it without stopping the Nginx.<br />
<br />
=== Apache ===<br />
If a Apache is running localy and serving for your domain you can simply use the <code>--apache</code> option and certbot will use Apache for the Challange and should complete it without stopping the Apache server.<br />
<br />
=== Standalone ===<br />
Certbot will start a Webserver on Port 80 and will try to serve a file containg a verification code. If the Certbot can find that file, the challange will be completed.<br />
<br />
=== Webroot ===<br />
Using the <code>--webroot <Path></code> the Certbot will put files under the given directory und the given directory and try to access them.</div>Timonhttps://wiki.its-treason.com/index.php?title=File:UML-Anwendungsfalldiagramm_beispiel.png&diff=21File:UML-Anwendungsfalldiagramm beispiel.png2022-02-23T19:11:43Z<p>Timon: </p>
<hr />
<div>Beispiel vom UML-Anwendungsfalldiagramm erstellt mit Excalidraw</div>Timonhttps://wiki.its-treason.com/index.php?title=Traefik&diff=19Traefik2022-02-07T22:40:37Z<p>Timon: /* Example Configuration File (YML) */</p>
<hr />
<div>Traefik is a reverse Proxy that manages routing of services on a Server.<br />
<br />
===Getting started===<br />
Traefik is preferable used inside a Docker container. <br />
<br />
Traefik docker-compose file:<br />
<syntaxhighlight lang="yaml"><br />
version: '3.9'<br />
<br />
services:<br />
reverse-proxy:<br />
image: traefik:v2.6<br />
restart: "always"<br />
# In this example traefik is configured with CLI options.<br />
# "--providers.docker=true": Enable Docker as a provider<br />
# "--providers.docker.network="traefik"" specify the docker network "traefik" as the network for traefik. This is option must be used when a container has two or more networks attached to it<br />
# "--api.insecure=true": enables traefiks dashboard<br />
command: --providers.docker=true --providers.docker.network="traefik" --api.insecure=true<br />
ports:<br />
# Open Port 80 & 443 for traefik<br />
- "80:80"<br />
- "443:443"<br />
# Open Port 8080 for traefiks webinterface<br />
- "8080:8080"<br />
volumes:<br />
# mount the docker socket, so that Traefik can listen to the Docker events<br />
- /var/run/docker.sock:/var/run/docker.sock<br />
networks:<br />
- traefik<br />
<br />
networks:<br />
traefik:<br />
driver: "bridge"<br />
name: traefik<br />
</syntaxhighlight><br />
<br />
Webserver docker-compose file:<br />
<syntaxhighlight lang="yaml"><br />
version: '3.9'<br />
<br />
services:<br />
webserver:<br />
image: httpd:2.4.52-alpine<br />
restart: "always"<br />
expose:<br />
# If only one port is exposed traefik, will detect and use it<br />
- 80<br />
labels:<br />
# Rules for routing can be defined with labels. "traefik.http.routers.<Container name>.rule" tells traefik when to route to this container<br />
# In this case traefik will route to this webserver when the requested host is "example.com"<br />
- traefik.http.routers.webserver.rule=Host(`example.com`)<br />
networks:<br />
# Make sure to add this service to the same network as traefik<br />
- traefik<br />
<br />
networks:<br />
traefik:<br />
external: true<br />
</syntaxhighlight><br />
<br />
===Configuration===<br />
Traefik can be configured by either commandline options or a config file. A config file must be created under <code>/etc/traefik/traefik.yml</code>. This file can also be in TOML format. Also note that all config options and values are '''case sensitive'''.<br />
<br />
==== Docker ====<br />
Full documentation about this topic: [https://doc.traefik.io/traefik/providers/docker/ Docker]<br />
<br />
===== providers.docker.exposedByDefault =====<br />
Default value: ''true''<br />
<br />
If set to false all containers are ignored by default and must use the <code>traefik.enable=true</code> label to be not ignored by traefik. This is usefull if you have a lot of containers not exposing any ports.<br />
<br />
===== providers.docker.network =====<br />
Default value: ''<None>''<br />
<br />
This defines the docker network that should be used by traefik to connect to other containers. If a container uses more than the traefik network this option should be used. This can also be applied per-container with the <code>traefik.docker.network</code> label.<br />
<br />
==== Logging ====<br />
Full documentation about this topic: [https://doc.traefik.io/traefik/observability/access-logs/ Access Logs] & [https://doc.traefik.io/traefik/observability/logs/ Logs]<br />
<br />
===== accessLog.filePath =====<br />
Default value: ''<None>''<br />
<br />
Defines the file to write access logs. If this option is not used the access logs are written to standard output (StdOut).<br />
<br />
===== accessLog.format =====<br />
Default value: ''"CLF"''<br />
<br />
Access logs written in the "Common Log Format" (CLF) by default. It is also possable to write access logs as JSON, by setting the format to <code>json</code>. Note the access log file is not written as a valid JSON file but instead is written in [https://jsonlines.org/ JSON-Lines]. If an Invalid format is provided traefik willl fallback to <code>CLF</code>.<br />
<br />
===== log.filePath =====<br />
Default value: ''<None>''<br />
<br />
Defines the file to write logs. If this option is not used the logs are written to standard output (StdOut).<br />
<br />
===== log.format =====<br />
Default value: ''"CLF"''<br />
<br />
Logs written in the "Common Log Format" (CLF) by default. It is also possable to write logs as JSON, by setting the format to <code>json</code>. Note the log file not in written as valid JSON file but instead is written in [https://jsonlines.org/ JSON-Lines]. If an Invalid format is provided traefik willl fallback to <code>CLF</code>.<br />
<br />
===== log.level =====<br />
Default value: "''ERROR''"<br />
<br />
This options sets the verbosity of the traefik logs. Valid values are: <code>DEBUG</code>, <code>INFO</code>, <code>WARN</code>, <code>ERROR</code>, <code>FATAL</code> & <code>PANIC</code><br />
<br />
==== Example Configuration File (YML) ====<br />
<br />
<syntaxhighlight lang="yaml"><br />
api:<br />
dashboard: true<br />
insecure: true<br />
<br />
entryPoints:<br />
web:<br />
address: ":80"<br />
websecure:<br />
address: ":443"<br />
<br />
providers:<br />
docker:<br />
network: "traefik"<br />
<br />
accesslog:<br />
filepath: "/opt/access.log"<br />
<br />
log:<br />
filepath: "/opt/traefik.log"<br />
</syntaxhighlight></div>Timonhttps://wiki.its-treason.com/index.php?title=Traefik&diff=18Traefik2022-02-07T22:40:18Z<p>Timon: /* Getting started */</p>
<hr />
<div>Traefik is a reverse Proxy that manages routing of services on a Server.<br />
<br />
===Getting started===<br />
Traefik is preferable used inside a Docker container. <br />
<br />
Traefik docker-compose file:<br />
<syntaxhighlight lang="yaml"><br />
version: '3.9'<br />
<br />
services:<br />
reverse-proxy:<br />
image: traefik:v2.6<br />
restart: "always"<br />
# In this example traefik is configured with CLI options.<br />
# "--providers.docker=true": Enable Docker as a provider<br />
# "--providers.docker.network="traefik"" specify the docker network "traefik" as the network for traefik. This is option must be used when a container has two or more networks attached to it<br />
# "--api.insecure=true": enables traefiks dashboard<br />
command: --providers.docker=true --providers.docker.network="traefik" --api.insecure=true<br />
ports:<br />
# Open Port 80 & 443 for traefik<br />
- "80:80"<br />
- "443:443"<br />
# Open Port 8080 for traefiks webinterface<br />
- "8080:8080"<br />
volumes:<br />
# mount the docker socket, so that Traefik can listen to the Docker events<br />
- /var/run/docker.sock:/var/run/docker.sock<br />
networks:<br />
- traefik<br />
<br />
networks:<br />
traefik:<br />
driver: "bridge"<br />
name: traefik<br />
</syntaxhighlight><br />
<br />
Webserver docker-compose file:<br />
<syntaxhighlight lang="yaml"><br />
version: '3.9'<br />
<br />
services:<br />
webserver:<br />
image: httpd:2.4.52-alpine<br />
restart: "always"<br />
expose:<br />
# If only one port is exposed traefik, will detect and use it<br />
- 80<br />
labels:<br />
# Rules for routing can be defined with labels. "traefik.http.routers.<Container name>.rule" tells traefik when to route to this container<br />
# In this case traefik will route to this webserver when the requested host is "example.com"<br />
- traefik.http.routers.webserver.rule=Host(`example.com`)<br />
networks:<br />
# Make sure to add this service to the same network as traefik<br />
- traefik<br />
<br />
networks:<br />
traefik:<br />
external: true<br />
</syntaxhighlight><br />
<br />
===Configuration===<br />
Traefik can be configured by either commandline options or a config file. A config file must be created under <code>/etc/traefik/traefik.yml</code>. This file can also be in TOML format. Also note that all config options and values are '''case sensitive'''.<br />
<br />
==== Docker ====<br />
Full documentation about this topic: [https://doc.traefik.io/traefik/providers/docker/ Docker]<br />
<br />
===== providers.docker.exposedByDefault =====<br />
Default value: ''true''<br />
<br />
If set to false all containers are ignored by default and must use the <code>traefik.enable=true</code> label to be not ignored by traefik. This is usefull if you have a lot of containers not exposing any ports.<br />
<br />
===== providers.docker.network =====<br />
Default value: ''<None>''<br />
<br />
This defines the docker network that should be used by traefik to connect to other containers. If a container uses more than the traefik network this option should be used. This can also be applied per-container with the <code>traefik.docker.network</code> label.<br />
<br />
==== Logging ====<br />
Full documentation about this topic: [https://doc.traefik.io/traefik/observability/access-logs/ Access Logs] & [https://doc.traefik.io/traefik/observability/logs/ Logs]<br />
<br />
===== accessLog.filePath =====<br />
Default value: ''<None>''<br />
<br />
Defines the file to write access logs. If this option is not used the access logs are written to standard output (StdOut).<br />
<br />
===== accessLog.format =====<br />
Default value: ''"CLF"''<br />
<br />
Access logs written in the "Common Log Format" (CLF) by default. It is also possable to write access logs as JSON, by setting the format to <code>json</code>. Note the access log file is not written as a valid JSON file but instead is written in [https://jsonlines.org/ JSON-Lines]. If an Invalid format is provided traefik willl fallback to <code>CLF</code>.<br />
<br />
===== log.filePath =====<br />
Default value: ''<None>''<br />
<br />
Defines the file to write logs. If this option is not used the logs are written to standard output (StdOut).<br />
<br />
===== log.format =====<br />
Default value: ''"CLF"''<br />
<br />
Logs written in the "Common Log Format" (CLF) by default. It is also possable to write logs as JSON, by setting the format to <code>json</code>. Note the log file not in written as valid JSON file but instead is written in [https://jsonlines.org/ JSON-Lines]. If an Invalid format is provided traefik willl fallback to <code>CLF</code>.<br />
<br />
===== log.level =====<br />
Default value: "''ERROR''"<br />
<br />
This options sets the verbosity of the traefik logs. Valid values are: <code>DEBUG</code>, <code>INFO</code>, <code>WARN</code>, <code>ERROR</code>, <code>FATAL</code> & <code>PANIC</code><br />
<br />
==== Example Configuration File (YML) ====<br />
<br />
<pre><br />
api:<br />
dashboard: true<br />
insecure: true<br />
<br />
entryPoints:<br />
web:<br />
address: ":80"<br />
websecure:<br />
address: ":443"<br />
<br />
providers:<br />
docker:<br />
network: "traefik"<br />
<br />
accesslog:<br />
filepath: "/opt/access.log"<br />
<br />
log:<br />
filepath: "/opt/traefik.log"<br />
</pre></div>Timonhttps://wiki.its-treason.com/index.php?title=Traefik&diff=17Traefik2022-01-29T02:29:54Z<p>Timon: Created page with "Traefik is a reverse Proxy that manages routing of services on a Server. ===Getting started=== Traefik is preferable used inside a Docker container. Traefik docker-compose file: <pre> version: '3.9' services: reverse-proxy: image: traefik:v2.6 restart: "always" # In this example traefik is configured with CLI options. # "--providers.docker=true": Enable Docker as a provider # "--providers.docker.network="traefik"" specify the docker network "tra..."</p>
<hr />
<div>Traefik is a reverse Proxy that manages routing of services on a Server.<br />
<br />
===Getting started===<br />
Traefik is preferable used inside a Docker container. <br />
<br />
Traefik docker-compose file:<br />
<pre><br />
version: '3.9'<br />
<br />
services:<br />
reverse-proxy:<br />
image: traefik:v2.6<br />
restart: "always"<br />
# In this example traefik is configured with CLI options.<br />
# "--providers.docker=true": Enable Docker as a provider<br />
# "--providers.docker.network="traefik"" specify the docker network "traefik" as the network for traefik. This is option must be used when a container has two or more networks attached to it<br />
# "--api.insecure=true": enables traefiks dashboard<br />
command: --providers.docker=true --providers.docker.network="traefik" --api.insecure=true<br />
ports:<br />
# Open Port 80 & 443 for traefik<br />
- "80:80"<br />
- "443:443"<br />
# Open Port 8080 for traefiks webinterface<br />
- "8080:8080"<br />
volumes:<br />
# mount the docker socket, so that Traefik can listen to the Docker events<br />
- /var/run/docker.sock:/var/run/docker.sock<br />
networks:<br />
- traefik<br />
<br />
networks:<br />
traefik:<br />
driver: "bridge"<br />
name: traefik<br />
</pre><br />
<br />
Webserver docker-compose file:<br />
version: '3.9'<br />
<br />
services:<br />
webserver:<br />
image: httpd:2.4.52-alpine<br />
restart: "always"<br />
expose:<br />
# If only one port is exposed traefik, will detect and use it<br />
- 80<br />
labels:<br />
# Rules for routing can be defined with labels. "traefik.http.routers.<Container name>.rule" tells traefik when to route to this container<br />
# In this case traefik will route to this webserver when the requested host is "example.com"<br />
- traefik.http.routers.webserver.rule=Host(`example.com`)<br />
networks:<br />
# Make sure to add this service to the same network as traefik<br />
- traefik<br />
<br />
networks:<br />
traefik:<br />
external: true<br />
<br />
===Configuration===<br />
Traefik can be configured by either commandline options or a config file. A config file must be created under <code>/etc/traefik/traefik.yml</code>. This file can also be in TOML format. Also note that all config options and values are '''case sensitive'''.<br />
<br />
==== Docker ====<br />
Full documentation about this topic: [https://doc.traefik.io/traefik/providers/docker/ Docker]<br />
<br />
===== providers.docker.exposedByDefault =====<br />
Default value: ''true''<br />
<br />
If set to false all containers are ignored by default and must use the <code>traefik.enable=true</code> label to be not ignored by traefik. This is usefull if you have a lot of containers not exposing any ports.<br />
<br />
===== providers.docker.network =====<br />
Default value: ''<None>''<br />
<br />
This defines the docker network that should be used by traefik to connect to other containers. If a container uses more than the traefik network this option should be used. This can also be applied per-container with the <code>traefik.docker.network</code> label.<br />
<br />
==== Logging ====<br />
Full documentation about this topic: [https://doc.traefik.io/traefik/observability/access-logs/ Access Logs] & [https://doc.traefik.io/traefik/observability/logs/ Logs]<br />
<br />
===== accessLog.filePath =====<br />
Default value: ''<None>''<br />
<br />
Defines the file to write access logs. If this option is not used the access logs are written to standard output (StdOut).<br />
<br />
===== accessLog.format =====<br />
Default value: ''"CLF"''<br />
<br />
Access logs written in the "Common Log Format" (CLF) by default. It is also possable to write access logs as JSON, by setting the format to <code>json</code>. Note the access log file is not written as a valid JSON file but instead is written in [https://jsonlines.org/ JSON-Lines]. If an Invalid format is provided traefik willl fallback to <code>CLF</code>.<br />
<br />
===== log.filePath =====<br />
Default value: ''<None>''<br />
<br />
Defines the file to write logs. If this option is not used the logs are written to standard output (StdOut).<br />
<br />
===== log.format =====<br />
Default value: ''"CLF"''<br />
<br />
Logs written in the "Common Log Format" (CLF) by default. It is also possable to write logs as JSON, by setting the format to <code>json</code>. Note the log file not in written as valid JSON file but instead is written in [https://jsonlines.org/ JSON-Lines]. If an Invalid format is provided traefik willl fallback to <code>CLF</code>.<br />
<br />
===== log.level =====<br />
Default value: "''ERROR''"<br />
<br />
This options sets the verbosity of the traefik logs. Valid values are: <code>DEBUG</code>, <code>INFO</code>, <code>WARN</code>, <code>ERROR</code>, <code>FATAL</code> & <code>PANIC</code><br />
<br />
==== Example Configuration File (YML) ====<br />
<br />
<pre><br />
api:<br />
dashboard: true<br />
insecure: true<br />
<br />
entryPoints:<br />
web:<br />
address: ":80"<br />
websecure:<br />
address: ":443"<br />
<br />
providers:<br />
docker:<br />
network: "traefik"<br />
<br />
accesslog:<br />
filepath: "/opt/access.log"<br />
<br />
log:<br />
filepath: "/opt/traefik.log"<br />
</pre></div>Timonhttps://wiki.its-treason.com/index.php?title=Certbot&diff=10Certbot2021-12-06T20:53:18Z<p>Timon: /* Retriving a Certificate */</p>
<hr />
<div>The Certbot is used the issue LetsEncrypt SSL-Certificates<br />
<br />
== Install ==<br />
Certbot '''must''' installed using the Snap-Store.<br />
<br />
Make sure the certbot is not installed using Apt:<br />
<br />
<code>sudo apt remove certbot</code><br />
<br />
Ensure the latest Snap version is installed:<br />
<br />
<code>sudo snap install core; sudo snap refresh core</code><br />
<br />
Install the Certbot, make sure to use the <code>--classic</code> flag<br />
<br />
<code>sudo snap install --classic certbot</code><br />
<br />
Link the certbot binary to a path thats in the $PATH variabel<br />
<br />
<code>sudo ln -s /snap/bin/certbot /usr/bin/certbot</code><br />
<br />
== Retrieving a Certificate ==<br />
To create an Certificate for <code>example.com</code> <br />
<br />
<code>sudo certbot certonly --nginx --agree-tos -n -d example.com</code><br />
<br />
* <code>--nginx</code>: Use Local installed nginx for the Authentication-Challange, see Challanges for other ways to authenticate<br />
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option<br />
* <code>-n</code>: Non-Interactive, do not prompt for anything<br />
* <code>-d <DOMAIN></code>: Domain to create the Certificate for<br />
<br />
The Certificate will be saved under:<br />
<br />
* <code>/etc/letsencrypt/live/<DOMAIN>/fullchain.pem</code>: Certificate<br />
* <code>/etc/letsencrypt/live/<DOMAIN>/privkey.pem</code>: Private key<br />
<br />
== Renewing Certificates ==<br />
To renew all Certificates use:<br />
<br />
<code>sudo certbot renew --nginx --agree-tos -n</code><br />
<br />
* <code>--nginx</code>: Use Local installed nginx for the Authentication-Challange, see Challanges for other ways to authenticate<br />
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option<br />
* <code>-n</code>: Non-Interactive, do not prompt for anything<br />
* <code>-d <DOMAIN></code>: Optional, Domain to renew the Certificate for<br />
<br />
Certificates will be updated if there expire in less than 30 days<br />
<br />
== Challanges ==<br />
To validate that you own a Domain you must complete a Challange using one of the following method<br />
<br />
=== Nginx ===<br />
If a Nginx is running localy and serving for your domain you can simply use the <code>--nginx</code> option and certbot will use Nginx for the Challange and should complete it without stopping the Nginx.<br />
<br />
=== Apache ===<br />
If a Apache is running localy and serving for your domain you can simply use the <code>--apache</code> option and certbot will use Apache for the Challange and should complete it without stopping the Apache server.<br />
<br />
=== Standalone ===<br />
Certbot will start a Webserver on Port 80 and will try to serve a file containg a verification code. If the Certbot can find that file, the challange will be completed.<br />
<br />
=== Webroot ===<br />
Using the <code>--webroot <Path></code> the Certbot will put files under the given directory und the given directory and try to access them.</div>Timonhttps://wiki.its-treason.com/index.php?title=Certbot&diff=9Certbot2021-12-06T20:52:58Z<p>Timon: Created page with "The Certbot is used the issue LetsEncrypt SSL-Certificates == Install == Certbot '''must''' installed using the Snap-Store. Make sure the certbot is not installed using Apt: <code>sudo apt remove certbot</code> Ensure the latest Snap version is installed: <code>sudo snap install core; sudo snap refresh core</code> Install the Certbot, make sure to use the <code>--classic</code> flag <code>sudo snap install --classic certbot</code> Link the certbot binary to a pat..."</p>
<hr />
<div>The Certbot is used the issue LetsEncrypt SSL-Certificates<br />
<br />
== Install ==<br />
Certbot '''must''' installed using the Snap-Store.<br />
<br />
Make sure the certbot is not installed using Apt:<br />
<br />
<code>sudo apt remove certbot</code><br />
<br />
Ensure the latest Snap version is installed:<br />
<br />
<code>sudo snap install core; sudo snap refresh core</code><br />
<br />
Install the Certbot, make sure to use the <code>--classic</code> flag<br />
<br />
<code>sudo snap install --classic certbot</code><br />
<br />
Link the certbot binary to a path thats in the $PATH variabel<br />
<br />
<code>sudo ln -s /snap/bin/certbot /usr/bin/certbot</code><br />
<br />
== Retriving a Certificate ==<br />
To create an Certificate for <code>example.com</code> <br />
<br />
<code>sudo certbot certonly --nginx --agree-tos -n -d example.com</code><br />
<br />
* <code>--nginx</code>: Use Local installed nginx for the Authentication-Challange, see Challanges for other ways to authenticate<br />
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option<br />
* <code>-n</code>: Non-Interactive, do not prompt for anything<br />
* <code>-d <DOMAIN></code>: Domain to create the Certificate for<br />
<br />
The Certificate will be saved under:<br />
<br />
* <code>/etc/letsencrypt/live/<DOMAIN>/fullchain.pem</code>: Certificate<br />
* <code>/etc/letsencrypt/live/<DOMAIN>/privkey.pem</code>: Private key<br />
<br />
== Renewing Certificates ==<br />
To renew all Certificates use:<br />
<br />
<code>sudo certbot renew --nginx --agree-tos -n</code><br />
<br />
* <code>--nginx</code>: Use Local installed nginx for the Authentication-Challange, see Challanges for other ways to authenticate<br />
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option<br />
* <code>-n</code>: Non-Interactive, do not prompt for anything<br />
* <code>-d <DOMAIN></code>: Optional, Domain to renew the Certificate for<br />
<br />
Certificates will be updated if there expire in less than 30 days<br />
<br />
== Challanges ==<br />
To validate that you own a Domain you must complete a Challange using one of the following method<br />
<br />
=== Nginx ===<br />
If a Nginx is running localy and serving for your domain you can simply use the <code>--nginx</code> option and certbot will use Nginx for the Challange and should complete it without stopping the Nginx.<br />
<br />
=== Apache ===<br />
If a Apache is running localy and serving for your domain you can simply use the <code>--apache</code> option and certbot will use Apache for the Challange and should complete it without stopping the Apache server.<br />
<br />
=== Standalone ===<br />
Certbot will start a Webserver on Port 80 and will try to serve a file containg a verification code. If the Certbot can find that file, the challange will be completed.<br />
<br />
=== Webroot ===<br />
Using the <code>--webroot <Path></code> the Certbot will put files under the given directory und the given directory and try to access them.</div>Timonhttps://wiki.its-treason.com/index.php?title=Category:Schule&diff=8Category:Schule2021-12-06T16:54:34Z<p>Timon: Created page with "<categorytree> </categorytree>"</p>
<hr />
<div><categorytree><br />
</categorytree></div>Timon