⚠️All content on this website, including text, images, graphics, and other materials, is protected by intellectual property rights and belongs to the respective owner. Reproduction, distribution, or unauthorized use of any content without prior written consent from the rights holder is prohibited.
🧠Keep in Mind: this blog doesn’t have ADS, COOKIES, POP-UPs, Amazon AFFILIATE LINKS, MEMBERSHIP TIERS, SPONSORED ARTICLES or any TRACKING CODE on it. This blog survives only because of donations from Good Samaritans.
📝Contact forms: I don’t have any contact forms on this website.
📧Email: I don’t collect any emails on this website.
📊Analytics: I don’t use Google Analytics or any Analytics program.
🪧Advertising: I don’t use Google AdSense or any Advertising program.
✍️Comments: I don’t allow comments on this blog. Instead, you can join my Synology Discord Server, Facebook Group or Reddit Community.
Please take this the right way. I like that you like my blog about Synology. But, to be honest, that’s as far as it goes. I have no desire to impose on you and zero interest in trying to do anything with your private details. If you need to contact me about any aspect of this Privacy Policy, please use the Contact Page.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
These websites may collect data about you, use cookies, embed additional third-party tracking and monitor your interaction with that embedded content, including tracing your interaction with the embedded content if you have an account and are logged in to that website.
I don’t retain any data.
If you have left comments on this site, (but you are not allowed because comments are deactivated on the mariushosting.com website) you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Nowhere.
“The “Synology” logo are trademarks of Synology, Inc., registered in the Republic of China (Taiwan) and other regions.”
ANYONE WHO USES THE MARIUSHOSTING.COM WEBSITE ALSO BEARS THE RISK THAT THE INFORMATION AND MATERIAL ON IT IS INCOMPLETE, INACCURATE, OUT OF DATE, OR THAT IT DOES NOT MEET THEIR NEEDS AND REQUIREMENTS. Under no circumstances is MARIUSHOSTING.COM responsible for any data loss OR corruption. You are using the mariushosting.com website at your own risk and you are aware of this. A Proper back-up is up to the user.
Why are some files on mariushosting under a password? Some Docker Containers need certain files to work properly. These files are hosted on my NAS at home and are modified by me to work specifically on a Synology NAS. There are usually at least a few lines of code that I change in various ways that make a big difference when it comes to the container working properly on your NAS. In other cases, the original file is modified because there are some things that are not needed at all to make the container work on a NAS and so the file gets cleaned of unnecessary code. You can also find these files elsewhere, but they are not edited like mine, nor tested to work on your NAS. In many cases, even something as small as a comma or number makes the biggest difference. So, any small issue that may appear when installing a container will be owed to using the general file available as it is; on the surface, maybe the original file works, or may appear to work flawlessly, but when something do happens, it’s usually because of it.
Remember that you may very well search for other guides online, but you will be sacrificing your privacy in return. mariushosting does not have any tracking or cookies. Your visit remains 100% anonymous on this site because your privacy is important to me. How free is a site with ads, affiliate marketing links, subscriptions and also donation requests on top of all that? You are producing money for the site owner, giving your data and being asked to support via donations, while this blog survives only because of donations from Good Samaritans.