https://mintarc.com/minthome/api.php?action=feedcontributions&feedformat=atom&user=Tommy 2026-08-04T21:25:41Z User contributions MediaWiki 1.43.9 https://mintarc.com/minthome/index.php?title=Daily_Post_August_04_2026&diff=4255 2026-08-04T01:40:13Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Self-Hosted vs. Cloud Ecosystem: Retaining Data Sovereignty with Open Source<br /> |description= Discover how SME owners can retain true data sovereignty, avoid proprietary vendor lock-in, and build a resilient infrastructure using open-source software and trusted support partners.<br /> |keywords= Self-Hosted vs Cloud, Data Sovereignty, Open Source Infrastructure, SME IT Strategy, FOSS Support, Vendor Lock-In, Managed Open Source, Sovereign Cloud, Data Privacy<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_August_04_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Self-Hosted vs. Cloud Ecosystems=<br /> The dilemma &quot;convenience vs. long-term Autonomy&quot;...for SME owners, every technology decision is a direct balancing act between immediate convenience and long-term operating costs. In the early growth phase of a business, commercial public cloud platforms have an seet deal: enterprise-grade tools, high availability, and instant global deployment for a small monthly subscription. However, as an SME scales, the cumulative cost of monthly software-as-a-service seats, data transfer fees, and proprietary cloud infrastructure begins to consume a higher percentage of operating capital. More specifically, reliance on big-tech ecosystems strips business owners of data sovereignty the ability to control where sensitive enterprise data lives, how it is processed, and who holds legal jurisdiction over it. Evaluating self-hosted open-source software against commercial cloud ecosystems is not really just a technical choice for developers; it is a business strategy that determines whether an SME owns its data and processes.<br /> <br /> ==Data Sovereignty and the Vendor Trap==<br /> Data sovereignty refers to the principle that digital information is governed by the laws and legal protections of the country or jurisdiction in which it is physically stored and processed. When an SME relies entirely on major multi-national cloud environments, its customer data, proprietary IP, and financial records are routinely replicated across global infrastructure subject to foreign jurisdictions and shifting terms of service. Beyond legal compliance, commercial cloud models intentionally design &quot;sticky&quot; environments through proprietary API layers and database formats, making data extraction tedious and expensive. Cloud providers routinely offer free data ingress and charging steep egress fees when a company attempts to move its data out. For an SME owner, this financial friction converts operational convenience into long-term vendor lock-in, where price increases must be absorbed because migrating away feels prohibitively hard.<br /> <br /> ==Pros, Cons, and the Cloud Advocate View==<br /> To make an informed decision, an SME owner must objectively evaluate the genuine benefits and drawbacks of cloud ecosystems. Advocates of commercial cloud environments rightly point out that public cloud platforms eliminate upfront capital expenditure, changing infrastructure costs into predictable recurring operating expenses. The major pros of commercial cloud include zero hardware procurement delays, automatic scaling during usage spikes, managed automated backups, and physical security handled entirely by the provider.<br /> <br /> However, the cons of commercial public cloud are equally significant for a growing SME compounding monthly subscription costs that scale linearly with headcount, unannounced API changes or service deprecations, strict vendor lock-in, and unpredictable data egress fees. Cloud enthusiasts frequently argue that self-hosting open-source software is an outdated trap for small businesses, claiming that managing internal servers creates unnecessary operational friction, diverts focus from core revenue-generating activities, and exposes the company to massive security risks if internal staff miss critical vulnerability patches.<br /> <br /> ==The Case for Open-Source &amp; Self-Hosting Pros, Cons, and Operational Realities==<br /> On the other end of the spectrum, self-hosting open-source software on infrastructure you control restores absolute data sovereignty and long-term cost predictability. The pros of the self-hosted open-source model include complete ownership over data, freedom from license price hikes, infinite customization through open source code, and significantly lower total cost of ownership once a business reaches sustained operational scale. Running open-source systems ensures that an SME can operate independently of third-party platform shut downs or policy shifts.<br /> <br /> However, transitioning to self-hosted open-source software comes with distinct operational hurdles. Initial deployment requires careful architecture design, data migration, and workflow adaptation. Once live, maintaining system uptime, applying security patches, taking regular backups, and managing vulnerabilities require ongoing effort and technical expertise. Relying entirely on a small internal team for these tasks can introduce operational strain and create single points of failure if key technical staff leave the company.<br /> <br /> Despite these challenges, small and medium enterprises are not forced to shoulder this burden entirely on their own. Self-hosting does not require building an expensive, dedicated platform engineering team from scratch. SMEs can bridge the operational gap by partnering with open-source agencies, Managed Service Providers, or open-source companies. These external partners handle daily infrastructure monitoring, maintenance, security hardening, and Service Level Agreements, allowing the business to retain data sovereignty and software flexibility while offloading heavy operational lifting.<br /> <br /> ==&quot;Myths&quot; Addressing Common FOSS Critiques==<br /> It is common to hear ardent cloud supporters label free and open-source software as &quot;insecure,&quot; &quot;unsupported,&quot; or &quot;unviable for serious business.&quot; While these criticisms stem from real operational concerns, they misrepresent modern open-source maturity. Critics frequently conflate open source code with a lack of security, ignoring the fact that open-source platforms are continuously audited by thousands of global developers, whereas proprietary cloud code relies on security through blackbox security.<br /> <br /> The argument that open-source software lacks support is similarly outdated; the open-source ecosystem is backed by extensive enterprise communities, third-party support vendors, and professional consultancy networks. The cost of open-source software is never zero because system maintenance and infrastructure management carry real labor expenses. However, framing FOSS as an irresponsible choice ignores the massive financial risk of allowing a single commercial vendor to hold your business data hostage behind rising subscription tiers.<br /> <br /> ==Managed Open-Source &amp; Sovereign Hybrids==<br /> Fortunately, SME owners do not have to choose between the chaotic overhead of raw self-hosting and the rigid trap of proprietary public clouds. A growing and effective middle ground is the adoption of managed open-source hosting and sovereign hybrid cloud models. Under this strategy, an SME standardizes its applications on open-source software stacks (such as open-source databases, storage tools, and productivity suites) and deploying them through regional hosting providers, localized data centers, or managed private instances.<br /> <br /> This hybrid approach allows small business owners to outsource routine server patching, physical hardware maintenance, and uptime monitoring and ensuring that the underlying software remains open, non-proprietary, and completely portable. If a hosting provider raises rates or underperforms, the SME can export its open-source databases and redeploy the exact same software stack onto a new server provider in hours without rewriting application code or retraining staff.<br /> <br /> For the SME owner, technology infrastructure should be viewed through the lens of long-term risk management and enterprise value creation. And leaning heavily on proprietary public cloud services makes sense for early-stage validation, blindly delegating all data and software systems to commercial tech giants creates existential long-term vulnerabilities. Strategically integrating open-source software and maintaining control over core data repositories, small and medium enterprises can retain data sovereignty, cap their infrastructure expenses, and build a good foundation that no third-party cloud vendor can alter or take away.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_August_04_2026&diff=4254 2026-08-04T01:39:04Z

<p>Tommy: Created page with &quot;=Self-Hosted vs. Cloud Ecosystems= The dilemma &quot;convenience vs. long-term Autonomy&quot;...for SME owners, every technology decision is a direct balancing act between immediate convenience and long-term operating costs. In the early growth phase of a business, commercial public cloud platforms have an seet deal: enterprise-grade tools, high availability, and instant global deployment for a small monthly subscription. However, as an SME scales, the cumulative cost of monthly s...&quot;</p> <hr /> <div>=Self-Hosted vs. Cloud Ecosystems=<br /> The dilemma &quot;convenience vs. long-term Autonomy&quot;...for SME owners, every technology decision is a direct balancing act between immediate convenience and long-term operating costs. In the early growth phase of a business, commercial public cloud platforms have an seet deal: enterprise-grade tools, high availability, and instant global deployment for a small monthly subscription. However, as an SME scales, the cumulative cost of monthly software-as-a-service seats, data transfer fees, and proprietary cloud infrastructure begins to consume a higher percentage of operating capital. More specifically, reliance on big-tech ecosystems strips business owners of data sovereignty the ability to control where sensitive enterprise data lives, how it is processed, and who holds legal jurisdiction over it. Evaluating self-hosted open-source software against commercial cloud ecosystems is not really just a technical choice for developers; it is a business strategy that determines whether an SME owns its data and processes.<br /> <br /> ==Data Sovereignty and the Vendor Trap==<br /> Data sovereignty refers to the principle that digital information is governed by the laws and legal protections of the country or jurisdiction in which it is physically stored and processed. When an SME relies entirely on major multi-national cloud environments, its customer data, proprietary IP, and financial records are routinely replicated across global infrastructure subject to foreign jurisdictions and shifting terms of service. Beyond legal compliance, commercial cloud models intentionally design &quot;sticky&quot; environments through proprietary API layers and database formats, making data extraction tedious and expensive. Cloud providers routinely offer free data ingress and charging steep egress fees when a company attempts to move its data out. For an SME owner, this financial friction converts operational convenience into long-term vendor lock-in, where price increases must be absorbed because migrating away feels prohibitively hard.<br /> <br /> ==Pros, Cons, and the Cloud Advocate View==<br /> To make an informed decision, an SME owner must objectively evaluate the genuine benefits and drawbacks of cloud ecosystems. Advocates of commercial cloud environments rightly point out that public cloud platforms eliminate upfront capital expenditure, changing infrastructure costs into predictable recurring operating expenses. The major pros of commercial cloud include zero hardware procurement delays, automatic scaling during usage spikes, managed automated backups, and physical security handled entirely by the provider.<br /> <br /> However, the cons of commercial public cloud are equally significant for a growing SME compounding monthly subscription costs that scale linearly with headcount, unannounced API changes or service deprecations, strict vendor lock-in, and unpredictable data egress fees. Cloud enthusiasts frequently argue that self-hosting open-source software is an outdated trap for small businesses, claiming that managing internal servers creates unnecessary operational friction, diverts focus from core revenue-generating activities, and exposes the company to massive security risks if internal staff miss critical vulnerability patches.<br /> <br /> ==The Case for Open-Source &amp; Self-Hosting Pros, Cons, and Operational Realities==<br /> On the other end of the spectrum, self-hosting open-source software on infrastructure you control restores absolute data sovereignty and long-term cost predictability. The pros of the self-hosted open-source model include complete ownership over data, freedom from license price hikes, infinite customization through open source code, and significantly lower total cost of ownership once a business reaches sustained operational scale. Running open-source systems ensures that an SME can operate independently of third-party platform shut downs or policy shifts.<br /> <br /> However, transitioning to self-hosted open-source software comes with distinct operational hurdles. Initial deployment requires careful architecture design, data migration, and workflow adaptation. Once live, maintaining system uptime, applying security patches, taking regular backups, and managing vulnerabilities require ongoing effort and technical expertise. Relying entirely on a small internal team for these tasks can introduce operational strain and create single points of failure if key technical staff leave the company.<br /> <br /> Despite these challenges, small and medium enterprises are not forced to shoulder this burden entirely on their own. Self-hosting does not require building an expensive, dedicated platform engineering team from scratch. SMEs can bridge the operational gap by partnering with open-source agencies, Managed Service Providers, or open-source companies. These external partners handle daily infrastructure monitoring, maintenance, security hardening, and Service Level Agreements, allowing the business to retain data sovereignty and software flexibility while offloading heavy operational lifting.<br /> <br /> ==&quot;Myths&quot; Addressing Common FOSS Critiques==<br /> It is common to hear ardent cloud supporters label free and open-source software as &quot;insecure,&quot; &quot;unsupported,&quot; or &quot;unviable for serious business.&quot; While these criticisms stem from real operational concerns, they misrepresent modern open-source maturity. Critics frequently conflate open source code with a lack of security, ignoring the fact that open-source platforms are continuously audited by thousands of global developers, whereas proprietary cloud code relies on security through blackbox security.<br /> <br /> The argument that open-source software lacks support is similarly outdated; the open-source ecosystem is backed by extensive enterprise communities, third-party support vendors, and professional consultancy networks. The cost of open-source software is never zero because system maintenance and infrastructure management carry real labor expenses. However, framing FOSS as an irresponsible choice ignores the massive financial risk of allowing a single commercial vendor to hold your business data hostage behind rising subscription tiers.<br /> <br /> ==Managed Open-Source &amp; Sovereign Hybrids==<br /> Fortunately, SME owners do not have to choose between the chaotic overhead of raw self-hosting and the rigid trap of proprietary public clouds. A growing and effective middle ground is the adoption of managed open-source hosting and sovereign hybrid cloud models. Under this strategy, an SME standardizes its applications on open-source software stacks (such as open-source databases, storage tools, and productivity suites) and deploying them through regional hosting providers, localized data centers, or managed private instances.<br /> <br /> This hybrid approach allows small business owners to outsource routine server patching, physical hardware maintenance, and uptime monitoring and ensuring that the underlying software remains open, non-proprietary, and completely portable. If a hosting provider raises rates or underperforms, the SME can export its open-source databases and redeploy the exact same software stack onto a new server provider in hours without rewriting application code or retraining staff.<br /> <br /> For the SME owner, technology infrastructure should be viewed through the lens of long-term risk management and enterprise value creation. And leaning heavily on proprietary public cloud services makes sense for early-stage validation, blindly delegating all data and software systems to commercial tech giants creates existential long-term vulnerabilities. Strategically integrating open-source software and maintaining control over core data repositories, small and medium enterprises can retain data sovereignty, cap their infrastructure expenses, and build a good foundation that no third-party cloud vendor can alter or take away.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4253 2026-08-04T01:13:05Z

<p>Tommy: /* August 2026 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年8月===<br /> *[[Daily_Post_Aug_03_2026JP|ハイブリッド仮想化のためのオブザーバビリティ・スタック8/03/2026]]<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> *[[Daily_Post_July_23_2026JP|LXDからIncusへの移行：オープンソース・システムコンテナの新たな標準 7/23/2026]]<br /> *[[Daily_Post_July_24_2026JP|単一のCLIからのコンテナと仮想マシンの統合管理 7/27/2026]]<br /> *[[Daily_Post_July_30_2026JP|Incusにおけるネットワーク高度化：カスタムLinuxブリッジとOVN (Open Virtual Network) 7/30/2026]]<br /> <br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===August 2026===<br /> *[[Daily_Post_August_03_2026|Daily Post August 03 2026 - Monitoring Proxmox &amp; Incus]]<br /> *[[Daily_Post_August_04_2026|Daily Post August 04 2026 - Self-Hosted vs. Cloud Ecosystems]]<br /> <br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> *[[Daily_Post_July_23_2026|Daily Post July 23 2026 - Migrating from LXD to Incus]]<br /> *[[Daily_Post_July_24_2026|Daily Post July 24 2026 - Managing Containers and Virtual Machines from One CLI]]<br /> *[[Daily_Post_July_27_2026|Daily Post July 27 2026 - Incus Networking OVN (Open Virtual Network) and Custom Bridges]]<br /> *[[Daily_Post_July_28_2026|Daily Post July 28 2026 - Incus Storage Pools using ZFS and Btrfs for Snapshots]]<br /> *[[Daily_Post_July_30_2026|Daily Post July 30 2026 - Nested virtualization]]<br /> *[[Daily_Post_July_31_2026|Daily Post July 31 2026 - Incus and Visual Management]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_August_03_2026&diff=4248 2026-08-03T01:36:40Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Monitoring Proxmox &amp; Incus with InfluxDB and Grafana<br /> |description= Learn how to build a unified observability stack for hybrid virtualization. Discover how to stream Proxmox VE and Incus container telemetry into InfluxDB time-series buckets and visualize performance with Grafana dashboards.<br /> |keywords= Proxmox monitoring, Incus containers, InfluxDB, Grafana dashboards, Telegraf, hybrid virtualization, open source observability, Linux server monitoring, time-series telemetry<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_August_03_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> ==Observability Stack for Hybrid Virtualization==<br /> Infrastructure environments frequently pair full virtualization with container orchestrators to maximize compute efficiency and operational flexibility. Running Proxmox Virtual Environment alongside Incus creates a good, open platform for managing both virtual machines and system containers. However, maintaining complete operational visibility across host hypervisors, kernel-based virtual machines, and unprivileged system containers presents a monitoring challenge. You need centralized insights into CPU saturation, memory allocation, storage throughput, and network traffic across both paradigms without incurring heavy telemetry overhead.<br /> <br /> Deploying a dedicated observability pipeline built around InfluxDB and Grafana addresses this requirement by establishing a scalable time-series telemetry hub. InfluxDB is good at collecting, indexing, and storing high-frequency time-series metrics generated by hypervisors and container engines. And, Grafana provides the flexible visualization layer needed to transform raw metric streams into operational dashboards. Combining Proxmox host and guest metrics alongside Incus container telemetry within a single time-series database, system administrators gain real-time visibility and historical trend analysis across their entire hybrid compute estate.<br /> <br /> ==InfluxDB and Grafana Telemetry Pipeline==<br /> The monitoring pipeline relies on a clean decoupling of metric emission, data ingestion, and visualization layers. At the foundation sits InfluxDB, functioning as the central time-series data store. Proxmox VE natively implements a metric server push mechanism that streams host and guest telemetry directly into InfluxDB over HTTP or UDP using the Line Protocol. This eliminates the need to install third-party background agents on the underlying Proxmox hypervisor nodes, preserving host stability and reducing configuration drift.<br /> <br /> Incus containers and hosts complement this push architecture through agent-based collection agents like Telegraf or native telemetry exporters. Because Incus leverages Linux containers to deliver OS-level virtualization, monitoring requires capturing cgroup v2 resource limits and host-level kernel metrics. Telegraf instances running within administrative containers or alongside the Incus daemon capture detailed process, network, and storage stats, forwarding them directly to InfluxDB buckets. Grafana then queries these centralized InfluxDB buckets using Flux or SQL-like query syntaxes, aggregating metric streams from both virtualization engines onto single dashboards.<br /> <br /> ==Proxmox VE Native Metric Forwarding==<br /> Integrating Proxmox VE into InfluxDB is straightforward thanks to the built-in Metric Server feature available directly within the Proxmox Datacenter interface. Navigating to the Datacenter configuration panel allows administrators to register a new InfluxDB backend by specifying the database endpoint, port, organization, target bucket, and API authentication token. Proxmox automatically formats system metrics including node CPU load, memory utilization, ZFS pool states, LXC container resources, and QEMU virtual machine disk activity into InfluxDB line protocol and pushes updates at configurable intervals.<br /> <br /> This direct native integration give significant operational advantages for cluster management. Metric collection happens asynchronously within the Proxmox cluster stack, ensuring that telemetry collection does not degrade management tasks or virtual machine performance. And, because Proxmox tags all outgoing telemetry with node names, virtual machine identifiers, and guest names, administrators receive structured time-series data out of the box. This metadata enables immediate granular filtering inside Grafana without requiring custom tag transformation scripts or manual metric labeling<br /> <br /> ==Telemetry Agent Deployment for Incus Container Environments==<br /> Proxmox handles its own hypervisor-level metric streaming, Incus infrastructure requires a targeted collection approach to capture fine-grained container performance statistics. Incus exposes detailed runtime metrics via its REST API and open telemetry endpoints. Deploying Telegraf across Incus host nodes provides an adaptable bridge to extract these container metrics and ship them into InfluxDB. Using Telegraf's system and cgroup plugins, administrators can gather real-time data regarding memory usage, CPU throttle limits, network interface throughput, and block I/O performance for every active Incus instance.<br /> <br /> For environments requiring deeper application-level visibility inside individual Incus containers, Telegraf instances or Prometheus node exporters can be installed within container templates. When paired with InfluxDB, these agents push interior guest metrics such as systemd service health, database buffer pools, and custom application runtimes alongside the hypervisor's exterior view of container resource usage. This dual perspective allows system administrators to correlate external resource pressure observed by the host with internal process activity occurring inside the Incus container.<br /> <br /> ==InfluxDB Data Modeling and Retention==<br /> Maintaining an InfluxDB deployment requires careful schema design and retention policy management. Time-series databases can rapidly grow in disk footprint when ingest rates from multi-node Proxmox clusters and dozens of Incus containers reach thousands of points per second. Creating dedicated InfluxDB buckets with tailored retention periods ensures that high-frequency operational metrics do not exhaust system storage while maintaining sufficient historical data for long-term capacity planning.<br /> <br /> A recommended architecture utilizes multiple tiered buckets based on data granularity. Raw, high-resolution metrics collected every ten seconds can be directed to a short-term operational bucket with a retention window of fourteen to thirty days. InfluxDB task engines can then run downsampling scripts that aggregate high-frequency raw points into hourly averages, storing the consolidated data in a long-term retention bucket retained for several years. This tiered strategy preserves granular troubleshooting capability during active incidents and drastically reducing long-term disk consumption for multi-year usage forecasting.<br /> <br /> ==Grafana Visualizations and Dashboards==<br /> This serves as the visual orchestration layer that brings Proxmox and Incus telemetry together into meaningful, actionable displays. When building dashboards for hybrid hypervisor environments, structuring views around high-level cluster health before drilling down into specific workload metrics provides the best operational workflow. Top-level dashboard panels should highlight aggregate compute capacity, cluster-wide memory usage, storage pool headroom, and active alert conditions.<br /> <br /> Below the executive summary level, specialized dashboard rows should segregate Proxmox hypervisor nodes, QEMU virtual machines, and Incus system containers. Variables in Grafana allow operators to dynamically filter metrics by cluster node, environment tag, or individual guest ID. Time-series graphs plotting CPU usage against allocation limits quickly reveal overcommitted host nodes, at the same time heatmaps of storage I/O latency highlight noisy-neighbor containers before they impact adjacent workloads. Incorporating single-stat gauge panels alongside historical trend graphs equips engineering teams to make diagnostic decisions during performance anomalies.<br /> <br /> ==Alerting and Operational Maintenance==<br /> A mature monitoring stack really changes passive telemetry visualization into a proactive incident prevention platform. Grafana features a combinded alerting system capable of evaluating complex queries against InfluxDB data sources in real time. Administrators can define alert rules targeting failure indicators, such as sustained high CPU throttle rates on Incus containers, ZFS pool fragmentation on Proxmox hosts, or impending storage exhaustion across virtual disks. Alerts can be routed directly to messaging channels, ticketing platforms, or pager systems based on severity.<br /> <br /> Long-term success with this monitoring architecture depends on continuous maintenance of the telemetry infrastructure itself. Monitoring the resource usage of the InfluxDB and Grafana instances ensures that the observability stack remains responsive during major network or hypervisor disruptions. Applying systematic updates to Grafana dashboards, maintaining security tokens for metric push endpoints, and periodically auditing storage usage across InfluxDB buckets helps a reliable, monitoring pipeline capable of scaling alongside expanding Proxmox and Incus environments.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_August_03_2026&diff=4247 2026-08-03T01:34:46Z

<p>Tommy: Created page with &quot;==Observability Stack for Hybrid Virtualization== Infrastructure environments frequently pair full virtualization with container orchestrators to maximize compute efficiency and operational flexibility. Running Proxmox Virtual Environment alongside Incus creates a good, open platform for managing both virtual machines and system containers. However, maintaining complete operational visibility across host hypervisors, kernel-based virtual machines, and unprivileged system...&quot;</p> <hr /> <div>==Observability Stack for Hybrid Virtualization==<br /> Infrastructure environments frequently pair full virtualization with container orchestrators to maximize compute efficiency and operational flexibility. Running Proxmox Virtual Environment alongside Incus creates a good, open platform for managing both virtual machines and system containers. However, maintaining complete operational visibility across host hypervisors, kernel-based virtual machines, and unprivileged system containers presents a monitoring challenge. You need centralized insights into CPU saturation, memory allocation, storage throughput, and network traffic across both paradigms without incurring heavy telemetry overhead.<br /> <br /> Deploying a dedicated observability pipeline built around InfluxDB and Grafana addresses this requirement by establishing a scalable time-series telemetry hub. InfluxDB is good at collecting, indexing, and storing high-frequency time-series metrics generated by hypervisors and container engines. And, Grafana provides the flexible visualization layer needed to transform raw metric streams into operational dashboards. Combining Proxmox host and guest metrics alongside Incus container telemetry within a single time-series database, system administrators gain real-time visibility and historical trend analysis across their entire hybrid compute estate.<br /> <br /> ==InfluxDB and Grafana Telemetry Pipeline==<br /> The monitoring pipeline relies on a clean decoupling of metric emission, data ingestion, and visualization layers. At the foundation sits InfluxDB, functioning as the central time-series data store. Proxmox VE natively implements a metric server push mechanism that streams host and guest telemetry directly into InfluxDB over HTTP or UDP using the Line Protocol. This eliminates the need to install third-party background agents on the underlying Proxmox hypervisor nodes, preserving host stability and reducing configuration drift.<br /> <br /> Incus containers and hosts complement this push architecture through agent-based collection agents like Telegraf or native telemetry exporters. Because Incus leverages Linux containers to deliver OS-level virtualization, monitoring requires capturing cgroup v2 resource limits and host-level kernel metrics. Telegraf instances running within administrative containers or alongside the Incus daemon capture detailed process, network, and storage stats, forwarding them directly to InfluxDB buckets. Grafana then queries these centralized InfluxDB buckets using Flux or SQL-like query syntaxes, aggregating metric streams from both virtualization engines onto single dashboards.<br /> <br /> ==Proxmox VE Native Metric Forwarding==<br /> Integrating Proxmox VE into InfluxDB is straightforward thanks to the built-in Metric Server feature available directly within the Proxmox Datacenter interface. Navigating to the Datacenter configuration panel allows administrators to register a new InfluxDB backend by specifying the database endpoint, port, organization, target bucket, and API authentication token. Proxmox automatically formats system metrics including node CPU load, memory utilization, ZFS pool states, LXC container resources, and QEMU virtual machine disk activity into InfluxDB line protocol and pushes updates at configurable intervals.<br /> <br /> This direct native integration give significant operational advantages for cluster management. Metric collection happens asynchronously within the Proxmox cluster stack, ensuring that telemetry collection does not degrade management tasks or virtual machine performance. And, because Proxmox tags all outgoing telemetry with node names, virtual machine identifiers, and guest names, administrators receive structured time-series data out of the box. This metadata enables immediate granular filtering inside Grafana without requiring custom tag transformation scripts or manual metric labeling<br /> <br /> ==Telemetry Agent Deployment for Incus Container Environments==<br /> Proxmox handles its own hypervisor-level metric streaming, Incus infrastructure requires a targeted collection approach to capture fine-grained container performance statistics. Incus exposes detailed runtime metrics via its REST API and open telemetry endpoints. Deploying Telegraf across Incus host nodes provides an adaptable bridge to extract these container metrics and ship them into InfluxDB. Using Telegraf's system and cgroup plugins, administrators can gather real-time data regarding memory usage, CPU throttle limits, network interface throughput, and block I/O performance for every active Incus instance.<br /> <br /> For environments requiring deeper application-level visibility inside individual Incus containers, Telegraf instances or Prometheus node exporters can be installed within container templates. When paired with InfluxDB, these agents push interior guest metrics such as systemd service health, database buffer pools, and custom application runtimes alongside the hypervisor's exterior view of container resource usage. This dual perspective allows system administrators to correlate external resource pressure observed by the host with internal process activity occurring inside the Incus container.<br /> <br /> ==InfluxDB Data Modeling and Retention==<br /> Maintaining an InfluxDB deployment requires careful schema design and retention policy management. Time-series databases can rapidly grow in disk footprint when ingest rates from multi-node Proxmox clusters and dozens of Incus containers reach thousands of points per second. Creating dedicated InfluxDB buckets with tailored retention periods ensures that high-frequency operational metrics do not exhaust system storage while maintaining sufficient historical data for long-term capacity planning.<br /> <br /> A recommended architecture utilizes multiple tiered buckets based on data granularity. Raw, high-resolution metrics collected every ten seconds can be directed to a short-term operational bucket with a retention window of fourteen to thirty days. InfluxDB task engines can then run downsampling scripts that aggregate high-frequency raw points into hourly averages, storing the consolidated data in a long-term retention bucket retained for several years. This tiered strategy preserves granular troubleshooting capability during active incidents and drastically reducing long-term disk consumption for multi-year usage forecasting.<br /> <br /> ==Grafana Visualizations and Dashboards==<br /> This serves as the visual orchestration layer that brings Proxmox and Incus telemetry together into meaningful, actionable displays. When building dashboards for hybrid hypervisor environments, structuring views around high-level cluster health before drilling down into specific workload metrics provides the best operational workflow. Top-level dashboard panels should highlight aggregate compute capacity, cluster-wide memory usage, storage pool headroom, and active alert conditions.<br /> <br /> Below the executive summary level, specialized dashboard rows should segregate Proxmox hypervisor nodes, QEMU virtual machines, and Incus system containers. Variables in Grafana allow operators to dynamically filter metrics by cluster node, environment tag, or individual guest ID. Time-series graphs plotting CPU usage against allocation limits quickly reveal overcommitted host nodes, at the same time heatmaps of storage I/O latency highlight noisy-neighbor containers before they impact adjacent workloads. Incorporating single-stat gauge panels alongside historical trend graphs equips engineering teams to make diagnostic decisions during performance anomalies.<br /> <br /> ==Alerting and Operational Maintenance==<br /> A mature monitoring stack really changes passive telemetry visualization into a proactive incident prevention platform. Grafana features a combinded alerting system capable of evaluating complex queries against InfluxDB data sources in real time. Administrators can define alert rules targeting failure indicators, such as sustained high CPU throttle rates on Incus containers, ZFS pool fragmentation on Proxmox hosts, or impending storage exhaustion across virtual disks. Alerts can be routed directly to messaging channels, ticketing platforms, or pager systems based on severity.<br /> <br /> Long-term success with this monitoring architecture depends on continuous maintenance of the telemetry infrastructure itself. Monitoring the resource usage of the InfluxDB and Grafana instances ensures that the observability stack remains responsive during major network or hypervisor disruptions. Applying systematic updates to Grafana dashboards, maintaining security tokens for metric push endpoints, and periodically auditing storage usage across InfluxDB buckets helps a reliable, monitoring pipeline capable of scaling alongside expanding Proxmox and Incus environments.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4246 2026-08-03T01:19:05Z

<p>Tommy: /* English */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> *[[Daily_Post_July_23_2026JP|LXDからIncusへの移行：オープンソース・システムコンテナの新たな標準 7/23/2026]]<br /> *[[Daily_Post_July_24_2026JP|単一のCLIからのコンテナと仮想マシンの統合管理 7/27/2026]]<br /> *[[Daily_Post_July_30_2026JP|Incusにおけるネットワーク高度化：カスタムLinuxブリッジとOVN (Open Virtual Network) 7/30/2026]]<br /> <br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===August 2026===<br /> *[[Daily_Post_August_03_2026|Daily Post August 03 2026 - Monitoring Proxmox &amp; Incus]]<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> *[[Daily_Post_July_23_2026|Daily Post July 23 2026 - Migrating from LXD to Incus]]<br /> *[[Daily_Post_July_24_2026|Daily Post July 24 2026 - Managing Containers and Virtual Machines from One CLI]]<br /> *[[Daily_Post_July_27_2026|Daily Post July 27 2026 - Incus Networking OVN (Open Virtual Network) and Custom Bridges]]<br /> *[[Daily_Post_July_28_2026|Daily Post July 28 2026 - Incus Storage Pools using ZFS and Btrfs for Snapshots]]<br /> *[[Daily_Post_July_30_2026|Daily Post July 30 2026 - Nested virtualization]]<br /> *[[Daily_Post_July_31_2026|Daily Post July 31 2026 - Incus and Visual Management]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_31_2026&diff=4245 2026-07-31T01:41:12Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= GUI Management for Incus: Navigating the Web UI and Third-Party Tools<br /> |description= Explore GUI management for Incus, from the native web UI and incus webui command to third-party control panels and multi-node management tools.<br /> |keywords= Incus, Incus Web UI, Graphical User Interface, Linux Containers, LXC, Virtual Machines, System Administration, Infrastructure Management, OpenID Connect, Web Console<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_31_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> <br /> =Incus and Visual Management=<br /> Lets recap...designed to deliver a public cloud-like experience on private infrastructure, Incus handles system containers, application containers, and full QEMU-based virtual machines under a single, unified REST API. System administrators and DevOps engineers frequently rely on the incus command-line tool for day-to-day operations, graphical user interfaces have become increasingly valued. Visual management tools reduce the friction of inspecting node health, managing virtual networks, observing storage utilization, and granting container access to team members who may not be comfortable navigating terminal workflows.<br /> <br /> The shift toward graphical management in the Incus ecosystem reflects a broader industry pattern where infrastructure managers cater to hybrid teams. Developers, quality assurance engineers, and operations technicians need to spin up instances, review logs, attached volumes, or open interactive shell sessions without memorizing extensive command flags. Graphical management tools satisfy this demand by converting multi-step CLI operations into intuitive, visual workflows, making Incus more accessible in small business environments, and enterprise data centers alike.<br /> <br /> ==The Incus Web UI Ecosystem==<br /> The graphical tool is tied to its architecture and history. Rather than building a web frontend from scratch, the Incus community adapted and maintained packages derived from the established LXD browser interface, making them compatible with the Incus daemon. In many distribution repositories, this interface is packaged under names like incus-ui or incus-ui-canonical. Once installed, administrators can expose the API server over HTTPS and authenticate using client TLS certificates or OpenID Connect identity providers, ensuring security for remote administration.<br /> <br /> To solve the historical friction of client certificate generation and browser importing, Incus releases introduced simplified access mechanisms. Executing incus webui in the command line, the Incus client creates a localized, temporary proxy server on the loopback interface protected by an ephemeral authorization token. This allows administrators to launch a secure web browser session instantly without manually configuring network listeners or managing browser keystores, giving a balance between convenience and strict security controls.<br /> <br /> ==Features and Operational Workflows in the Native Web UI==<br /> Navigating the native Incus web interface is a dashboard structured around core infrastructure primitives: instances, images, profiles, storage pools, networks, and projects. The primary instances view aggregates both lightweight Linux containers and full-fledged virtual machines into a clear list. From this central screen, operators can inspect state indicators, CPU usage, memory consumption, IP address assignments, and storage footprints at a glance, removing the need to run iterative status commands across multiple terminal tabs.<br /> <br /> Instance lifecycle management within the web interface is straightforward and immediate. Users can launch new containers or virtual machines by selecting base images from default public remotes such as images.linuxcontainers.org or from local custom repositories. Configuration profiles, which define network attachments, resource limits, and cloud-init parameters, can be attached or modified visually before creation. Operators can perform immediate operational tasks such as starting, stopping, restarting, pausing, or deleting instances directly through context menus.<br /> <br /> Beyond basic instance control, the web UI provides visibility into storage and networking abstractions. Storage pool management submenus display total capacity, allocated volumes, and snapshot histories across backends like ZFS, Btrfs, LVM, or Ceph. Networking screens allow administrators to inspect bridge devices, overlay networks, managed DHCP leases, and firewall rules. For granular multi-tenancy, the project switching dropdown allows users to isolate environments into logically segregated domains, ensuring that development, staging, and production assets remain neatly partitioned.<br /> <br /> Direct instance interaction is another major highlight of the integrated web dashboard. Leveraging WebSocket connections, the interface has an in-browser terminal console that connects straight into a container's root shell or user environment without needing SSH keys pre-installed. For virtual machines running graphical operating systems or head-less servers requiring low-level access, the web interface integrates SPICE and VNC display streams, enabling interactive desktop sessions directly inside the browser window.<br /> <br /> ==Third-Party Tools and Custom Management Platforms==<br /> The native web UI handles direct node administration with finesse, the broader community has developed third-party tools to address specialized orchestration and multi-node requirements. Lightweight web management tools such as LXConsole offer alternative, containerized web portals that connect to Incus daemons over the standard REST API. These tools appeal to administrators who prefer running management software inside isolated application containers rather than modifying host system packages or binding host web services directly.<br /> <br /> For organizations operating across distributed infrastructure, multi-server management platforms and cloud control panels extend Incus capabilities significantly. Tools built around the Incus REST API allow engineering teams to consolidate multiple standalone hosts and Incus clusters into a unified pane of glass. These community-driven management panels frequently add features beyond the scope of a host-level UI, such as centralized user access controls, role-based permissions, automated backup schedules across multiple hosts, and billing or resource quota tracking tailored for small hosting providers and university lab environments.<br /> <br /> Automation and Infrastructure as Code integrations complement graphical tools by providing structured deployment models. Providers for Terraform and OpenTofu allow teams to define Incus instances, networks, and storage pools declaratively, while Ansible connection plugins facilitate software provisioning across launched environments. In many organizations, administrators use graphical interfaces primarily for real-time monitoring, visual inspection, and interactive troubleshooting, delegating initial provisioning and configuration tasks to these automated pipelines.<br /> <br /> ==Choosing the Right Interface Strategy for Your Infrastructure==<br /> Selecting the appropriate graphical management strategy for Incus depends entirely on deployment scale, security requirements, and team operational habits. For single-host installations, home labs, or development workstations, relying on the built-in incus webui browser launcher provides speed with zero static exposure to external networks. Because the temporary web server binds strictly to the loopback address and authenticates via single-use tokens, it eliminates unauthorized exposure while offering a complete graphical suite for inspecting system behavior.<br /> <br /> In enterprise data centers or shared multi-user environments, deploying the full web interface behind centralized identity infrastructure is the recommended path. Binding the Incus API daemon to a secure internal interface and authenticating users via OpenID Connect guarantees that access logs, multi-factor authentication, and centralized user revocation policies are strictly enforced. Combining this approach with Incus projects ensures that individual departments or tenant groups only see and manage the specific resources assigned to their authorization scope.<br /> <br /> Graphical interfaces should be viewed as an extension of the foundation provided by Incus. Rather than replacing the command-line interface or API-driven automation, web UIs and third-party dashboards observability, lower the entry barrier for new operators, and streamline day-to-day administrative tasks. Understanding the strengths of both native web interfaces and community management platforms, administrators can construct an efficient, secure, and highly flexible management workflow tailored precisely to their infrastructure needs.<br /> <br /> ==What would a transition from Proxmox to Incus GUI be like==<br /> For an experienced Proxmox VE user, transitioning to the Incus Web UI feels less like learning a completely new paradigm and more like switching from a fully integrated virtualization suite to a clean, modular engine built specifically around the Linux kernel.<br /> <br /> Proxmox and Incus share a core foundation both rely heavily on LXC for system containers and QEMU/KVM for virtual machines but their operational philosophies and visual management tools differ significantly.<br /> <br /> ===1. Unified Node vs. Modular Service===<br /> In Proxmox, the web interface is a monolithic management layer tied directly to pve-cluster, corosync, and custom Proxmox daemons. Proxmox controls the entire hypervisor environment, from storage formatting and network bridging to firewalling and clustering rules.<br /> <br /> Incus, operates as a single, lightweight system daemon driven entirely by a well-documented REST API. The Incus Web UI is not an embedded operating system control panel like Proxmox's web interface; it is a decoupled single-page web application that communicates with the Incus daemon over HTTPS.<br /> <br /> For a Proxmox user, this distinction means the Incus interface feels much lighter and faster, but it also delegates host-level tasks (like system updating, base OS disk partitioning, or raw ZFS pool creation) back to the underlying Linux host OS rather than handling them within the UI.<br /> <br /> ===2.Datacenter Tree vs. Projects===<br /> The layout of the two interfaces requires the biggest mental shift:<br /> <br /> *Proxmox uses a strict hierarchical tree view on the left navigation panel (Datacenter -&gt; Node -&gt; Storage/Guest). Every VM and container is immediately visible under its assigned cluster node, identified primarily by a numerical VM ID (for example 100 (web-server)).<br /> <br /> *Incus abandons numerical IDs in favor of unique string names (for example web-server) and replaces the global datacenter tree with Projects.<br /> <br /> In the Incus UI, multi-tenancy and resource grouping are built around these Projects. Instead of browsing a tree of nodes, you use a top-level dropdown to select your current Project (default, staging, production). The UI then displays only the instances, networks, profiles, and storage volumes belonging to that specific project context.<br /> <br /> If you are running an Incus Cluster, instances across different physical nodes are presented within the same project view, eliminating the need to click into individual node sub-trees just to find a running container.<br /> <br /> ===3. Profiles vs. Hardware Tab Configurations===<br /> In Proxmox, you configure guest settings directly on the individual VM or container by adjusting options in its dedicated Hardware and Options tabs. Proxmox supports Cloud-Init templates, creating reusable base configurations across multiple guests often requires cloning pre-configured templates.<br /> <br /> Incus handles configuration through Profiles, which function much like composable infrastructure templates:<br /> <br /> *A Profile defines resource limits (CPU, RAM), device mounts, network attachments, and Cloud-Init user-data scripts.<br /> <br /> *Multiple profiles can be stacked on a single instance (for example, applying both a small-instance profile for CPU/RAM limits and a routed-net profile for network settings).<br /> <br /> *Modifying a profile in the Incus Web UI instantly updates all containers and VMs linked to that profile across the entire node or cluster.<br /> <br /> A Proxmox user adapting to Incus will quickly find that defining profiles upfront drastically reduces manual work when spinning up new environments compared to setting hardware parameters on individual guests.<br /> <br /> ===4. Networking and Storage Conceptual Differences===<br /> '''Networking'''<br /> Proxmox relies heavily on standard Linux bridges (vmbr0, vmbr1), Open vSwitch, and direct VLAN tagging configured on network interfaces within the web UI.<br /> <br /> Incus simplifies this by providing managed network types natively through the UI, primarily using built-in Linux bridges with automatic DHCP/DNS management (incusbr0) or OVN (Open Virtual Network) for advanced multi-host overlay networks and software-defined routing. Setting up isolated networks or routed containers in Incus often requires fewer manual host configuration steps than configuring SDN or custom bridge interfaces in Proxmox.<br /> <br /> '''Storage'''<br /> In Proxmox, storage is configured globally under Datacenter -&gt; Storage, mapping backends (ZFS, LVM-thin, Ceph, NFS) to specific guest usage roles (disk images vs. ISOs).<br /> <br /> Incus abstracts storage into Storage Pools. Within the Incus UI, a single storage pool (backed by ZFS, Btrfs, LVM, or Ceph) holds both instance root disks and custom storage volumes. Incus treats custom storage volumes as first-class primitives meaning you can easily create a standalone storage volume in the UI and attach, detach, or share it across containers without manipulating underlying host block devices.<br /> <br /> ===5. Console Access and Image Workflow===<br /> *Console Access Proxmox defaults to noVNC and SPICE for virtual machines and container shells. Incus provides an interactive, low-latency WebSocket terminal directly in the web browser for container root shells, alongside SPICE/VNC rendering for full virtual machines.<br /> <br /> *Image Management Proxmox users are accustomed to manually downloading ISO images or downloading LXC templates from the Proxmox storage menu. Incus uses Remote Image Registries. From the Incus Web UI, launching an instance allows you to search and pull live images directly from public remotes (such as images.linuxcontainers.org) without needing to pre-download template files to local storage first.<br /> <br /> <br /> If you are moving from Proxmox to Incus, think of Incus as a more API-first container and VM hypervisor.<br /> <br /> And Proxmox excels as a turnkey, hyper-converged replacement for traditional enterprise virtualization stacks (like VMware vSphere), Incus excels at rapid container deployment, clean API integrations, and flexible, profile-driven workflows. Once you get used to navigating by Projects and driving configurations through Profiles, managing instances in the Incus Web UI feels exceptionally fast and lightweight.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_31_2026&diff=4244 2026-07-31T01:40:14Z

<p>Tommy: /* 5. Console Access and Image Workflow */</p> <hr /> <div>=Incus and Visual Management=<br /> Lets recap...designed to deliver a public cloud-like experience on private infrastructure, Incus handles system containers, application containers, and full QEMU-based virtual machines under a single, unified REST API. System administrators and DevOps engineers frequently rely on the incus command-line tool for day-to-day operations, graphical user interfaces have become increasingly valued. Visual management tools reduce the friction of inspecting node health, managing virtual networks, observing storage utilization, and granting container access to team members who may not be comfortable navigating terminal workflows.<br /> <br /> The shift toward graphical management in the Incus ecosystem reflects a broader industry pattern where infrastructure managers cater to hybrid teams. Developers, quality assurance engineers, and operations technicians need to spin up instances, review logs, attached volumes, or open interactive shell sessions without memorizing extensive command flags. Graphical management tools satisfy this demand by converting multi-step CLI operations into intuitive, visual workflows, making Incus more accessible in small business environments, and enterprise data centers alike.<br /> <br /> ==The Incus Web UI Ecosystem==<br /> The graphical tool is tied to its architecture and history. Rather than building a web frontend from scratch, the Incus community adapted and maintained packages derived from the established LXD browser interface, making them compatible with the Incus daemon. In many distribution repositories, this interface is packaged under names like incus-ui or incus-ui-canonical. Once installed, administrators can expose the API server over HTTPS and authenticate using client TLS certificates or OpenID Connect identity providers, ensuring security for remote administration.<br /> <br /> To solve the historical friction of client certificate generation and browser importing, Incus releases introduced simplified access mechanisms. Executing incus webui in the command line, the Incus client creates a localized, temporary proxy server on the loopback interface protected by an ephemeral authorization token. This allows administrators to launch a secure web browser session instantly without manually configuring network listeners or managing browser keystores, giving a balance between convenience and strict security controls.<br /> <br /> ==Features and Operational Workflows in the Native Web UI==<br /> Navigating the native Incus web interface is a dashboard structured around core infrastructure primitives: instances, images, profiles, storage pools, networks, and projects. The primary instances view aggregates both lightweight Linux containers and full-fledged virtual machines into a clear list. From this central screen, operators can inspect state indicators, CPU usage, memory consumption, IP address assignments, and storage footprints at a glance, removing the need to run iterative status commands across multiple terminal tabs.<br /> <br /> Instance lifecycle management within the web interface is straightforward and immediate. Users can launch new containers or virtual machines by selecting base images from default public remotes such as images.linuxcontainers.org or from local custom repositories. Configuration profiles, which define network attachments, resource limits, and cloud-init parameters, can be attached or modified visually before creation. Operators can perform immediate operational tasks such as starting, stopping, restarting, pausing, or deleting instances directly through context menus.<br /> <br /> Beyond basic instance control, the web UI provides visibility into storage and networking abstractions. Storage pool management submenus display total capacity, allocated volumes, and snapshot histories across backends like ZFS, Btrfs, LVM, or Ceph. Networking screens allow administrators to inspect bridge devices, overlay networks, managed DHCP leases, and firewall rules. For granular multi-tenancy, the project switching dropdown allows users to isolate environments into logically segregated domains, ensuring that development, staging, and production assets remain neatly partitioned.<br /> <br /> Direct instance interaction is another major highlight of the integrated web dashboard. Leveraging WebSocket connections, the interface has an in-browser terminal console that connects straight into a container's root shell or user environment without needing SSH keys pre-installed. For virtual machines running graphical operating systems or head-less servers requiring low-level access, the web interface integrates SPICE and VNC display streams, enabling interactive desktop sessions directly inside the browser window.<br /> <br /> ==Third-Party Tools and Custom Management Platforms==<br /> The native web UI handles direct node administration with finesse, the broader community has developed third-party tools to address specialized orchestration and multi-node requirements. Lightweight web management tools such as LXConsole offer alternative, containerized web portals that connect to Incus daemons over the standard REST API. These tools appeal to administrators who prefer running management software inside isolated application containers rather than modifying host system packages or binding host web services directly.<br /> <br /> For organizations operating across distributed infrastructure, multi-server management platforms and cloud control panels extend Incus capabilities significantly. Tools built around the Incus REST API allow engineering teams to consolidate multiple standalone hosts and Incus clusters into a unified pane of glass. These community-driven management panels frequently add features beyond the scope of a host-level UI, such as centralized user access controls, role-based permissions, automated backup schedules across multiple hosts, and billing or resource quota tracking tailored for small hosting providers and university lab environments.<br /> <br /> Automation and Infrastructure as Code integrations complement graphical tools by providing structured deployment models. Providers for Terraform and OpenTofu allow teams to define Incus instances, networks, and storage pools declaratively, while Ansible connection plugins facilitate software provisioning across launched environments. In many organizations, administrators use graphical interfaces primarily for real-time monitoring, visual inspection, and interactive troubleshooting, delegating initial provisioning and configuration tasks to these automated pipelines.<br /> <br /> ==Choosing the Right Interface Strategy for Your Infrastructure==<br /> Selecting the appropriate graphical management strategy for Incus depends entirely on deployment scale, security requirements, and team operational habits. For single-host installations, home labs, or development workstations, relying on the built-in incus webui browser launcher provides speed with zero static exposure to external networks. Because the temporary web server binds strictly to the loopback address and authenticates via single-use tokens, it eliminates unauthorized exposure while offering a complete graphical suite for inspecting system behavior.<br /> <br /> In enterprise data centers or shared multi-user environments, deploying the full web interface behind centralized identity infrastructure is the recommended path. Binding the Incus API daemon to a secure internal interface and authenticating users via OpenID Connect guarantees that access logs, multi-factor authentication, and centralized user revocation policies are strictly enforced. Combining this approach with Incus projects ensures that individual departments or tenant groups only see and manage the specific resources assigned to their authorization scope.<br /> <br /> Graphical interfaces should be viewed as an extension of the foundation provided by Incus. Rather than replacing the command-line interface or API-driven automation, web UIs and third-party dashboards observability, lower the entry barrier for new operators, and streamline day-to-day administrative tasks. Understanding the strengths of both native web interfaces and community management platforms, administrators can construct an efficient, secure, and highly flexible management workflow tailored precisely to their infrastructure needs.<br /> <br /> ==What would a transition from Proxmox to Incus GUI be like==<br /> For an experienced Proxmox VE user, transitioning to the Incus Web UI feels less like learning a completely new paradigm and more like switching from a fully integrated virtualization suite to a clean, modular engine built specifically around the Linux kernel.<br /> <br /> Proxmox and Incus share a core foundation both rely heavily on LXC for system containers and QEMU/KVM for virtual machines but their operational philosophies and visual management tools differ significantly.<br /> <br /> ===1. Unified Node vs. Modular Service===<br /> In Proxmox, the web interface is a monolithic management layer tied directly to pve-cluster, corosync, and custom Proxmox daemons. Proxmox controls the entire hypervisor environment, from storage formatting and network bridging to firewalling and clustering rules.<br /> <br /> Incus, operates as a single, lightweight system daemon driven entirely by a well-documented REST API. The Incus Web UI is not an embedded operating system control panel like Proxmox's web interface; it is a decoupled single-page web application that communicates with the Incus daemon over HTTPS.<br /> <br /> For a Proxmox user, this distinction means the Incus interface feels much lighter and faster, but it also delegates host-level tasks (like system updating, base OS disk partitioning, or raw ZFS pool creation) back to the underlying Linux host OS rather than handling them within the UI.<br /> <br /> ===2.Datacenter Tree vs. Projects===<br /> The layout of the two interfaces requires the biggest mental shift:<br /> <br /> *Proxmox uses a strict hierarchical tree view on the left navigation panel (Datacenter -&gt; Node -&gt; Storage/Guest). Every VM and container is immediately visible under its assigned cluster node, identified primarily by a numerical VM ID (for example 100 (web-server)).<br /> <br /> *Incus abandons numerical IDs in favor of unique string names (for example web-server) and replaces the global datacenter tree with Projects.<br /> <br /> In the Incus UI, multi-tenancy and resource grouping are built around these Projects. Instead of browsing a tree of nodes, you use a top-level dropdown to select your current Project (default, staging, production). The UI then displays only the instances, networks, profiles, and storage volumes belonging to that specific project context.<br /> <br /> If you are running an Incus Cluster, instances across different physical nodes are presented within the same project view, eliminating the need to click into individual node sub-trees just to find a running container.<br /> <br /> ===3. Profiles vs. Hardware Tab Configurations===<br /> In Proxmox, you configure guest settings directly on the individual VM or container by adjusting options in its dedicated Hardware and Options tabs. Proxmox supports Cloud-Init templates, creating reusable base configurations across multiple guests often requires cloning pre-configured templates.<br /> <br /> Incus handles configuration through Profiles, which function much like composable infrastructure templates:<br /> <br /> *A Profile defines resource limits (CPU, RAM), device mounts, network attachments, and Cloud-Init user-data scripts.<br /> <br /> *Multiple profiles can be stacked on a single instance (for example, applying both a small-instance profile for CPU/RAM limits and a routed-net profile for network settings).<br /> <br /> *Modifying a profile in the Incus Web UI instantly updates all containers and VMs linked to that profile across the entire node or cluster.<br /> <br /> A Proxmox user adapting to Incus will quickly find that defining profiles upfront drastically reduces manual work when spinning up new environments compared to setting hardware parameters on individual guests.<br /> <br /> ===4. Networking and Storage Conceptual Differences===<br /> '''Networking'''<br /> Proxmox relies heavily on standard Linux bridges (vmbr0, vmbr1), Open vSwitch, and direct VLAN tagging configured on network interfaces within the web UI.<br /> <br /> Incus simplifies this by providing managed network types natively through the UI, primarily using built-in Linux bridges with automatic DHCP/DNS management (incusbr0) or OVN (Open Virtual Network) for advanced multi-host overlay networks and software-defined routing. Setting up isolated networks or routed containers in Incus often requires fewer manual host configuration steps than configuring SDN or custom bridge interfaces in Proxmox.<br /> <br /> '''Storage'''<br /> In Proxmox, storage is configured globally under Datacenter -&gt; Storage, mapping backends (ZFS, LVM-thin, Ceph, NFS) to specific guest usage roles (disk images vs. ISOs).<br /> <br /> Incus abstracts storage into Storage Pools. Within the Incus UI, a single storage pool (backed by ZFS, Btrfs, LVM, or Ceph) holds both instance root disks and custom storage volumes. Incus treats custom storage volumes as first-class primitives meaning you can easily create a standalone storage volume in the UI and attach, detach, or share it across containers without manipulating underlying host block devices.<br /> <br /> ===5. Console Access and Image Workflow===<br /> *Console Access Proxmox defaults to noVNC and SPICE for virtual machines and container shells. Incus provides an interactive, low-latency WebSocket terminal directly in the web browser for container root shells, alongside SPICE/VNC rendering for full virtual machines.<br /> <br /> *Image Management Proxmox users are accustomed to manually downloading ISO images or downloading LXC templates from the Proxmox storage menu. Incus uses Remote Image Registries. From the Incus Web UI, launching an instance allows you to search and pull live images directly from public remotes (such as images.linuxcontainers.org) without needing to pre-download template files to local storage first.<br /> <br /> <br /> If you are moving from Proxmox to Incus, think of Incus as a more API-first container and VM hypervisor.<br /> <br /> And Proxmox excels as a turnkey, hyper-converged replacement for traditional enterprise virtualization stacks (like VMware vSphere), Incus excels at rapid container deployment, clean API integrations, and flexible, profile-driven workflows. Once you get used to navigating by Projects and driving configurations through Profiles, managing instances in the Incus Web UI feels exceptionally fast and lightweight.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_31_2026&diff=4243 2026-07-31T01:39:18Z

<p>Tommy: Created page with &quot;=Incus and Visual Management= Lets recap...designed to deliver a public cloud-like experience on private infrastructure, Incus handles system containers, application containers, and full QEMU-based virtual machines under a single, unified REST API. System administrators and DevOps engineers frequently rely on the incus command-line tool for day-to-day operations, graphical user interfaces have become increasingly valued. Visual management tools reduce the friction of ins...&quot;</p> <hr /> <div>=Incus and Visual Management=<br /> Lets recap...designed to deliver a public cloud-like experience on private infrastructure, Incus handles system containers, application containers, and full QEMU-based virtual machines under a single, unified REST API. System administrators and DevOps engineers frequently rely on the incus command-line tool for day-to-day operations, graphical user interfaces have become increasingly valued. Visual management tools reduce the friction of inspecting node health, managing virtual networks, observing storage utilization, and granting container access to team members who may not be comfortable navigating terminal workflows.<br /> <br /> The shift toward graphical management in the Incus ecosystem reflects a broader industry pattern where infrastructure managers cater to hybrid teams. Developers, quality assurance engineers, and operations technicians need to spin up instances, review logs, attached volumes, or open interactive shell sessions without memorizing extensive command flags. Graphical management tools satisfy this demand by converting multi-step CLI operations into intuitive, visual workflows, making Incus more accessible in small business environments, and enterprise data centers alike.<br /> <br /> ==The Incus Web UI Ecosystem==<br /> The graphical tool is tied to its architecture and history. Rather than building a web frontend from scratch, the Incus community adapted and maintained packages derived from the established LXD browser interface, making them compatible with the Incus daemon. In many distribution repositories, this interface is packaged under names like incus-ui or incus-ui-canonical. Once installed, administrators can expose the API server over HTTPS and authenticate using client TLS certificates or OpenID Connect identity providers, ensuring security for remote administration.<br /> <br /> To solve the historical friction of client certificate generation and browser importing, Incus releases introduced simplified access mechanisms. Executing incus webui in the command line, the Incus client creates a localized, temporary proxy server on the loopback interface protected by an ephemeral authorization token. This allows administrators to launch a secure web browser session instantly without manually configuring network listeners or managing browser keystores, giving a balance between convenience and strict security controls.<br /> <br /> ==Features and Operational Workflows in the Native Web UI==<br /> Navigating the native Incus web interface is a dashboard structured around core infrastructure primitives: instances, images, profiles, storage pools, networks, and projects. The primary instances view aggregates both lightweight Linux containers and full-fledged virtual machines into a clear list. From this central screen, operators can inspect state indicators, CPU usage, memory consumption, IP address assignments, and storage footprints at a glance, removing the need to run iterative status commands across multiple terminal tabs.<br /> <br /> Instance lifecycle management within the web interface is straightforward and immediate. Users can launch new containers or virtual machines by selecting base images from default public remotes such as images.linuxcontainers.org or from local custom repositories. Configuration profiles, which define network attachments, resource limits, and cloud-init parameters, can be attached or modified visually before creation. Operators can perform immediate operational tasks such as starting, stopping, restarting, pausing, or deleting instances directly through context menus.<br /> <br /> Beyond basic instance control, the web UI provides visibility into storage and networking abstractions. Storage pool management submenus display total capacity, allocated volumes, and snapshot histories across backends like ZFS, Btrfs, LVM, or Ceph. Networking screens allow administrators to inspect bridge devices, overlay networks, managed DHCP leases, and firewall rules. For granular multi-tenancy, the project switching dropdown allows users to isolate environments into logically segregated domains, ensuring that development, staging, and production assets remain neatly partitioned.<br /> <br /> Direct instance interaction is another major highlight of the integrated web dashboard. Leveraging WebSocket connections, the interface has an in-browser terminal console that connects straight into a container's root shell or user environment without needing SSH keys pre-installed. For virtual machines running graphical operating systems or head-less servers requiring low-level access, the web interface integrates SPICE and VNC display streams, enabling interactive desktop sessions directly inside the browser window.<br /> <br /> ==Third-Party Tools and Custom Management Platforms==<br /> The native web UI handles direct node administration with finesse, the broader community has developed third-party tools to address specialized orchestration and multi-node requirements. Lightweight web management tools such as LXConsole offer alternative, containerized web portals that connect to Incus daemons over the standard REST API. These tools appeal to administrators who prefer running management software inside isolated application containers rather than modifying host system packages or binding host web services directly.<br /> <br /> For organizations operating across distributed infrastructure, multi-server management platforms and cloud control panels extend Incus capabilities significantly. Tools built around the Incus REST API allow engineering teams to consolidate multiple standalone hosts and Incus clusters into a unified pane of glass. These community-driven management panels frequently add features beyond the scope of a host-level UI, such as centralized user access controls, role-based permissions, automated backup schedules across multiple hosts, and billing or resource quota tracking tailored for small hosting providers and university lab environments.<br /> <br /> Automation and Infrastructure as Code integrations complement graphical tools by providing structured deployment models. Providers for Terraform and OpenTofu allow teams to define Incus instances, networks, and storage pools declaratively, while Ansible connection plugins facilitate software provisioning across launched environments. In many organizations, administrators use graphical interfaces primarily for real-time monitoring, visual inspection, and interactive troubleshooting, delegating initial provisioning and configuration tasks to these automated pipelines.<br /> <br /> ==Choosing the Right Interface Strategy for Your Infrastructure==<br /> Selecting the appropriate graphical management strategy for Incus depends entirely on deployment scale, security requirements, and team operational habits. For single-host installations, home labs, or development workstations, relying on the built-in incus webui browser launcher provides speed with zero static exposure to external networks. Because the temporary web server binds strictly to the loopback address and authenticates via single-use tokens, it eliminates unauthorized exposure while offering a complete graphical suite for inspecting system behavior.<br /> <br /> In enterprise data centers or shared multi-user environments, deploying the full web interface behind centralized identity infrastructure is the recommended path. Binding the Incus API daemon to a secure internal interface and authenticating users via OpenID Connect guarantees that access logs, multi-factor authentication, and centralized user revocation policies are strictly enforced. Combining this approach with Incus projects ensures that individual departments or tenant groups only see and manage the specific resources assigned to their authorization scope.<br /> <br /> Graphical interfaces should be viewed as an extension of the foundation provided by Incus. Rather than replacing the command-line interface or API-driven automation, web UIs and third-party dashboards observability, lower the entry barrier for new operators, and streamline day-to-day administrative tasks. Understanding the strengths of both native web interfaces and community management platforms, administrators can construct an efficient, secure, and highly flexible management workflow tailored precisely to their infrastructure needs.<br /> <br /> ==What would a transition from Proxmox to Incus GUI be like==<br /> For an experienced Proxmox VE user, transitioning to the Incus Web UI feels less like learning a completely new paradigm and more like switching from a fully integrated virtualization suite to a clean, modular engine built specifically around the Linux kernel.<br /> <br /> Proxmox and Incus share a core foundation both rely heavily on LXC for system containers and QEMU/KVM for virtual machines but their operational philosophies and visual management tools differ significantly.<br /> <br /> ===1. Unified Node vs. Modular Service===<br /> In Proxmox, the web interface is a monolithic management layer tied directly to pve-cluster, corosync, and custom Proxmox daemons. Proxmox controls the entire hypervisor environment, from storage formatting and network bridging to firewalling and clustering rules.<br /> <br /> Incus, operates as a single, lightweight system daemon driven entirely by a well-documented REST API. The Incus Web UI is not an embedded operating system control panel like Proxmox's web interface; it is a decoupled single-page web application that communicates with the Incus daemon over HTTPS.<br /> <br /> For a Proxmox user, this distinction means the Incus interface feels much lighter and faster, but it also delegates host-level tasks (like system updating, base OS disk partitioning, or raw ZFS pool creation) back to the underlying Linux host OS rather than handling them within the UI.<br /> <br /> ===2.Datacenter Tree vs. Projects===<br /> The layout of the two interfaces requires the biggest mental shift:<br /> <br /> *Proxmox uses a strict hierarchical tree view on the left navigation panel (Datacenter -&gt; Node -&gt; Storage/Guest). Every VM and container is immediately visible under its assigned cluster node, identified primarily by a numerical VM ID (for example 100 (web-server)).<br /> <br /> *Incus abandons numerical IDs in favor of unique string names (for example web-server) and replaces the global datacenter tree with Projects.<br /> <br /> In the Incus UI, multi-tenancy and resource grouping are built around these Projects. Instead of browsing a tree of nodes, you use a top-level dropdown to select your current Project (default, staging, production). The UI then displays only the instances, networks, profiles, and storage volumes belonging to that specific project context.<br /> <br /> If you are running an Incus Cluster, instances across different physical nodes are presented within the same project view, eliminating the need to click into individual node sub-trees just to find a running container.<br /> <br /> ===3. Profiles vs. Hardware Tab Configurations===<br /> In Proxmox, you configure guest settings directly on the individual VM or container by adjusting options in its dedicated Hardware and Options tabs. Proxmox supports Cloud-Init templates, creating reusable base configurations across multiple guests often requires cloning pre-configured templates.<br /> <br /> Incus handles configuration through Profiles, which function much like composable infrastructure templates:<br /> <br /> *A Profile defines resource limits (CPU, RAM), device mounts, network attachments, and Cloud-Init user-data scripts.<br /> <br /> *Multiple profiles can be stacked on a single instance (for example, applying both a small-instance profile for CPU/RAM limits and a routed-net profile for network settings).<br /> <br /> *Modifying a profile in the Incus Web UI instantly updates all containers and VMs linked to that profile across the entire node or cluster.<br /> <br /> A Proxmox user adapting to Incus will quickly find that defining profiles upfront drastically reduces manual work when spinning up new environments compared to setting hardware parameters on individual guests.<br /> <br /> ===4. Networking and Storage Conceptual Differences===<br /> '''Networking'''<br /> Proxmox relies heavily on standard Linux bridges (vmbr0, vmbr1), Open vSwitch, and direct VLAN tagging configured on network interfaces within the web UI.<br /> <br /> Incus simplifies this by providing managed network types natively through the UI, primarily using built-in Linux bridges with automatic DHCP/DNS management (incusbr0) or OVN (Open Virtual Network) for advanced multi-host overlay networks and software-defined routing. Setting up isolated networks or routed containers in Incus often requires fewer manual host configuration steps than configuring SDN or custom bridge interfaces in Proxmox.<br /> <br /> '''Storage'''<br /> In Proxmox, storage is configured globally under Datacenter -&gt; Storage, mapping backends (ZFS, LVM-thin, Ceph, NFS) to specific guest usage roles (disk images vs. ISOs).<br /> <br /> Incus abstracts storage into Storage Pools. Within the Incus UI, a single storage pool (backed by ZFS, Btrfs, LVM, or Ceph) holds both instance root disks and custom storage volumes. Incus treats custom storage volumes as first-class primitives meaning you can easily create a standalone storage volume in the UI and attach, detach, or share it across containers without manipulating underlying host block devices.<br /> <br /> ===5. Console Access and Image Workflow===<br /> *Console Access Proxmox defaults to noVNC and SPICE for virtual machines and container shells. Incus provides an interactive, low-latency WebSocket terminal directly in the web browser for container root shells, alongside SPICE/VNC rendering for full virtual machines.<br /> <br /> *Image Management Proxmox users are accustomed to manually downloading ISO images or downloading LXC templates from the Proxmox storage menu. Incus uses Remote Image Registries. From the Incus Web UI, launching an instance allows you to search and pull live images directly from public remotes (such as images.linuxcontainers.org) without needing to pre-download template files to local storage first.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4242 2026-07-31T01:12:08Z

<p>Tommy: /* July 2026 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> *[[Daily_Post_July_23_2026JP|LXDからIncusへの移行：オープンソース・システムコンテナの新たな標準 7/23/2026]]<br /> *[[Daily_Post_July_24_2026JP|単一のCLIからのコンテナと仮想マシンの統合管理 7/27/2026]]<br /> *[[Daily_Post_July_30_2026JP|Incusにおけるネットワーク高度化：カスタムLinuxブリッジとOVN (Open Virtual Network) 7/30/2026]]<br /> <br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> *[[Daily_Post_July_23_2026|Daily Post July 23 2026 - Migrating from LXD to Incus]]<br /> *[[Daily_Post_July_24_2026|Daily Post July 24 2026 - Managing Containers and Virtual Machines from One CLI]]<br /> *[[Daily_Post_July_27_2026|Daily Post July 27 2026 - Incus Networking OVN (Open Virtual Network) and Custom Bridges]]<br /> *[[Daily_Post_July_28_2026|Daily Post July 28 2026 - Incus Storage Pools using ZFS and Btrfs for Snapshots]]<br /> *[[Daily_Post_July_30_2026|Daily Post July 30 2026 - Nested virtualization]]<br /> *[[Daily_Post_July_31_2026|Daily Post July 31 2026 - Incus and Visual Management]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_30_2026&diff=4238 2026-07-30T02:35:11Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Nested Virtualization: Running Incus inside a Proxmox VM<br /> |description= Discover why businesses combine Proxmox VE and Incus. Learn how nested virtualization delivers tenant isolation, hardware abstraction, and simplified disaster recovery.<br /> |keywords= Incus, Proxmox VE, Nested Virtualization, PVE, System Containers, Hypervisor, Proxmox Backup Server, Multi-Tenant, Infrastructure Security, Linux Virtualization<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_30_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Nested virtualization=<br /> The idea of running a hypervisor or container daemon within a virtual machine that is itself hosted by a physical hypervisor can sounds like an unnecessary, inception-like engineering experiment. But, when applied to running Incus inside a Proxmox Virtual Environment virtual machine, nested virtualization becomes very useful. design pattern for infrastructure. Proxmox VE acts as the foundational, bare-metal hypervisor, providing management for physical compute, storage, and networking. Inside a Proxmox-managed Linux VM, Incus operates as a secondary, lightweight container and VM daemon. Combining these two systems creates a layered architecture that solves operational challenges.<br /> <br /> To understand why an enterprise would adopt this pattern, it is helpful to think about the architectural strengths of both platforms. Proxmox is good at macro-level infrastructure management. It handles bare-metal hardware integration, high-availability clusters, storage backends like Ceph and ZFS, and physical network bridging with ease generally. On the other hand, Incus is good at micro-level orchestration. It allows administrators to spin up dozens or hundreds of lightweight system containers or virtual machines in seconds via a fast REST API and CLI. <br /> <br /> ==Isolation and Security==<br /> One of the primary values this architecture offers businesses is safe, multi-tenant isolation for development and testing environments. In a traditional setup, giving developers access to run container orchestration software directly on physical hypervisors presents security and operational risks. System-level container engines require broad privileges on the underlying Linux kernel, creating a broad attack surface. Provisioning a dedicated Proxmox VM for a software team and installing Incus inside it, the enterprise constructs a strong hardware-virtualized boundary around that team's entire workspace. <br /> <br /> ==Density and Resource Efficiency==<br /> This nested approach dramatically improves resource efficiency and density for large-scale application workloads. Virtual machines generated by traditional hypervisors carry notable overhead because each requires a full OS kernel and dedicated hardware emulation. If an enterprise needs to deploy fifty isolated microservices or developer sandboxes, running fifty separate Proxmox VMs consumes substantial memory and CPU overhead. Running a single, well-resourced Proxmox VM and deploying fifty Incus system containers inside it, the enterprise leverages container-level kernel sharing. Incus containers launch almost instantaneously and share the underlying VM kernel, allowing businesses to achieve massive consolidation ratios while preserving isolated execution environments.<br /> <br /> ==Networking, Auditing, and Infrastructure Portability==<br /> Network segmentation and security auditing also benefit significantly from this hybrid architecture. Proxmox allows network administrators to define precise virtual network interfaces, VLAN tags, and firewalls at the hypervisor level. The nested Incus installation inherits this parent VM network interface, allowing it to act as an isolated internal network bridge for all nested containers. This structure simplifies compliance and policy enforcement. Security teams can enforce firewall rules and monitor traffic at the Proxmox layer without needing to manage the dynamic, high-churn network interfaces created internally as Incus containers are added and removed.<br /> <br /> Finally, running Incus inside a Proxmox VM offers infrastructure portability and simplified disaster recovery. A Proxmox VM housing an entire Incus environment along with its containers, storage pools, and configuration profilescan be backed up, snapshotted, and live-migrated as a single, unified virtual disk. If a physical bare-metal server needs maintenance, administrators can migrate the parent Proxmox VM to another node in the cluster without needing to export or re-orchestrate individual Incus containers. This abstraction layer bridges the gap between traditional enterprise virtualization and cloud-native container workloads.<br /> <br /> ==The reason you put Incus inside Proxmox and almost never Proxmox inside Incus==<br /> It is because of how they handle physical hardware, kernel access, and bare-metal orchestration.<br /> Proxmox VE is a complete bare-metal operating system built directly on Debian Linux. Its primary job is to manage physical server hardware RAID cards, network interface controllers (NICs), physical RAM, storage pools (like ZFS or Ceph), and CPU virtualization extensions (Intel VT-x / AMD-V).<br /> <br /> Incus, is capable of managing full virtual machines via QEMU, was built from LXD as a container/VM manager meant to sit on top of an existing Linux kernel.<br /> <br /> If you try to put Proxmox inside an Incus VM:<br /> *Hardware passthrough becomes a mess Proxmox expects raw, low-level control of storage and networking to manage clusters, storage pools, and firewalling. Inside an Incus VM, it gets an emulated, virtualized layer instead of real hardware, severely limiting its core capabilities.<br /> <br /> *Double virtualizing for no reason Proxmox’s main strength is managing physical nodes and storage clusters. Strip away its access to physical hardware, and you lose most of why Proxmox exists in the first place.<br /> <br /> Putting Incus inside Proxmox works because Proxmox provides the physical foundation.<br /> <br /> ==Production Incus vs. Production Proxmox==<br /> Incus isn't a scaled-down tool; it’s designed for heavy production lifting. It handles both LXC system containers and full QEMU virtual machines, features native clustering, storage abstraction (ZFS, Ceph, LVM), and precise resource controls.<br /> <br /> ===When you compare them in production===<br /> *Proxmox gives you a complete, GUI-centric bare-metal hypervisor appliance with integrated cluster management, high availability, and out-of-the-box storage handling.<br /> <br /> *Incus gives you a light, API-native operational model with near-zero overhead for system containers and fine-grained control via CLI.<br /> <br /> When you run production Incus inside a Proxmox VM, you aren't doing it to make Incus &quot;safe&quot; for production you're doing it to combine two different layers of production infrastructure management.<br /> <br /> ===Unified Bare-Metal Management===<br /> In a production datacenter, you often have legacy VMs, Windows servers, full Linux virtual machines, and lightweight Incus instances.<br /> *If you run Incus directly on bare metal across your fleet, you have to manage physical hardware monitoring, storage arrays, network switches, and host backups for those Incus hosts separately from the rest of your virtualization estate.<br /> <br /> * Using Proxmox as the bare-metal hypervisor layer across all physical nodes, Proxmox handles the raw hardware, Ceph/ZFS storage pools, physical networking, and hardware alerts. Incus runs inside dedicated production VMs on top of that stable base<br /> <br /> ===Infrastructure-as-a-Service and Multi-Tenant Fleet Division===<br /> If you operate as a service provider or run multiple internal production business units, you don't always want a single massive Incus cluster sharing one kernel or network boundary across all tenants.<br /> <br /> Deploying production Incus daemons inside Proxmox VMs, you can carve up your physical hardware into isolated production tiers:<br /> <br /> *Production Tier A: Lives in a multi-node Incus setup inside dedicated Proxmox compute resources with guaranteed CPU/RAM pinning.<br /> <br /> *Production Tier B: Runs in a separate Proxmox VM or directly on Proxmox, completely isolated at the hardware boundary level from Tier A.<br /> <br /> ===Hypervisor-Level Backup and Disaster Recovery===<br /> Incus has great internal snapshotting and image export capabilities, taking a full, crash-consistent backup of a production environment at the hypervisor level adds a layer of safety.<br /> <br /> *A Proxmox VM running a production Incus instance can be backed up using Proxmox Backup Server with block-level deduplication, incremental backups, and live encryption.<br /> <br /> *If a production disaster strikes (like a corrupted host OS database or broken storage pool configuration inside the VM), you can restore the entire operating system and its active Incus daemon to any physical Proxmox host in minutes.<br /> <br /> ===Zero-Downtime Hardware Maintenance===<br /> If a physical server hosting your production environment needs a BIOS update, RAM replacement, or kernel patch:<br /> <br /> *Proxmox handles live migration of the parent VM to another physical host in the Proxmox cluster without taking the nested production Incus containers down.<br /> <br /> *You maintain high availability at the physical hardware level without having to re-route or fail over the internal Incus network.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_30_2026&diff=4237 2026-07-30T02:34:33Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Nested Virtualization: Running Incus inside a Proxmox VM<br /> |description= Discover why businesses combine Proxmox VE and Incus. Learn how nested virtualization delivers tenant isolation, hardware abstraction, and simplified disaster recovery.<br /> |keywords= Incus, Proxmox VE, Nested Virtualization, PVE, System Containers, Hypervisor, Proxmox Backup Server, Multi-Tenant, Infrastructure Security, Linux Virtualization<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_30_2026<br /> }}<br /> =Nested virtualization=<br /> The idea of running a hypervisor or container daemon within a virtual machine that is itself hosted by a physical hypervisor can sounds like an unnecessary, inception-like engineering experiment. But, when applied to running Incus inside a Proxmox Virtual Environment virtual machine, nested virtualization becomes very useful. design pattern for infrastructure. Proxmox VE acts as the foundational, bare-metal hypervisor, providing management for physical compute, storage, and networking. Inside a Proxmox-managed Linux VM, Incus operates as a secondary, lightweight container and VM daemon. Combining these two systems creates a layered architecture that solves operational challenges.<br /> <br /> To understand why an enterprise would adopt this pattern, it is helpful to think about the architectural strengths of both platforms. Proxmox is good at macro-level infrastructure management. It handles bare-metal hardware integration, high-availability clusters, storage backends like Ceph and ZFS, and physical network bridging with ease generally. On the other hand, Incus is good at micro-level orchestration. It allows administrators to spin up dozens or hundreds of lightweight system containers or virtual machines in seconds via a fast REST API and CLI. <br /> <br /> ==Isolation and Security==<br /> One of the primary values this architecture offers businesses is safe, multi-tenant isolation for development and testing environments. In a traditional setup, giving developers access to run container orchestration software directly on physical hypervisors presents security and operational risks. System-level container engines require broad privileges on the underlying Linux kernel, creating a broad attack surface. Provisioning a dedicated Proxmox VM for a software team and installing Incus inside it, the enterprise constructs a strong hardware-virtualized boundary around that team's entire workspace. <br /> <br /> ==Density and Resource Efficiency==<br /> This nested approach dramatically improves resource efficiency and density for large-scale application workloads. Virtual machines generated by traditional hypervisors carry notable overhead because each requires a full OS kernel and dedicated hardware emulation. If an enterprise needs to deploy fifty isolated microservices or developer sandboxes, running fifty separate Proxmox VMs consumes substantial memory and CPU overhead. Running a single, well-resourced Proxmox VM and deploying fifty Incus system containers inside it, the enterprise leverages container-level kernel sharing. Incus containers launch almost instantaneously and share the underlying VM kernel, allowing businesses to achieve massive consolidation ratios while preserving isolated execution environments.<br /> <br /> ==Networking, Auditing, and Infrastructure Portability==<br /> Network segmentation and security auditing also benefit significantly from this hybrid architecture. Proxmox allows network administrators to define precise virtual network interfaces, VLAN tags, and firewalls at the hypervisor level. The nested Incus installation inherits this parent VM network interface, allowing it to act as an isolated internal network bridge for all nested containers. This structure simplifies compliance and policy enforcement. Security teams can enforce firewall rules and monitor traffic at the Proxmox layer without needing to manage the dynamic, high-churn network interfaces created internally as Incus containers are added and removed.<br /> <br /> Finally, running Incus inside a Proxmox VM offers infrastructure portability and simplified disaster recovery. A Proxmox VM housing an entire Incus environment along with its containers, storage pools, and configuration profilescan be backed up, snapshotted, and live-migrated as a single, unified virtual disk. If a physical bare-metal server needs maintenance, administrators can migrate the parent Proxmox VM to another node in the cluster without needing to export or re-orchestrate individual Incus containers. This abstraction layer bridges the gap between traditional enterprise virtualization and cloud-native container workloads.<br /> <br /> ==The reason you put Incus inside Proxmox and almost never Proxmox inside Incus==<br /> It is because of how they handle physical hardware, kernel access, and bare-metal orchestration.<br /> Proxmox VE is a complete bare-metal operating system built directly on Debian Linux. Its primary job is to manage physical server hardware RAID cards, network interface controllers (NICs), physical RAM, storage pools (like ZFS or Ceph), and CPU virtualization extensions (Intel VT-x / AMD-V).<br /> <br /> Incus, is capable of managing full virtual machines via QEMU, was built from LXD as a container/VM manager meant to sit on top of an existing Linux kernel.<br /> <br /> If you try to put Proxmox inside an Incus VM:<br /> *Hardware passthrough becomes a mess Proxmox expects raw, low-level control of storage and networking to manage clusters, storage pools, and firewalling. Inside an Incus VM, it gets an emulated, virtualized layer instead of real hardware, severely limiting its core capabilities.<br /> <br /> *Double virtualizing for no reason Proxmox’s main strength is managing physical nodes and storage clusters. Strip away its access to physical hardware, and you lose most of why Proxmox exists in the first place.<br /> <br /> Putting Incus inside Proxmox works because Proxmox provides the physical foundation.<br /> <br /> ==Production Incus vs. Production Proxmox==<br /> Incus isn't a scaled-down tool; it’s designed for heavy production lifting. It handles both LXC system containers and full QEMU virtual machines, features native clustering, storage abstraction (ZFS, Ceph, LVM), and precise resource controls.<br /> <br /> ===When you compare them in production===<br /> *Proxmox gives you a complete, GUI-centric bare-metal hypervisor appliance with integrated cluster management, high availability, and out-of-the-box storage handling.<br /> <br /> *Incus gives you a light, API-native operational model with near-zero overhead for system containers and fine-grained control via CLI.<br /> <br /> When you run production Incus inside a Proxmox VM, you aren't doing it to make Incus &quot;safe&quot; for production you're doing it to combine two different layers of production infrastructure management.<br /> <br /> ===Unified Bare-Metal Management===<br /> In a production datacenter, you often have legacy VMs, Windows servers, full Linux virtual machines, and lightweight Incus instances.<br /> *If you run Incus directly on bare metal across your fleet, you have to manage physical hardware monitoring, storage arrays, network switches, and host backups for those Incus hosts separately from the rest of your virtualization estate.<br /> <br /> * Using Proxmox as the bare-metal hypervisor layer across all physical nodes, Proxmox handles the raw hardware, Ceph/ZFS storage pools, physical networking, and hardware alerts. Incus runs inside dedicated production VMs on top of that stable base<br /> <br /> ===Infrastructure-as-a-Service and Multi-Tenant Fleet Division===<br /> If you operate as a service provider or run multiple internal production business units, you don't always want a single massive Incus cluster sharing one kernel or network boundary across all tenants.<br /> <br /> Deploying production Incus daemons inside Proxmox VMs, you can carve up your physical hardware into isolated production tiers:<br /> <br /> *Production Tier A: Lives in a multi-node Incus setup inside dedicated Proxmox compute resources with guaranteed CPU/RAM pinning.<br /> <br /> *Production Tier B: Runs in a separate Proxmox VM or directly on Proxmox, completely isolated at the hardware boundary level from Tier A.<br /> <br /> ===Hypervisor-Level Backup and Disaster Recovery===<br /> Incus has great internal snapshotting and image export capabilities, taking a full, crash-consistent backup of a production environment at the hypervisor level adds a layer of safety.<br /> <br /> *A Proxmox VM running a production Incus instance can be backed up using Proxmox Backup Server with block-level deduplication, incremental backups, and live encryption.<br /> <br /> *If a production disaster strikes (like a corrupted host OS database or broken storage pool configuration inside the VM), you can restore the entire operating system and its active Incus daemon to any physical Proxmox host in minutes.<br /> <br /> ===Zero-Downtime Hardware Maintenance===<br /> If a physical server hosting your production environment needs a BIOS update, RAM replacement, or kernel patch:<br /> <br /> *Proxmox handles live migration of the parent VM to another physical host in the Proxmox cluster without taking the nested production Incus containers down.<br /> <br /> *You maintain high availability at the physical hardware level without having to re-route or fail over the internal Incus network.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_30_2026&diff=4236 2026-07-30T02:32:56Z

<p>Tommy: Created page with &quot;=Nested virtualization= The idea of running a hypervisor or container daemon within a virtual machine that is itself hosted by a physical hypervisor can sounds like an unnecessary, inception-like engineering experiment. But, when applied to running Incus inside a Proxmox Virtual Environment virtual machine, nested virtualization becomes very useful. design pattern for infrastructure. Proxmox VE acts as the foundational, bare-metal hypervisor, providing management for phy...&quot;</p> <hr /> <div>=Nested virtualization=<br /> The idea of running a hypervisor or container daemon within a virtual machine that is itself hosted by a physical hypervisor can sounds like an unnecessary, inception-like engineering experiment. But, when applied to running Incus inside a Proxmox Virtual Environment virtual machine, nested virtualization becomes very useful. design pattern for infrastructure. Proxmox VE acts as the foundational, bare-metal hypervisor, providing management for physical compute, storage, and networking. Inside a Proxmox-managed Linux VM, Incus operates as a secondary, lightweight container and VM daemon. Combining these two systems creates a layered architecture that solves operational challenges.<br /> <br /> To understand why an enterprise would adopt this pattern, it is helpful to think about the architectural strengths of both platforms. Proxmox is good at macro-level infrastructure management. It handles bare-metal hardware integration, high-availability clusters, storage backends like Ceph and ZFS, and physical network bridging with ease generally. On the other hand, Incus is good at micro-level orchestration. It allows administrators to spin up dozens or hundreds of lightweight system containers or virtual machines in seconds via a fast REST API and CLI. <br /> <br /> ==Isolation and Security==<br /> One of the primary values this architecture offers businesses is safe, multi-tenant isolation for development and testing environments. In a traditional setup, giving developers access to run container orchestration software directly on physical hypervisors presents security and operational risks. System-level container engines require broad privileges on the underlying Linux kernel, creating a broad attack surface. Provisioning a dedicated Proxmox VM for a software team and installing Incus inside it, the enterprise constructs a strong hardware-virtualized boundary around that team's entire workspace. <br /> <br /> ==Density and Resource Efficiency==<br /> This nested approach dramatically improves resource efficiency and density for large-scale application workloads. Virtual machines generated by traditional hypervisors carry notable overhead because each requires a full OS kernel and dedicated hardware emulation. If an enterprise needs to deploy fifty isolated microservices or developer sandboxes, running fifty separate Proxmox VMs consumes substantial memory and CPU overhead. Running a single, well-resourced Proxmox VM and deploying fifty Incus system containers inside it, the enterprise leverages container-level kernel sharing. Incus containers launch almost instantaneously and share the underlying VM kernel, allowing businesses to achieve massive consolidation ratios while preserving isolated execution environments.<br /> <br /> ==Networking, Auditing, and Infrastructure Portability==<br /> Network segmentation and security auditing also benefit significantly from this hybrid architecture. Proxmox allows network administrators to define precise virtual network interfaces, VLAN tags, and firewalls at the hypervisor level. The nested Incus installation inherits this parent VM network interface, allowing it to act as an isolated internal network bridge for all nested containers. This structure simplifies compliance and policy enforcement. Security teams can enforce firewall rules and monitor traffic at the Proxmox layer without needing to manage the dynamic, high-churn network interfaces created internally as Incus containers are added and removed.<br /> <br /> Finally, running Incus inside a Proxmox VM offers infrastructure portability and simplified disaster recovery. A Proxmox VM housing an entire Incus environment along with its containers, storage pools, and configuration profilescan be backed up, snapshotted, and live-migrated as a single, unified virtual disk. If a physical bare-metal server needs maintenance, administrators can migrate the parent Proxmox VM to another node in the cluster without needing to export or re-orchestrate individual Incus containers. This abstraction layer bridges the gap between traditional enterprise virtualization and cloud-native container workloads.<br /> <br /> ==The reason you put Incus inside Proxmox and almost never Proxmox inside Incus==<br /> It is because of how they handle physical hardware, kernel access, and bare-metal orchestration.<br /> Proxmox VE is a complete bare-metal operating system built directly on Debian Linux. Its primary job is to manage physical server hardware RAID cards, network interface controllers (NICs), physical RAM, storage pools (like ZFS or Ceph), and CPU virtualization extensions (Intel VT-x / AMD-V).<br /> <br /> Incus, is capable of managing full virtual machines via QEMU, was built from LXD as a container/VM manager meant to sit on top of an existing Linux kernel.<br /> <br /> If you try to put Proxmox inside an Incus VM:<br /> *Hardware passthrough becomes a mess Proxmox expects raw, low-level control of storage and networking to manage clusters, storage pools, and firewalling. Inside an Incus VM, it gets an emulated, virtualized layer instead of real hardware, severely limiting its core capabilities.<br /> <br /> *Double virtualizing for no reason Proxmox’s main strength is managing physical nodes and storage clusters. Strip away its access to physical hardware, and you lose most of why Proxmox exists in the first place.<br /> <br /> Putting Incus inside Proxmox works because Proxmox provides the physical foundation.<br /> <br /> ==Production Incus vs. Production Proxmox==<br /> Incus isn't a scaled-down tool; it’s designed for heavy production lifting. It handles both LXC system containers and full QEMU virtual machines, features native clustering, storage abstraction (ZFS, Ceph, LVM), and precise resource controls.<br /> <br /> ===When you compare them in production===<br /> *Proxmox gives you a complete, GUI-centric bare-metal hypervisor appliance with integrated cluster management, high availability, and out-of-the-box storage handling.<br /> <br /> *Incus gives you a light, API-native operational model with near-zero overhead for system containers and fine-grained control via CLI.<br /> <br /> When you run production Incus inside a Proxmox VM, you aren't doing it to make Incus &quot;safe&quot; for production you're doing it to combine two different layers of production infrastructure management.<br /> <br /> ===Unified Bare-Metal Management===<br /> In a production datacenter, you often have legacy VMs, Windows servers, full Linux virtual machines, and lightweight Incus instances.<br /> *If you run Incus directly on bare metal across your fleet, you have to manage physical hardware monitoring, storage arrays, network switches, and host backups for those Incus hosts separately from the rest of your virtualization estate.<br /> <br /> * Using Proxmox as the bare-metal hypervisor layer across all physical nodes, Proxmox handles the raw hardware, Ceph/ZFS storage pools, physical networking, and hardware alerts. Incus runs inside dedicated production VMs on top of that stable base<br /> <br /> ===Infrastructure-as-a-Service and Multi-Tenant Fleet Division===<br /> If you operate as a service provider or run multiple internal production business units, you don't always want a single massive Incus cluster sharing one kernel or network boundary across all tenants.<br /> <br /> Deploying production Incus daemons inside Proxmox VMs, you can carve up your physical hardware into isolated production tiers:<br /> <br /> *Production Tier A: Lives in a multi-node Incus setup inside dedicated Proxmox compute resources with guaranteed CPU/RAM pinning.<br /> <br /> *Production Tier B: Runs in a separate Proxmox VM or directly on Proxmox, completely isolated at the hardware boundary level from Tier A.<br /> <br /> ===Hypervisor-Level Backup and Disaster Recovery===<br /> Incus has great internal snapshotting and image export capabilities, taking a full, crash-consistent backup of a production environment at the hypervisor level adds a layer of safety.<br /> <br /> *A Proxmox VM running a production Incus instance can be backed up using Proxmox Backup Server with block-level deduplication, incremental backups, and live encryption.<br /> <br /> *If a production disaster strikes (like a corrupted host OS database or broken storage pool configuration inside the VM), you can restore the entire operating system and its active Incus daemon to any physical Proxmox host in minutes.<br /> <br /> ===Zero-Downtime Hardware Maintenance===<br /> If a physical server hosting your production environment needs a BIOS update, RAM replacement, or kernel patch:<br /> <br /> *Proxmox handles live migration of the parent VM to another physical host in the Proxmox cluster without taking the nested production Incus containers down.<br /> <br /> *You maintain high availability at the physical hardware level without having to re-route or fail over the internal Incus network.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4235 2026-07-30T01:16:35Z

<p>Tommy: /* July 2026 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> *[[Daily_Post_July_23_2026JP|LXDからIncusへの移行：オープンソース・システムコンテナの新たな標準 7/23/2026]]<br /> *[[Daily_Post_July_24_2026JP|単一のCLIからのコンテナと仮想マシンの統合管理 7/27/2026]]<br /> <br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> *[[Daily_Post_July_23_2026|Daily Post July 23 2026 - Migrating from LXD to Incus]]<br /> *[[Daily_Post_July_24_2026|Daily Post July 24 2026 - Managing Containers and Virtual Machines from One CLI]]<br /> *[[Daily_Post_July_27_2026|Daily Post July 27 2026 - Incus Networking OVN (Open Virtual Network) and Custom Bridges]]<br /> *[[Daily_Post_July_28_2026|Daily Post July 28 2026 - Incus Storage Pools using ZFS and Btrfs for Snapshots]]<br /> *[[Daily_Post_July_30_2026|Daily Post July 30 2026 - Nested virtualization]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_28_2026&diff=4234 2026-07-28T01:03:14Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Storage Pools in Incus ZFS and Btrfs for Instant Snapshots<br /> |description= Learn how Incus utilizes Copy-on-Write storage backends like ZFS and Btrfs to deliver instant snapshots, zero-cost cloning, and rapid container provisioning.<br /> |keywords= Incus, Incus Storage Pools, ZFS, Btrfs, Copy-on-Write, Instant Snapshots, Container Storage, ZPOOL, Subvolumes, Linux Virtualization<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_28_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Incus Storage Pools using ZFS and Btrfs for Snapshots=<br /> Traditional file systems like ext4 paired with basic directory backends does give compatibility, but they don't have the capabilities required for large production environments. To really get the full potential of Incus particularly regarding fast deployment, resource efficiency, and instantaneous snapshots you need Copy-on-Write storage backends. For example these backends are ZFS and Btrfs, two storage technologies that can change how virtualized storage is provisioned and maintained.<br /> <br /> ==Storage Pools in Incus==<br /> Incus abstracts storage management away from raw block devices and host paths through a unified construct called a storage pool. A storage pool is a designated storage space allocated to Incus, which the system uses to store instance root file systems, custom data volumes, base images, and snapshots. Establishing this abstraction layer, Incus decouples application workloads from the underlying hardware details. When an administrator launches a new container or virtual machine, Incus requests space from the specified storage pool, creating a storage volume tailored to that instance.<br /> <br /> The choice of storage driver configured for a pool determines how these volumes behave under the hood. When using a simple directory driver, creating a snapshot or cloning a container requires copying every single file using utility tools like rsync. This approach is slow, scales poorly with container size, and consumes large amounts of storage space. On the other hand, Copy-on-Write storage drivers use file system and volume management capabilities built directly into the Linux kernel. Managing storage through specialized drivers for ZFS or Btrfs, Incus goes from resource-heavy operations to something more like metadata updates.<br /> <br /> ==Copy-on-Write Architecture==<br /> In traditional file systems, modifying a file involves overwriting existing data blocks on the disk drive. If a write operation is interrupted halfway through, the file system can suffer corruption or data loss. Copy-on-Write operates on a different mechanism. When data is modified on a Copy-on-Write file system, the system writes the new data to entirely new, unallocated disk blocks rather than overwriting the old blocks. Once the new write is successfully committed, the metadata pointers are updated to point to the new location.<br /> <br /> This architectural design provides two massive benefits for container and virtual machine platforms. First, it renders storage immune to data corruption caused by incomplete writes, as old data remains untouched until the new write is finalized. Second, it allows multiple storage entities to share the exact same underlying physical data blocks until one of those entities modifies a block. This block-sharing behavior is what makes instant snapshotting and zero-cost cloning possible inside Incus storage pools.<br /> <br /> ==ZFS in Incus==<br /> When integrated as an Incus storage pool driver, ZFS manages physical storage devices inside a structure known as a zpool. Within this pool, Incus automatically creates individual ZFS datasets for each container root file system and ZFS volumes for virtual machine block devices.<br /> <br /> ZFS employs end-to-end checksumming across all data blocks, protecting instances against silent data corruption, often known as bit rot. ZFS integrates native transparent compression using fast algorithms like ZSTD or LZ4. In practice, running dozens of Linux containers on a ZFS pool often gives compression ratios of two to one or higher, effectively doubling available disk capacity.<br /> <br /> When an administrator takes a snapshot of a container hosted on a ZFS pool, Incus invokes ZFS snapshot creation natively. The snapshot instantly freezes the dataset’s current metadata state. Because no actual file copying occurs, the snapshot completes in milliseconds regardless of whether the container occupies two gigabytes or two terabytes of disk space. ZFS snapshots consume zero additional storage space at the moment of creation. Storage overhead only grows gradually as the container mutates and new blocks are written to the pool. ZFS also is good at at volume replication, enabling native bit-stream transfer between Incus hosts via send and receive mechanisms.<br /> <br /> But, these enterprise features come with a resource requirement. ZFS relies heavily on host system memory to run its Adaptive Replacement Cache. For production environments with high memory capacity, ZFS can be the most resilient and scalable storage choice for Incus deployments.<br /> <br /> ==Btrfs in Incus==<br /> Btrfs is a native Linux Copy-on-Write file system designed to deliver storage capabilities without requiring complex setup or heavy RAM overhead. When configured as an Incus storage pool, the Btrfs driver organizes container filesystems into subvolumes. Each container, image, and snapshot exists as an isolated Btrfs subvolume within the overarching file system hierarchy.<br /> <br /> The main appeal of Btrfs in Incus is its low barrier to entry and lightweight resource footprint. Where as ZFS, which requires dedicated kernel modules and significant memory allocations, Btrfs is built directly into the mainline Linux kernel. This makes Btrfs a good choice for edge computing devices, developer laptops, single-board computers, and small-scale servers where memory capacity must be preserved for workloads rather than storage management.<br /> <br /> Inside Incus, Btrfs snapshotting works on the exact same Copy-on-Write philosophy as ZFS. Taking an instance snapshot creates a read-only or read-write Btrfs subvolume snapshot in real time. The new subvolume references the existing extents of the original dataset without duplicating physical storage blocks. This allows developers to take rapid, effortless snapshots before performing risky application updates or operating system upgrades.<br /> <br /> Btrfs excels at container management, you should note a specific design consideration regarding virtual machines. Because Btrfs is primarily an extent-based file system rather than a dedicated block manager, Incus stores virtual machine root disks as large loop files on top of Btrfs subvolumes. Random write operations within virtual machines on Btrfs can cause fragmentation over time. But, for container-centric workloads, Btrfs delivers performance, built-in subvolume tree management, and instant snapshot capabilities with minimal operational overhead.<br /> <br /> ==Instant Snapshots and Copy-on-Write Cloning==<br /> The combination of Incus with either ZFS or Btrfs changes day-to-day administrative workflows through instant snapshotting and copy-on-write cloning. A snapshot captures the complete state of an instance’s root file system at a precise moment in time. Because both storage engines rely on metadata pointer manipulation rather than bulk data duplication, snapshots complete instantly. Administrators can automate snapshot generation prior to automated system updates, ensuring that any breaking change can be reverted within seconds by restoring the previous snapshot state.<br /> <br /> Copy-on-Write storage pools dramatically accelerate instance provisioning. When launching a new container from a base image in Incus, the storage driver creates a thin clone directly from the cached image snapshot. Instead of uncompressing and expanding a rootfs tarball for every new container, Incus creates a writable child snapshot referencing the base image. Launching a new instance takes less than a second, while consuming virtually zero initial storage capacity. This capability is great in continuous integration pipelines and devops workflows, where hundreds of container environments are repeatedly spun up, tested, and destroyed within minutes.<br /> <br /> Selecting between ZFS and Btrfs for an Incus infrastructure depends on hardware resources, workload demands, and operational requirements. Systems equipped with ample memory and dedicated physical storage devices will benefit most from ZFS, utilizing its checksumming, cache hierarchy, and volume options. Conversely, systems running on tighter resource constraints or requiring seamless mainline kernel integration will find Btrfs to be an exceptionally versatile, performant option.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_28_2026&diff=4233 2026-07-28T01:02:01Z

<p>Tommy: Created page with &quot;=Incus Storage Pools using ZFS and Btrfs for Snapshots= Traditional file systems like ext4 paired with basic directory backends does give compatibility, but they don&#039;t have the capabilities required for large production environments. To really get the full potential of Incus particularly regarding fast deployment, resource efficiency, and instantaneous snapshots you need Copy-on-Write storage backends. For example these backends are ZFS and Btrfs, two storage technologie...&quot;</p> <hr /> <div>=Incus Storage Pools using ZFS and Btrfs for Snapshots=<br /> Traditional file systems like ext4 paired with basic directory backends does give compatibility, but they don't have the capabilities required for large production environments. To really get the full potential of Incus particularly regarding fast deployment, resource efficiency, and instantaneous snapshots you need Copy-on-Write storage backends. For example these backends are ZFS and Btrfs, two storage technologies that can change how virtualized storage is provisioned and maintained.<br /> <br /> ==Storage Pools in Incus==<br /> Incus abstracts storage management away from raw block devices and host paths through a unified construct called a storage pool. A storage pool is a designated storage space allocated to Incus, which the system uses to store instance root file systems, custom data volumes, base images, and snapshots. Establishing this abstraction layer, Incus decouples application workloads from the underlying hardware details. When an administrator launches a new container or virtual machine, Incus requests space from the specified storage pool, creating a storage volume tailored to that instance.<br /> <br /> The choice of storage driver configured for a pool determines how these volumes behave under the hood. When using a simple directory driver, creating a snapshot or cloning a container requires copying every single file using utility tools like rsync. This approach is slow, scales poorly with container size, and consumes large amounts of storage space. On the other hand, Copy-on-Write storage drivers use file system and volume management capabilities built directly into the Linux kernel. Managing storage through specialized drivers for ZFS or Btrfs, Incus goes from resource-heavy operations to something more like metadata updates.<br /> <br /> ==Copy-on-Write Architecture==<br /> In traditional file systems, modifying a file involves overwriting existing data blocks on the disk drive. If a write operation is interrupted halfway through, the file system can suffer corruption or data loss. Copy-on-Write operates on a different mechanism. When data is modified on a Copy-on-Write file system, the system writes the new data to entirely new, unallocated disk blocks rather than overwriting the old blocks. Once the new write is successfully committed, the metadata pointers are updated to point to the new location.<br /> <br /> This architectural design provides two massive benefits for container and virtual machine platforms. First, it renders storage immune to data corruption caused by incomplete writes, as old data remains untouched until the new write is finalized. Second, it allows multiple storage entities to share the exact same underlying physical data blocks until one of those entities modifies a block. This block-sharing behavior is what makes instant snapshotting and zero-cost cloning possible inside Incus storage pools.<br /> <br /> ==ZFS in Incus==<br /> When integrated as an Incus storage pool driver, ZFS manages physical storage devices inside a structure known as a zpool. Within this pool, Incus automatically creates individual ZFS datasets for each container root file system and ZFS volumes for virtual machine block devices.<br /> <br /> ZFS employs end-to-end checksumming across all data blocks, protecting instances against silent data corruption, often known as bit rot. ZFS integrates native transparent compression using fast algorithms like ZSTD or LZ4. In practice, running dozens of Linux containers on a ZFS pool often gives compression ratios of two to one or higher, effectively doubling available disk capacity.<br /> <br /> When an administrator takes a snapshot of a container hosted on a ZFS pool, Incus invokes ZFS snapshot creation natively. The snapshot instantly freezes the dataset’s current metadata state. Because no actual file copying occurs, the snapshot completes in milliseconds regardless of whether the container occupies two gigabytes or two terabytes of disk space. ZFS snapshots consume zero additional storage space at the moment of creation. Storage overhead only grows gradually as the container mutates and new blocks are written to the pool. ZFS also is good at at volume replication, enabling native bit-stream transfer between Incus hosts via send and receive mechanisms.<br /> <br /> But, these enterprise features come with a resource requirement. ZFS relies heavily on host system memory to run its Adaptive Replacement Cache. For production environments with high memory capacity, ZFS can be the most resilient and scalable storage choice for Incus deployments.<br /> <br /> ==Btrfs in Incus==<br /> Btrfs is a native Linux Copy-on-Write file system designed to deliver storage capabilities without requiring complex setup or heavy RAM overhead. When configured as an Incus storage pool, the Btrfs driver organizes container filesystems into subvolumes. Each container, image, and snapshot exists as an isolated Btrfs subvolume within the overarching file system hierarchy.<br /> <br /> The main appeal of Btrfs in Incus is its low barrier to entry and lightweight resource footprint. Where as ZFS, which requires dedicated kernel modules and significant memory allocations, Btrfs is built directly into the mainline Linux kernel. This makes Btrfs a good choice for edge computing devices, developer laptops, single-board computers, and small-scale servers where memory capacity must be preserved for workloads rather than storage management.<br /> <br /> Inside Incus, Btrfs snapshotting works on the exact same Copy-on-Write philosophy as ZFS. Taking an instance snapshot creates a read-only or read-write Btrfs subvolume snapshot in real time. The new subvolume references the existing extents of the original dataset without duplicating physical storage blocks. This allows developers to take rapid, effortless snapshots before performing risky application updates or operating system upgrades.<br /> <br /> Btrfs excels at container management, you should note a specific design consideration regarding virtual machines. Because Btrfs is primarily an extent-based file system rather than a dedicated block manager, Incus stores virtual machine root disks as large loop files on top of Btrfs subvolumes. Random write operations within virtual machines on Btrfs can cause fragmentation over time. But, for container-centric workloads, Btrfs delivers performance, built-in subvolume tree management, and instant snapshot capabilities with minimal operational overhead.<br /> <br /> ==Instant Snapshots and Copy-on-Write Cloning==<br /> The combination of Incus with either ZFS or Btrfs changes day-to-day administrative workflows through instant snapshotting and copy-on-write cloning. A snapshot captures the complete state of an instance’s root file system at a precise moment in time. Because both storage engines rely on metadata pointer manipulation rather than bulk data duplication, snapshots complete instantly. Administrators can automate snapshot generation prior to automated system updates, ensuring that any breaking change can be reverted within seconds by restoring the previous snapshot state.<br /> <br /> Copy-on-Write storage pools dramatically accelerate instance provisioning. When launching a new container from a base image in Incus, the storage driver creates a thin clone directly from the cached image snapshot. Instead of uncompressing and expanding a rootfs tarball for every new container, Incus creates a writable child snapshot referencing the base image. Launching a new instance takes less than a second, while consuming virtually zero initial storage capacity. This capability is great in continuous integration pipelines and devops workflows, where hundreds of container environments are repeatedly spun up, tested, and destroyed within minutes.<br /> <br /> Selecting between ZFS and Btrfs for an Incus infrastructure depends on hardware resources, workload demands, and operational requirements. Systems equipped with ample memory and dedicated physical storage devices will benefit most from ZFS, utilizing its checksumming, cache hierarchy, and volume options. Conversely, systems running on tighter resource constraints or requiring seamless mainline kernel integration will find Btrfs to be an exceptionally versatile, performant option.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4232 2026-07-28T00:41:30Z

<p>Tommy: /* July 2026 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> *[[Daily_Post_July_23_2026JP|LXDからIncusへの移行：オープンソース・システムコンテナの新たな標準 7/23/2026]]<br /> *[[Daily_Post_July_24_2026JP|単一のCLIからのコンテナと仮想マシンの統合管理 7/27/2026]]<br /> <br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> *[[Daily_Post_July_23_2026|Daily Post July 23 2026 - Migrating from LXD to Incus]]<br /> *[[Daily_Post_July_24_2026|Daily Post July 24 2026 - Managing Containers and Virtual Machines from One CLI]]<br /> *[[Daily_Post_July_27_2026|Daily Post July 27 2026 - Incus Networking OVN (Open Virtual Network) and Custom Bridges]]<br /> *[[Daily_Post_July_28_2026|Daily Post July 28 2026 - Incus Storage Pools using ZFS and Btrfs for Snapshots]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_27_2026&diff=4227 2026-07-27T01:43:14Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Advanced Incus Networking: OVN vs Custom Bridges Explained<br /> |description= Incus networking with custom Linux bridges, 802.1Q VLANs, and OVN software-defined networking. Compare distributed routing and Proxmox VE differences.<br /> |keywords= Incus, Incus Networking, OVN, Open Virtual Network, Open vSwitch, Custom Bridges, Linux Bridge, Geneve Tunnels, Proxmox VE, Software Defined Networking, Container Virtualization<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_27_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Incus Networking OVN (Open Virtual Network) and Custom Bridges=<br /> Managed bridge is the default on a new install and it provides immediate plug-and-play connectivity for basic workloads. However, enterprise infrastructures and self-hosted environments will outgrow simple setups. <br /> <br /> This is where advanced networking in Incus comes into play and it relies on two primary things '''Custom Linux Bridges''' and '''Open Virtual Network (OVN)'''. These two networking layers provide fine-grained traffic control, multi-tenant network isolation, transparent VLAN tagging, and scalable cross-host overlay networks.<br /> <br /> When you first initialize an Incus daemon, it typically creates a managed bridge named incusbr0. This default interface handles IP allocation via DHCP, sets up local NAT rules through iptables or nftables, and provides immediate internet outbound routing for instances. This is convenient, but the default model treats every instance as part of a single shared local subnet bound strictly to a single host.<br /> <br /> In enterprise production deployments or homelabs, relying solely on host-managed NAT bridges introduces some limitations. System administrators need containers to exist directly on physical local area network subnets, expose distinct public IPv4 or IPv6 addresses without layer 4 port translation, or communicate across multiple physical hypervisors on isolated overlay channels. Transitioning to custom Linux bridges or software-defined networking through OVN resolves these constraints by decoupling instance connectivity from basic host-level NAT.<br /> <br /> ==Custom Linux Bridges==<br /> These allow Incus instances to attach directly to host network interfaces that are configured outside of Incus itself. Instead of letting Incus manage the DHCP daemon, routing tables, and firewall rules, a custom bridge delegates network governance to your host operating system network manager, such as netplan, systemd-networkd, or traditional interfaces files.<br /> <br /> When you bind an Incus profile or instance network interface to an unmanaged custom Linux bridge like br0, the instance virtual Ethernet pair connects straight into the host bridge kernel module. This architecture effectively turns the host bridge into a virtual Layer 2 switch. Any container or virtual machine attached to this custom bridge appears directly on the physical network switch connected to the physical host NIC.<br /> <br /> The benefit of custom bridges is direct Layer 2 exposure. Instances can request IP addresses directly from external enterprise DHCP servers, announce their own IP addresses via ARP or Neighbor Discovery, and run network services on standard ports without relying on proxy devices or NAT rules. <br /> <br /> ==Configuration and Use Cases for Custom Bridges==<br /> Bridges help when combined with IEEE 802.1Q VLAN tagging. Creating a custom bridge on top of a physical VLAN interface for instance, bond0.100 for VLAN 100 Incus instances connected to that bridge automatically inherit the network isolation and routing policies configured on the physical network switch. Alternatively, Incus supports passing raw VLAN tags to instances on a trunked custom bridge, allowing individual instances to manage multiple tagged sub-interfaces internally.<br /> <br /> Custom bridges are also good for hosting network virtual appliances such as OPNsense, pfSense, or custom router containers. Attaching multiple custom bridges representing distinct physical or virtual network segments to a single router VM, you can construct firewall topologies directly inside Incus. In this pattern, Incus acts as a transparent hypervisor, leaving all Layer 3 routing, domain name resolution, and filtering to the dedicated virtual appliance.<br /> <br /> However, custom Linux bridges have scaling limits. Because traditional bridges operate strictly within the kernel of a single physical machine, stretching a bridge across multiple physical Incus hosts requires external physical network configuration like GRE tunnels, VXLAN interfaces managed at the OS level, or enterprise hardware switches supporting multi-chassis link aggregation. <br /> <br /> ==Software-Defined Networking with OVN==<br /> Open Virtual Network, or OVN, is an open-source software-defined networking system developed under the Open vSwitch project. Incus integrates natively with OVN to provide logical Layer 2 switches, logical Layer 3 routers, distributed firewalls, and dynamic network tunneling across single nodes and multi-node clusters alike.<br /> <br /> This is different from Linux bridges that forward frames between local interfaces, OVN introduces an abstraction layer above physical hardware. When you create an OVN network in Incus, you define a complete virtual network topology including logical subnets, gateway routers, static routes, and access control lists. Incus translates these human-readable declarations into logical flows stored within the OVN Northbound database. OVN daemons then translate these logical flows into physical OpenFlow rules executed by Open vSwitch instances on each hypervisor node.<br /> <br /> The primary architectural driver for choosing OVN is complete isolation combined with logical flexibility. In multi-tenant environments, different teams or applications can spin up overlapping IP subnets without colliding. OVN encapsulates packet traffic using Geneve tunnels, allowing logical networks to span across disparate host nodes regardless of the underlying physical network topology.<br /> <br /> ==Mechanics of Incus OVN Networks==<br /> An Incus OVN network relies on a host bridge to serve as its uplink, typically an unmanaged bridge or an Incus-managed bridge providing external connectivity. From there, OVN constructs virtual logical routers that perform SNAT and DNAT operations, IPv6 router advertisements, and distributed DHCP services directly within Open vSwitch, completely eliminating the need for separate dnsmasq processes per network.<br /> <br /> Security in OVN is built into the data plane rather than layered on top via host firewall rules. Incus leverages OVN Network ACLs to enforce stateful packet filtering at the virtual port level. This means firewall policies follow the instance wherever it migrates within an Incus cluster. If a container moves from Host A to Host B, its logical switch port bindings, firewall rules, and floating IP associations move with it without requiring physical network re-learning or switch reconfigurations.<br /> <br /> Additionally, OVN natively supports load balancing and Floating IPs. You can allocate public or external IP addresses from an uplink network and map them directly to private instance IPs running inside isolated OVN logical networks. This provides enterprise-grade ingress capabilities comparable to public cloud providers, allowing fine-grained exposure of individual services without exposing internal network structures.<br /> <br /> ==Multi-Host Clustering and Distributed Virtual Routing==<br /> In a standard multi-host cluster without OVN, instance communication across hosts must travel through traditional physical routing, requiring pre-allocated static routes or physical VLANs for every subnet. With OVN, Incus manages a fully distributed virtual router across all cluster members.<br /> <br /> When Instance A on Host 1 sends a packet to Instance B on Host 2 on the same logical network, the local Open vSwitch on Host 1 encapsulates the frame in a Geneve tunnel and transmits it directly across the physical network to Host 2. If the traffic requires Layer 3 routing between two different logical networks, the routing logic is executed locally on Host 1 before encapsulation, avoiding unnecessary hairpinned hops to a centralized gateway node.<br /> <br /> This distributed virtual routing architecture eliminates single points of failure and bandwidth bottlenecks. East-West traffic between containers on different hosts flows over short paths with minimal latency, while North-South traffic to the outer internet can be distributed across multiple chassis nodes equipped with external network uplinks.<br /> <br /> Deciding whether to implement custom Linux bridges or OVN depends on your structural scale, performance targets, and underlying infrastructure control. Custom Linux bridges are simple, zero software-defined networking overhead, and native performance for single-host topologies or environments where physical switches already manage VLANs and Layer 3 routing. They are good for high-throughput database workloads, bare-metal integration, and simple homelabs where instances need simple local LAN exposure.<br /> <br /> On the other hand, OVN is the ideal solution for multi-tenant environments, large Incus clusters, cloud-native deployments, and setups requiring programmatic network isolation. Although OVN introduces extra software components like Open vSwitch and OVN databases, it helps administrators with automated multi-host tunneling, integrated distributed firewalls, floating IPs, and cloud-like networking flexibility. <br /> <br /> ==Incus Networking vs. Proxmox VE==<br /> Comparing Incus networking to Proxmox VE shows distinct design philosophies in guest management and software-defined networking (SDN). Both platforms leverage standard Linux bridges for direct, host-level Layer 2 connectivity, their approaches to overlay networking, state synchronization, and SDN architecture are different.<br /> <br /> Proxmox VE structures its networking around a host-centric model, historically relying on standard Linux bridges, Open vSwitch, and its built-in SDN feature set introduced in recent releases. Proxmox SDN organizes networks using Zones and VNets, leaning heavily on traditional EVPN-BGP and VXLAN models to stretch Layer 2 networks across cluster nodes. Control plane synchronization across a Proxmox cluster depends on Corosync and the Proxmox Cluster File System (pmxcfs). This setup is okay at mapping virtual machines into existing enterprise VLANs and physical networking gear, it treats advanced overlay networking as an additional management layer sitting on top of host configurations.<br /> <br /> Incus treats network logical abstractions as first-class primitives integrated directly into its daemon and REST API. Instead of relying on Corosync or external BGP EVPN control planes for overlay networking, Incus embeds OVN as a native network provider. When running an Incus cluster, network state synchronizes via an integrated Raft consensus database rather than a shared cluster file system. This design allows Incus to program logical switches, distributed virtual routers, NAT rules, stateful ACL firewalls, and dynamic DHCP services across cluster nodes using Geneve encapsulation without requiring network fabric switches or external BGP daemons.<br /> <br /> Really.. the difference comes down to target use cases and operational ergonomics. Proxmox VE provides a GUI-driven operational experience tailored toward hypervisor-level virtual machine administration, making simple bridge and VLAN management immediately accessible for traditional virtualization admins. Incus provides an API-first, declarative model where OVN logical topologies including micro-segmentation, floating public IPs, and multi-tenant overlay routers can be spun up, modified, and torn down through CLI commands or infrastructure-as-code automation. Infrastructure engineers choosing between the two must weigh Proxmox's traditional hypervisor ecosystem against Incus's lightweight, programmable cloud-style SDN fabric.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_27_2026&diff=4226 2026-07-27T01:42:02Z

<p>Tommy: Created page with &quot;=Incus Networking OVN (Open Virtual Network) and Custom Bridges= Managed bridge is the default on a new install and it provides immediate plug-and-play connectivity for basic workloads. However, enterprise infrastructures and self-hosted environments will outgrow simple setups. This is where advanced networking in Incus comes into play and it relies on two primary things &#039;&#039;&#039;Custom Linux Bridges&#039;&#039;&#039; and &#039;&#039;&#039;Open Virtual Network (OVN)&#039;&#039;&#039;. These two networking layers provid...&quot;</p> <hr /> <div>=Incus Networking OVN (Open Virtual Network) and Custom Bridges=<br /> Managed bridge is the default on a new install and it provides immediate plug-and-play connectivity for basic workloads. However, enterprise infrastructures and self-hosted environments will outgrow simple setups. <br /> <br /> This is where advanced networking in Incus comes into play and it relies on two primary things '''Custom Linux Bridges''' and '''Open Virtual Network (OVN)'''. These two networking layers provide fine-grained traffic control, multi-tenant network isolation, transparent VLAN tagging, and scalable cross-host overlay networks.<br /> <br /> When you first initialize an Incus daemon, it typically creates a managed bridge named incusbr0. This default interface handles IP allocation via DHCP, sets up local NAT rules through iptables or nftables, and provides immediate internet outbound routing for instances. This is convenient, but the default model treats every instance as part of a single shared local subnet bound strictly to a single host.<br /> <br /> In enterprise production deployments or homelabs, relying solely on host-managed NAT bridges introduces some limitations. System administrators need containers to exist directly on physical local area network subnets, expose distinct public IPv4 or IPv6 addresses without layer 4 port translation, or communicate across multiple physical hypervisors on isolated overlay channels. Transitioning to custom Linux bridges or software-defined networking through OVN resolves these constraints by decoupling instance connectivity from basic host-level NAT.<br /> <br /> ==Custom Linux Bridges==<br /> These allow Incus instances to attach directly to host network interfaces that are configured outside of Incus itself. Instead of letting Incus manage the DHCP daemon, routing tables, and firewall rules, a custom bridge delegates network governance to your host operating system network manager, such as netplan, systemd-networkd, or traditional interfaces files.<br /> <br /> When you bind an Incus profile or instance network interface to an unmanaged custom Linux bridge like br0, the instance virtual Ethernet pair connects straight into the host bridge kernel module. This architecture effectively turns the host bridge into a virtual Layer 2 switch. Any container or virtual machine attached to this custom bridge appears directly on the physical network switch connected to the physical host NIC.<br /> <br /> The benefit of custom bridges is direct Layer 2 exposure. Instances can request IP addresses directly from external enterprise DHCP servers, announce their own IP addresses via ARP or Neighbor Discovery, and run network services on standard ports without relying on proxy devices or NAT rules. <br /> <br /> ==Configuration and Use Cases for Custom Bridges==<br /> Bridges help when combined with IEEE 802.1Q VLAN tagging. Creating a custom bridge on top of a physical VLAN interface for instance, bond0.100 for VLAN 100 Incus instances connected to that bridge automatically inherit the network isolation and routing policies configured on the physical network switch. Alternatively, Incus supports passing raw VLAN tags to instances on a trunked custom bridge, allowing individual instances to manage multiple tagged sub-interfaces internally.<br /> <br /> Custom bridges are also good for hosting network virtual appliances such as OPNsense, pfSense, or custom router containers. Attaching multiple custom bridges representing distinct physical or virtual network segments to a single router VM, you can construct firewall topologies directly inside Incus. In this pattern, Incus acts as a transparent hypervisor, leaving all Layer 3 routing, domain name resolution, and filtering to the dedicated virtual appliance.<br /> <br /> However, custom Linux bridges have scaling limits. Because traditional bridges operate strictly within the kernel of a single physical machine, stretching a bridge across multiple physical Incus hosts requires external physical network configuration like GRE tunnels, VXLAN interfaces managed at the OS level, or enterprise hardware switches supporting multi-chassis link aggregation. <br /> <br /> ==Software-Defined Networking with OVN==<br /> Open Virtual Network, or OVN, is an open-source software-defined networking system developed under the Open vSwitch project. Incus integrates natively with OVN to provide logical Layer 2 switches, logical Layer 3 routers, distributed firewalls, and dynamic network tunneling across single nodes and multi-node clusters alike.<br /> <br /> This is different from Linux bridges that forward frames between local interfaces, OVN introduces an abstraction layer above physical hardware. When you create an OVN network in Incus, you define a complete virtual network topology including logical subnets, gateway routers, static routes, and access control lists. Incus translates these human-readable declarations into logical flows stored within the OVN Northbound database. OVN daemons then translate these logical flows into physical OpenFlow rules executed by Open vSwitch instances on each hypervisor node.<br /> <br /> The primary architectural driver for choosing OVN is complete isolation combined with logical flexibility. In multi-tenant environments, different teams or applications can spin up overlapping IP subnets without colliding. OVN encapsulates packet traffic using Geneve tunnels, allowing logical networks to span across disparate host nodes regardless of the underlying physical network topology.<br /> <br /> ==Mechanics of Incus OVN Networks==<br /> An Incus OVN network relies on a host bridge to serve as its uplink, typically an unmanaged bridge or an Incus-managed bridge providing external connectivity. From there, OVN constructs virtual logical routers that perform SNAT and DNAT operations, IPv6 router advertisements, and distributed DHCP services directly within Open vSwitch, completely eliminating the need for separate dnsmasq processes per network.<br /> <br /> Security in OVN is built into the data plane rather than layered on top via host firewall rules. Incus leverages OVN Network ACLs to enforce stateful packet filtering at the virtual port level. This means firewall policies follow the instance wherever it migrates within an Incus cluster. If a container moves from Host A to Host B, its logical switch port bindings, firewall rules, and floating IP associations move with it without requiring physical network re-learning or switch reconfigurations.<br /> <br /> Additionally, OVN natively supports load balancing and Floating IPs. You can allocate public or external IP addresses from an uplink network and map them directly to private instance IPs running inside isolated OVN logical networks. This provides enterprise-grade ingress capabilities comparable to public cloud providers, allowing fine-grained exposure of individual services without exposing internal network structures.<br /> <br /> ==Multi-Host Clustering and Distributed Virtual Routing==<br /> In a standard multi-host cluster without OVN, instance communication across hosts must travel through traditional physical routing, requiring pre-allocated static routes or physical VLANs for every subnet. With OVN, Incus manages a fully distributed virtual router across all cluster members.<br /> <br /> When Instance A on Host 1 sends a packet to Instance B on Host 2 on the same logical network, the local Open vSwitch on Host 1 encapsulates the frame in a Geneve tunnel and transmits it directly across the physical network to Host 2. If the traffic requires Layer 3 routing between two different logical networks, the routing logic is executed locally on Host 1 before encapsulation, avoiding unnecessary hairpinned hops to a centralized gateway node.<br /> <br /> This distributed virtual routing architecture eliminates single points of failure and bandwidth bottlenecks. East-West traffic between containers on different hosts flows over short paths with minimal latency, while North-South traffic to the outer internet can be distributed across multiple chassis nodes equipped with external network uplinks.<br /> <br /> Deciding whether to implement custom Linux bridges or OVN depends on your structural scale, performance targets, and underlying infrastructure control. Custom Linux bridges are simple, zero software-defined networking overhead, and native performance for single-host topologies or environments where physical switches already manage VLANs and Layer 3 routing. They are good for high-throughput database workloads, bare-metal integration, and simple homelabs where instances need simple local LAN exposure.<br /> <br /> On the other hand, OVN is the ideal solution for multi-tenant environments, large Incus clusters, cloud-native deployments, and setups requiring programmatic network isolation. Although OVN introduces extra software components like Open vSwitch and OVN databases, it helps administrators with automated multi-host tunneling, integrated distributed firewalls, floating IPs, and cloud-like networking flexibility. <br /> <br /> ==Incus Networking vs. Proxmox VE==<br /> Comparing Incus networking to Proxmox VE shows distinct design philosophies in guest management and software-defined networking (SDN). Both platforms leverage standard Linux bridges for direct, host-level Layer 2 connectivity, their approaches to overlay networking, state synchronization, and SDN architecture are different.<br /> <br /> Proxmox VE structures its networking around a host-centric model, historically relying on standard Linux bridges, Open vSwitch, and its built-in SDN feature set introduced in recent releases. Proxmox SDN organizes networks using Zones and VNets, leaning heavily on traditional EVPN-BGP and VXLAN models to stretch Layer 2 networks across cluster nodes. Control plane synchronization across a Proxmox cluster depends on Corosync and the Proxmox Cluster File System (pmxcfs). This setup is okay at mapping virtual machines into existing enterprise VLANs and physical networking gear, it treats advanced overlay networking as an additional management layer sitting on top of host configurations.<br /> <br /> Incus treats network logical abstractions as first-class primitives integrated directly into its daemon and REST API. Instead of relying on Corosync or external BGP EVPN control planes for overlay networking, Incus embeds OVN as a native network provider. When running an Incus cluster, network state synchronizes via an integrated Raft consensus database rather than a shared cluster file system. This design allows Incus to program logical switches, distributed virtual routers, NAT rules, stateful ACL firewalls, and dynamic DHCP services across cluster nodes using Geneve encapsulation without requiring network fabric switches or external BGP daemons.<br /> <br /> Really.. the difference comes down to target use cases and operational ergonomics. Proxmox VE provides a GUI-driven operational experience tailored toward hypervisor-level virtual machine administration, making simple bridge and VLAN management immediately accessible for traditional virtualization admins. Incus provides an API-first, declarative model where OVN logical topologies including micro-segmentation, floating public IPs, and multi-tenant overlay routers can be spun up, modified, and torn down through CLI commands or infrastructure-as-code automation. Infrastructure engineers choosing between the two must weigh Proxmox's traditional hypervisor ecosystem against Incus's lightweight, programmable cloud-style SDN fabric.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4225 2026-07-27T01:14:06Z

<p>Tommy: /* English */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> *[[Daily_Post_July_23_2026JP|LXDからIncusへの移行：オープンソース・システムコンテナの新たな標準 7/23/2026]]<br /> <br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> *[[Daily_Post_July_23_2026|Daily Post July 23 2026 - Migrating from LXD to Incus]]<br /> *[[Daily_Post_July_24_2026|Daily Post July 24 2026 - Managing Containers and Virtual Machines from One CLI]]<br /> *[[Daily_Post_July_27_2026|Daily Post July 27 2026 - Incus Networking OVN (Open Virtual Network) and Custom Bridges]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4224 2026-07-27T01:13:11Z

<p>Tommy: /* July 2026 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> *[[Daily_Post_July_23_2026JP|LXDからIncusへの移行：オープンソース・システムコンテナの新たな標準 7/23/2026]]<br /> <br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> *[[Daily_Post_July_23_2026|Daily Post July 23 2026 - Migrating from LXD to Incus]]<br /> *[[Daily_Post_July_24_2026|Daily Post July 24 2026 - Managing Containers and Virtual Machines from One CLI]]<br /> *[[Daily_Post_July_27_2026|Daily Post July 27 2026 - Incus Networking OVN (Open Virtual Network) and Custom Bridges<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_24_2026&diff=4223 2026-07-24T02:45:25Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Incus Architecture: Managing Containers and Virtual Machines from One CLI<br /> |description= An architectural overview of Incus, explaining its unified daemon, REST API, storage drivers, networking layers, and dual-engine orchestration for containers and VMs.<br /> |keywords= Incus, Linux Containers, LXC, QEMU, KVM, System Containers, Virtual Machines, Container Architecture, Virtualization, incusd, dqlite, OVN<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_24_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Managing Containers and Virtual Machines from One CLI=<br /> Light container technologies provided near-instant boot times and minimal resource overhead by sharing the host kernel. On the other hand, traditional hypervisors offered complete kernel isolation and cross-platform flexibility at the cost of higher memory consumption and slower initialization. Operating both environments typically meant maintaining disparate toolchains, distinct network configurations, and separate storage mechanisms.<br /> <br /> While both Incus and Proxmox VE (PVE) trie to solve the same core problem managing both system containers (LXC) and full virtual machines (QEMU/KVM) from a single platform they approach this goal from different design philosophies, architectures, and target use case/<br /> <br /> '''Orchestration Engine vs. Turnkey OS'''<br /> *Proxmox VE is a complete Linux distribution. Proxmox is built as a custom Debian-based operating system designed to turn bare-metal servers into hypervisors out of the box. It packages Debian, LXC, QEMU/KVM, Corosync, and its own web interface into a monolithic, integrated platform.<br /> *Incus is a composable daemon and CLI. Incus is an application/service that runs on top of almost any existing Linux distribution (Ubuntu, Debian, Fedora, Arch, Alpine, etc.). It acts as a lightweight daemon (incusd) with a REST API and CLI tool (incus). You bring your preferred base host OS, and Incus runs as the compute orchestrator on top.<br /> <br /> '''API-First CLI vs. Web-First Management'''<br /> *Proxmox VE is web-centric. Proxmox is built around its Web GUI (PVE Web UI). While it has command-line utilities (pct for containers, qm for virtual machines, pvecm for clusters), these are distinct tools built for specific subsystems rather than a single unified client tool.<br /> *Incus is API/CLI-centric. Incus provides a single, unified command-line interface (incus) for all operations managing containers, VMs, storage, and networking uses the exact same syntax. Everything in Incus flows through a single REST API, making remote execution, automation, and CI/CD integration good without needing a web interface (though third-party GUIs exist).<br /> <br /> '''LXC and VM Handling Paradigms'''<br /> *Proxmox treats containers and VMs differently in the CLI. In Proxmox, a container is created with pct create, whereas a VM is created with qm create. They have separate configuration files, separate parameter formats, and slightly different feature sets within the management layer.<br /> *Incus treats containers and VMs identically in the abstraction layer. In Incus, an instance is an instance. You launch a container with incus launch images:ubuntu/22.04 my-container and a full virtual machine with incus launch images:ubuntu/22.04 my-vm --vm. They share the same profile system, storage syntax, network attaching logic, and lifecycle commands (start, stop, snapshot, migrate).<br /> <br /> '''Clustering and Database Architecture'''<br /> *Proxmox clusters rely on pmxcfs (a fuse-based cluster filesystem synchronized via Corosync). It is optimized for smaller to medium-sized clusters (typically 3 to 32 nodes) and requires dedicated, low-latency cluster communication networks to prevent quorum issues.<br /> *Incus has a native distributed SQLite database (dqlite) driven by the Raft consensus algorithm embedded directly inside the incusd daemon. Any node in an Incus cluster can handle API calls, and the cluster scales without requiring an external cluster filesystem layer like Corosync.<br /> <br /> One way to look at it is, Proxmox VE as an open-source alternative to VMware vSphere or Nutanix—a turnkey, appliance-like hypervisor with a web dashboard for managing infrastructure visually.<br /> <br /> And Incus as a lightweight, public-cloud-style engine (similar to AWS EC2 or OpenStack primitives) running directly on bare-metal Linux—designed for developers and sysadmins who prefer fast CLI interactions, declarative profiles, scriptability, and minimal overhead.<br /> <br /> ==The Daemon and the Unified REST API Architecture==<br /> Incus architecture is a single background service, incusd, written in Go. This daemon is responsible for managing the entire lifecycle of all instances, storage pools, network interfaces, and security policies on a host system. Rather than tying management logic directly to the command-line client, Incus exposes all functionality through a clean, event-driven REST API.<br /> <br /> The Incus command-line tool (incus) acts purely as a REST client. Whether you execute commands locally over a Unix domain socket or remotely over an encrypted TLS connection, the underlying API endpoints remain identical. This design decouples the user experience from the physical location of the hypervisor host. A developer working on a laptop can execute the exact same commands against local containers, a remote bare-metal server, or a distant multi-node cluster, operating with full feature parity without needing extra middleware or management plugins.<br /> <br /> ==Container and Virtual Machine Runtime Engines==<br /> Incus presents a uniform management interface to the user, it intelligently drives two distinct underlying runtime engines to launch workloads depending on the required isolation level.<br /> <br /> When launching a system container, Incus interfaces directly with liblxc to leverage native Linux kernel features such as namespaces, control groups (cgroups), and seccomp filtering. System containers simulate a complete Linux operating system including systemd init processes, system logs, and background services while sharing the host kernel. Incus emphasizes security by default, running containers as unprivileged instances using user namespace mappings. This maps root inside the container to an unprivileged user ID on the host host system, dramatically reducing the risk of container breakouts.<br /> <br /> When full hardware isolation or a non-native kernel is required, Incus switches its backend driver to QEMU and KVM hardware virtualization. To maintain operational consistency, Incus embeds a lightweight helper utility, incus-agent, inside the virtual machine guest image. This agent communicates back to the parent incusd daemon, enabling features like file transfers, live executive console attachment, and guest system metrics collection. Because Incus handles the QEMU command-line flags and driver instantiations internally, users can spawn a fully isolated Linux or non-Linux virtual machine using the exact same CLI command structure used for containers, simply appending a flag to designate VM mode.<br /> <br /> ==Storage and Network Abstraction Layers==<br /> An architectural strength of Incus is its ability to share storage backends and networking topologies across both containers and virtual machines without requiring custom hardware configurations.<br /> <br /> The Incus storage driver abstraction layer supports multiple enterprise backends, including ZFS, Btrfs, LVM, raw directory structures, and distributed Ceph storage. Storage pools are defined independently of the compute workloads. When an instance is launched, Incus automatically provisions storage volumes according to the driver capabilities utilizing copy-on-write dataset cloning for ZFS or Btrfs, or thin-provisioned logical volumes for LVM. This design allows instant snapshotting, fast template cloning, and easy live migration of both containers and virtual machines across physical storage nodes.<br /> <br /> Networking in Incus follows a similarly abstract model. Administrators can create native Linux bridges, Open Virtual Network overlay networks, or macvlan configurations. Incus automatically manages DHCP allocation, DNS resolution, and firewall rules for connected instances. Devices such as network interface cards, physical GPUs, USB devices, or raw disk paths can be dynamically attached or hot-plugged into running instances using uniform API calls, whether the target guest is running inside a lightweight system container or inside a QEMU virtual machine.<br /> <br /> ==Profile-Based Configuration Management==<br /> Declarative configuration management is embedded into the Incus architecture through the use of profiles. Profiles act as reusable configuration templates that specify resource limits, attached devices, storage pools, environment variables, and network connections.<br /> <br /> Multiple profiles can be cascaded and applied to an instance at launch or updated while the instance is running. For example, a default profile might define standard network bridging and primary storage pool attachments, while a secondary profile imposes memory limits, CPU pinning constraints, or custom firewall configurations. Because profiles apply transparently across both system containers and virtual machines, operations teams can enforce security baselines and resource quotas across heterogeneous compute workloads without writing bespoke scripts for different hypervisor tools.<br /> <br /> ==Distributed Clustering and High Availability==<br /> Incus scales from a single developer machine up to massive enterprise data center clusters. That is different from traditional virtual machine managers that rely on enterprise cluster managers like Corosync or Pacemaker, Incus features a native, built-in distributed architecture.<br /> <br /> An Incus cluster consists of multiple physical nodes connected together to share a single unified view of the environment. Cluster state is synchronized using an embedded relational database engine driven by the Raft consensus algorithm. This distributed transactional database ensures strong consistency across all cluster nodes without single points of failure. When managing a cluster, any node can receive CLI requests and route operations to the target host transparently. If a node fails, Incus can automatically rebalance or restart high-availability workloads on healthy remaining nodes, providing infrastructure resilience with minimal operational overhead.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_24_2026&diff=4222 2026-07-24T02:44:24Z

<p>Tommy: </p> <hr /> <div>=Managing Containers and Virtual Machines from One CLI=<br /> Light container technologies provided near-instant boot times and minimal resource overhead by sharing the host kernel. On the other hand, traditional hypervisors offered complete kernel isolation and cross-platform flexibility at the cost of higher memory consumption and slower initialization. Operating both environments typically meant maintaining disparate toolchains, distinct network configurations, and separate storage mechanisms.<br /> <br /> While both Incus and Proxmox VE (PVE) trie to solve the same core problem managing both system containers (LXC) and full virtual machines (QEMU/KVM) from a single platform they approach this goal from different design philosophies, architectures, and target use case/<br /> <br /> '''Orchestration Engine vs. Turnkey OS'''<br /> *Proxmox VE is a complete Linux distribution. Proxmox is built as a custom Debian-based operating system designed to turn bare-metal servers into hypervisors out of the box. It packages Debian, LXC, QEMU/KVM, Corosync, and its own web interface into a monolithic, integrated platform.<br /> *Incus is a composable daemon and CLI. Incus is an application/service that runs on top of almost any existing Linux distribution (Ubuntu, Debian, Fedora, Arch, Alpine, etc.). It acts as a lightweight daemon (incusd) with a REST API and CLI tool (incus). You bring your preferred base host OS, and Incus runs as the compute orchestrator on top.<br /> <br /> '''API-First CLI vs. Web-First Management'''<br /> *Proxmox VE is web-centric. Proxmox is built around its Web GUI (PVE Web UI). While it has command-line utilities (pct for containers, qm for virtual machines, pvecm for clusters), these are distinct tools built for specific subsystems rather than a single unified client tool.<br /> *Incus is API/CLI-centric. Incus provides a single, unified command-line interface (incus) for all operations managing containers, VMs, storage, and networking uses the exact same syntax. Everything in Incus flows through a single REST API, making remote execution, automation, and CI/CD integration good without needing a web interface (though third-party GUIs exist).<br /> <br /> '''LXC and VM Handling Paradigms'''<br /> *Proxmox treats containers and VMs differently in the CLI. In Proxmox, a container is created with pct create, whereas a VM is created with qm create. They have separate configuration files, separate parameter formats, and slightly different feature sets within the management layer.<br /> *Incus treats containers and VMs identically in the abstraction layer. In Incus, an instance is an instance. You launch a container with incus launch images:ubuntu/22.04 my-container and a full virtual machine with incus launch images:ubuntu/22.04 my-vm --vm. They share the same profile system, storage syntax, network attaching logic, and lifecycle commands (start, stop, snapshot, migrate).<br /> <br /> '''Clustering and Database Architecture'''<br /> *Proxmox clusters rely on pmxcfs (a fuse-based cluster filesystem synchronized via Corosync). It is optimized for smaller to medium-sized clusters (typically 3 to 32 nodes) and requires dedicated, low-latency cluster communication networks to prevent quorum issues.<br /> *Incus has a native distributed SQLite database (dqlite) driven by the Raft consensus algorithm embedded directly inside the incusd daemon. Any node in an Incus cluster can handle API calls, and the cluster scales without requiring an external cluster filesystem layer like Corosync.<br /> <br /> One way to look at it is, Proxmox VE as an open-source alternative to VMware vSphere or Nutanix—a turnkey, appliance-like hypervisor with a web dashboard for managing infrastructure visually.<br /> <br /> And Incus as a lightweight, public-cloud-style engine (similar to AWS EC2 or OpenStack primitives) running directly on bare-metal Linux—designed for developers and sysadmins who prefer fast CLI interactions, declarative profiles, scriptability, and minimal overhead.<br /> <br /> ==The Daemon and the Unified REST API Architecture==<br /> Incus architecture is a single background service, incusd, written in Go. This daemon is responsible for managing the entire lifecycle of all instances, storage pools, network interfaces, and security policies on a host system. Rather than tying management logic directly to the command-line client, Incus exposes all functionality through a clean, event-driven REST API.<br /> <br /> The Incus command-line tool (incus) acts purely as a REST client. Whether you execute commands locally over a Unix domain socket or remotely over an encrypted TLS connection, the underlying API endpoints remain identical. This design decouples the user experience from the physical location of the hypervisor host. A developer working on a laptop can execute the exact same commands against local containers, a remote bare-metal server, or a distant multi-node cluster, operating with full feature parity without needing extra middleware or management plugins.<br /> <br /> ==Container and Virtual Machine Runtime Engines==<br /> Incus presents a uniform management interface to the user, it intelligently drives two distinct underlying runtime engines to launch workloads depending on the required isolation level.<br /> <br /> When launching a system container, Incus interfaces directly with liblxc to leverage native Linux kernel features such as namespaces, control groups (cgroups), and seccomp filtering. System containers simulate a complete Linux operating system including systemd init processes, system logs, and background services while sharing the host kernel. Incus emphasizes security by default, running containers as unprivileged instances using user namespace mappings. This maps root inside the container to an unprivileged user ID on the host host system, dramatically reducing the risk of container breakouts.<br /> <br /> When full hardware isolation or a non-native kernel is required, Incus switches its backend driver to QEMU and KVM hardware virtualization. To maintain operational consistency, Incus embeds a lightweight helper utility, incus-agent, inside the virtual machine guest image. This agent communicates back to the parent incusd daemon, enabling features like file transfers, live executive console attachment, and guest system metrics collection. Because Incus handles the QEMU command-line flags and driver instantiations internally, users can spawn a fully isolated Linux or non-Linux virtual machine using the exact same CLI command structure used for containers, simply appending a flag to designate VM mode.<br /> <br /> ==Storage and Network Abstraction Layers==<br /> An architectural strength of Incus is its ability to share storage backends and networking topologies across both containers and virtual machines without requiring custom hardware configurations.<br /> <br /> The Incus storage driver abstraction layer supports multiple enterprise backends, including ZFS, Btrfs, LVM, raw directory structures, and distributed Ceph storage. Storage pools are defined independently of the compute workloads. When an instance is launched, Incus automatically provisions storage volumes according to the driver capabilities utilizing copy-on-write dataset cloning for ZFS or Btrfs, or thin-provisioned logical volumes for LVM. This design allows instant snapshotting, fast template cloning, and easy live migration of both containers and virtual machines across physical storage nodes.<br /> <br /> Networking in Incus follows a similarly abstract model. Administrators can create native Linux bridges, Open Virtual Network overlay networks, or macvlan configurations. Incus automatically manages DHCP allocation, DNS resolution, and firewall rules for connected instances. Devices such as network interface cards, physical GPUs, USB devices, or raw disk paths can be dynamically attached or hot-plugged into running instances using uniform API calls, whether the target guest is running inside a lightweight system container or inside a QEMU virtual machine.<br /> <br /> ==Profile-Based Configuration Management==<br /> Declarative configuration management is embedded into the Incus architecture through the use of profiles. Profiles act as reusable configuration templates that specify resource limits, attached devices, storage pools, environment variables, and network connections.<br /> <br /> Multiple profiles can be cascaded and applied to an instance at launch or updated while the instance is running. For example, a default profile might define standard network bridging and primary storage pool attachments, while a secondary profile imposes memory limits, CPU pinning constraints, or custom firewall configurations. Because profiles apply transparently across both system containers and virtual machines, operations teams can enforce security baselines and resource quotas across heterogeneous compute workloads without writing bespoke scripts for different hypervisor tools.<br /> <br /> ==Distributed Clustering and High Availability==<br /> Incus scales from a single developer machine up to massive enterprise data center clusters. That is different from traditional virtual machine managers that rely on enterprise cluster managers like Corosync or Pacemaker, Incus features a native, built-in distributed architecture.<br /> <br /> An Incus cluster consists of multiple physical nodes connected together to share a single unified view of the environment. Cluster state is synchronized using an embedded relational database engine driven by the Raft consensus algorithm. This distributed transactional database ensures strong consistency across all cluster nodes without single points of failure. When managing a cluster, any node can receive CLI requests and route operations to the target host transparently. If a node fails, Incus can automatically rebalance or restart high-availability workloads on healthy remaining nodes, providing infrastructure resilience with minimal operational overhead.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_24_2026&diff=4221 2026-07-24T02:35:41Z

<p>Tommy: </p> <hr /> <div>=Managing Containers and Virtual Machines from One CLI=<br /> Light container technologies provided near-instant boot times and minimal resource overhead by sharing the host kernel. On the other hand, traditional hypervisors offered complete kernel isolation and cross-platform flexibility at the cost of higher memory consumption and slower initialization. Operating both environments typically meant maintaining disparate toolchains, distinct network configurations, and separate storage mechanisms.<br /> <br /> While both Incus and Proxmox VE (PVE) trie to solve the same core problem managing both system containers (LXC) and full virtual machines (QEMU/KVM) from a single platform they approach this goal from different design philosophies, architectures, and target use case/<br /> <br /> '''Orchestration Engine vs. Turnkey OS'''<br /> *Proxmox VE is a complete Linux distribution. Proxmox is built as a custom Debian-based operating system designed to turn bare-metal servers into hypervisors out of the box. It packages Debian, LXC, QEMU/KVM, Corosync, and its own web interface into a monolithic, integrated platform.<br /> *Incus is a composable daemon and CLI. Incus is an application/service that runs on top of almost any existing Linux distribution (Ubuntu, Debian, Fedora, Arch, Alpine, etc.). It acts as a lightweight daemon (incusd) with a REST API and CLI tool (incus). You bring your preferred base host OS, and Incus runs as the compute orchestrator on top.<br /> <br /> '''API-First CLI vs. Web-First Management'''<br /> *Proxmox VE is web-centric. Proxmox is built around its Web GUI (PVE Web UI). While it has command-line utilities (pct for containers, qm for virtual machines, pvecm for clusters), these are distinct tools built for specific subsystems rather than a single unified client tool.<br /> *Incus is API/CLI-centric. Incus provides a single, unified command-line interface (incus) for all operations managing containers, VMs, storage, and networking uses the exact same syntax. Everything in Incus flows through a single REST API, making remote execution, automation, and CI/CD integration good without needing a web interface (though third-party GUIs exist).<br /> <br /> '''LXC and VM Handling Paradigms'''<br /> *Proxmox treats containers and VMs differently in the CLI. In Proxmox, a container is created with pct create, whereas a VM is created with qm create. They have separate configuration files, separate parameter formats, and slightly different feature sets within the management layer.<br /> *Incus treats containers and VMs identically in the abstraction layer. In Incus, an instance is an instance. You launch a container with incus launch images:ubuntu/22.04 my-container and a full virtual machine with incus launch images:ubuntu/22.04 my-vm --vm. They share the same profile system, storage syntax, network attaching logic, and lifecycle commands (start, stop, snapshot, migrate).<br /> <br /> '''Clustering and Database Architecture'''<br /> *Proxmox clusters rely on pmxcfs (a fuse-based cluster filesystem synchronized via Corosync). It is optimized for smaller to medium-sized clusters (typically 3 to 32 nodes) and requires dedicated, low-latency cluster communication networks to prevent quorum issues.<br /> *Incus has a native distributed SQLite database (dqlite) driven by the Raft consensus algorithm embedded directly inside the incusd daemon. Any node in an Incus cluster can handle API calls, and the cluster scales without requiring an external cluster filesystem layer like Corosync.<br /> <br /> One way to look at it is, Proxmox VE as an open-source alternative to VMware vSphere or Nutanix—a turnkey, appliance-like hypervisor with a web dashboard for managing infrastructure visually.<br /> <br /> And Incus as a lightweight, public-cloud-style engine (similar to AWS EC2 or OpenStack primitives) running directly on bare-metal Linux—designed for developers and sysadmins who prefer fast CLI interactions, declarative profiles, scriptability, and minimal overhead.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_24_2026&diff=4220 2026-07-24T02:34:58Z

<p>Tommy: Created page with &quot;=Managing Containers and Virtual Machines from One CLI= Light container technologies provided near-instant boot times and minimal resource overhead by sharing the host kernel. On the other hand, traditional hypervisors offered complete kernel isolation and cross-platform flexibility at the cost of higher memory consumption and slower initialization. Operating both environments typically meant maintaining disparate toolchains, distinct network configurations, and separate...&quot;</p> <hr /> <div>=Managing Containers and Virtual Machines from One CLI=<br /> Light container technologies provided near-instant boot times and minimal resource overhead by sharing the host kernel. On the other hand, traditional hypervisors offered complete kernel isolation and cross-platform flexibility at the cost of higher memory consumption and slower initialization. Operating both environments typically meant maintaining disparate toolchains, distinct network configurations, and separate storage mechanisms.<br /> <br /> While both Incus and Proxmox VE (PVE) trie to solve the same core problem managing both system containers (LXC) and full virtual machines (QEMU/KVM) from a single platform they approach this goal from different design philosophies, architectures, and target use case/<br /> <br /> #Orchestration Engine vs. Turnkey OS<br /> *Proxmox VE is a complete Linux distribution. Proxmox is built as a custom Debian-based operating system designed to turn bare-metal servers into hypervisors out of the box. It packages Debian, LXC, QEMU/KVM, Corosync, and its own web interface into a monolithic, integrated platform.<br /> *Incus is a composable daemon and CLI. Incus is an application/service that runs on top of almost any existing Linux distribution (Ubuntu, Debian, Fedora, Arch, Alpine, etc.). It acts as a lightweight daemon (incusd) with a REST API and CLI tool (incus). You bring your preferred base host OS, and Incus runs as the compute orchestrator on top.<br /> <br /> #API-First CLI vs. Web-First Management<br /> *Proxmox VE is web-centric. Proxmox is built around its Web GUI (PVE Web UI). While it has command-line utilities (pct for containers, qm for virtual machines, pvecm for clusters), these are distinct tools built for specific subsystems rather than a single unified client tool.<br /> *Incus is API/CLI-centric. Incus provides a single, unified command-line interface (incus) for all operations managing containers, VMs, storage, and networking uses the exact same syntax. Everything in Incus flows through a single REST API, making remote execution, automation, and CI/CD integration good without needing a web interface (though third-party GUIs exist).<br /> <br /> #LXC and VM Handling Paradigms<br /> *Proxmox treats containers and VMs differently in the CLI. In Proxmox, a container is created with pct create, whereas a VM is created with qm create. They have separate configuration files, separate parameter formats, and slightly different feature sets within the management layer.<br /> *Incus treats containers and VMs identically in the abstraction layer. In Incus, an instance is an instance. You launch a container with incus launch images:ubuntu/22.04 my-container and a full virtual machine with incus launch images:ubuntu/22.04 my-vm --vm. They share the same profile system, storage syntax, network attaching logic, and lifecycle commands (start, stop, snapshot, migrate).<br /> <br /> #Clustering and Database Architecture<br /> *Proxmox clusters rely on pmxcfs (a fuse-based cluster filesystem synchronized via Corosync). It is optimized for smaller to medium-sized clusters (typically 3 to 32 nodes) and requires dedicated, low-latency cluster communication networks to prevent quorum issues.<br /> *Incus has a native distributed SQLite database (dqlite) driven by the Raft consensus algorithm embedded directly inside the incusd daemon. Any node in an Incus cluster can handle API calls, and the cluster scales without requiring an external cluster filesystem layer like Corosync.<br /> <br /> One way to look at it is, Proxmox VE as an open-source alternative to VMware vSphere or Nutanix—a turnkey, appliance-like hypervisor with a web dashboard for managing infrastructure visually.<br /> <br /> And Incus as a lightweight, public-cloud-style engine (similar to AWS EC2 or OpenStack primitives) running directly on bare-metal Linux—designed for developers and sysadmins who prefer fast CLI interactions, declarative profiles, scriptability, and minimal overhead.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4219 2026-07-24T02:18:15Z

<p>Tommy: /* July 2026 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> *[[Daily_Post_July_23_2026JP|LXDからIncusへの移行：オープンソース・システムコンテナの新たな標準 7/23/2026]]<br /> <br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> *[[Daily_Post_July_23_2026|Daily Post July 23 2026 - Migrating from LXD to Incus]]<br /> *[[Daily_Post_July_24_2026|Daily Post July 24 2026 - Managing Containers and Virtual Machines from One CLI]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_23_2026&diff=4214 2026-07-23T01:04:08Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Migrating from LXD to Incus: Why and How to Make the Switch<br /> |description= A comprehensive guide on LXD and Incus, explaining the Canonical fork, project roadmap, and step-by-step migration process for system containers and VMs.<br /> |keywords= Incus, LXD, Linux Containers, LXC, Canonical, System Containers, QEMU, VM Migration, Open Source, lxd-to-incus, Container Virtualization<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_23_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Migrating from LXD to Incus=<br /> For years, containerization on Linux was dominated by two primary paradigms. On one side stood application container engines like Docker and Podman, designed to package isolated, single-process microservices. On the other side stood system container technologies, which provide lightweight virtual environments that behave, look, and feel like full-blown Linux operating systems without the performance overhead of full hardware virtualization. At the center of this system container realm was LXD. However, significant governance shifts, licensing changes, and strategic corporate decisions have changed that cuased the fork to Incus as the new standard bearer for open-source system containers and lightweight virtual machines. Understanding this evolution, why the ecosystem split, and how to execute a migration is important for sysadmins, DevOps engineers, and infrastructure architects.<br /> <br /> ==Understanding LXD==<br /> To understand the current state of system container management, you must first look at LXD. Originally launched under the umbrella of the Linux Containers project with primary sponsorship from Canonical, LXD was built as a REST API-driven daemon built on top of LXC (Linux Containers). Bare LXC provided low-level primitives for interacting with kernel namespaces, cgroups, and capabilities, LXD brought a polished, user-friendly interface to manage container lifecycles, storage pools, networks, and cluster deployments.<br /> <br /> LXD filled a niche between traditional hypervisors like KVM or VMware and application containers like Docker. It allowed users to run entire Linux distributions complete with init systems like systemd, SSH daemons, package managers, and cron jobs inside isolated kernel containers that booted in seconds and consumed minimal memory. Later versions of LXD even expanded to manage full QEMU-based virtual machines through the exact same unified REST API and command-line interface, giving operators a single tool to manage both light containers and heavy virtual machines.<br /> <br /> ==Enter Incus==<br /> Incus is a fully open-source, community-driven daemon designed to manage system containers and virtual machines. Created in mid-2023 under the Linux Containers project umbrella, Incus is a direct fork of LXD. It retains the underlying architectural strengths that made LXD popular while steering the project back toward community-led development, open governance, and traditional open-source software licensing.<br /> <br /> The project was spearheaded by Aleksa Sarai and longtime LXD lead developer Stéphane Graber, along with other core contributors from the original project. Incus aims to provide a reliable, flexible platform for running containers and virtual machines across diverse deployment environments, ranging from single-node homelabs to multi-node enterprise production clusters. Maintaining familiar operational paradigms, Incus has diverged from LXD by removing legacy tech debt, improving security defaults, introducing native support for OCI container images, and expanding integration with identity providers like OpenFGA and OpenID Connect.<br /> <br /> ==The Rift==<br /> The split between LXD and Incus was not caused by technical disagreements over software architecture, but rather by fundamental shifts in corporate strategy and project governance. In July 2023, Canonical made the sudden corporate decision to take direct control of the LXD project. Prior to this decision, LXD had operated as a community project under the Linux Containers umbrella, even though Canonical was its primary funder and employed most of its core maintainers. Canonical moved the LXD codebase out of the Linux Containers repository, relocated discussion forums to Canonical platforms, and required contributors to sign a Canonical Contributor License Agreement.<br /> <br /> Canonical's strategic rationale stemmed from a desire to integrate LXD into its commercial product portfolio, particularly Ubuntu Server, MicroCloud, and enterprise support offerings. Canonical sought to unify its container story under corporate governance to streamline enterprise packaging, commercial SLA delivery, and product roadmaps.<br /> <br /> However, the friction intensified a few months later when Canonical relicensed the entire LXD codebase from the permissive Apache 2.0 license to the Copyleft AGPLv3 (Affero General Public License). This licensing shift created substantial hurdles for third-party integrators, cloud providers, and open-source projects that embedded LXD into their platforms without wishing to adopt AGPL restrictions. Furthermore, Canonical restricted access to the public images.linuxcontainers.org image server for LXD clients, effectively cutting non-Incus users off from community-maintained distribution images. In response, the core maintainers, led by Stéphane Graber, created Incus as a permanent fork, retaining the original Apache 2.0 license and preserving independent governance within the Linux Containers project.<br /> <br /> ==The Future of the Incus Project==<br /> The future of Incus is defined by community-centric innovation and neutral open-source governance. Unlike LXD, which is now tied to Canonical's commercial ecosystem and Ubuntu-centric deployment models, Incus is distribution-agnostic. It receives first-class packaging across major Linux distributions, including Debian, Fedora, Arch Linux, Alpine, and Ubuntu via independent repositories.<br /> <br /> Incus is moving forward with several roadmap priorities. First, it is enhancing support for running OCI container images directly alongside system containers, bridging the gap between application container runtimes and system container managers. Second, Incus is pushing forward with enterprise identity and access management features, integrating fine-grained role-based access controls via OpenFGA. Third, the project is introducing live hot-plugging features for shared storage paths and devices in virtual machines, along with deeper integration for advanced networking stacks like OVN and BGP. Because Incus remains licensed under Apache 2.0, downstream developers and software vendors can freely build commercial and open-source infrastructure services on top of Incus without licensing friction.<br /> <br /> ==Why You Should Migrate from LXD to Incus==<br /> For administrators currently running LXD, staying on Canonical's stack presents growing long-term operational risks and limitations. The primary reason to switch is long-term sustainability and access to the broader open-source ecosystem. Canonical's decision to block LXD clients from accessing the official Linux Containers image repository means LXD users must rely solely on Canonical's image infrastructure or build custom image delivery pipelines. In contrast, Incus natively retains access to the complete library of community-built Linux distribution images.<br /> <br /> Another reason is developer momentum. The original core maintainers and primary community contributors moved their focus entirely to Incus. As a result, new feature development, performance optimization, and bug fixes are happening primarily within the Incus codebase. Additionally, Incus avoids forcing users into Canonical's Snap package ecosystem, allowing operators to run natively packaged binaries from distribution repositories or custom build pipelines, which improves system stability, startup performance, and backup flexibility.<br /> <br /> ==Preparation and Prerequisites==<br /> Before performing a migration, proper preparation is necessary to ensure zero data loss. The migration process is designed as an in-place conversion using an official tool named lxd-to-incus, which inspects existing LXD storage, networks, profiles, and instances, and converts them directly into Incus resources.<br /> <br /> To prepare your system, you should first audit your current LXD setup. Take complete inventory of running containers, virtual machines, storage pools (such as ZFS, Btrfs, or LVM), custom network bridges, and configuration profiles. Ensure that your host operating system is fully updated and that your LXD daemon is running a compatible version. It is important to create off-site backups or storage-level snapshots of all essential container data prior to starting the automated migration script.<br /> <br /> You must also install the Incus daemon packages on your host system before running the migration. When installing Incus, it is important that you do not run the initial setup command (incus admin init), because the automated migration utility expects a fresh, uninitialized Incus installation so that it can populate the database with your existing LXD configurations.<br /> <br /> ==Migration Process with lxd-to-incus==<br /> The migration process is streamlined thanks to the &lt;code&gt;lxd-to-incus&lt;/code&gt; utility provided by the Incus team. The first step in the execution phase is to install the migration package on your system, which is typically distributed alongside Incus tools. Once installed, you execute the &lt;code&gt;lxd-to-incus&lt;/code&gt; command with root privileges.<br /> <br /> When launched, the migration tool performs a thorough dry-run validation check. It connects to both the running LXD daemon and the installed Incus service to compare API versions, inspect database schemas, verify storage drivers, and check network configurations. If any incompatibilities are detected such as unsupported custom profile keys or version mismatches the tool halts before making any destructive changes and provides feedback on what must be resolved.<br /> <br /> Once validation succeeds, the script asks for confirmation to proceed. Upon confirmation, the migration tool systematically stops all active LXD containers and virtual machines to prevent data corruption. It then migrates database records, updates mount paths for storage pools, transfers network bridge definitions, and updates configuration profiles. After data structures are moved, the tool rewrites paths from the old LXD directory structures to the new Incus locations under &lt;code&gt;/var/lib/incus&lt;/code&gt;. Finally, the tool shuts down the LXD daemon service, starts the Incus service, and offers to automatically uninstall or purge the old LXD package from your host system.<br /> <br /> ==Post-Migration Verification and Adapting to the Incus Ecosystem==<br /> Once the migration tool completes its work, you must verify the operational status of your migrated environment. The fundamental shift for command-line interaction is transitioning from the &lt;code&gt;lxc&lt;/code&gt; CLI command to the &lt;code&gt;incus&lt;/code&gt; CLI tool. System administrators should test instance management by querying instance listings, checking storage pool statuses, and verifying network interfaces.<br /> <br /> You should start your migrated instances and execute internal health checks to verify that services, IP address assignments, DNS resolution, and mounted storage volumes are functioning properly. If your host user accounts need administration privileges, make sure to add them to the &lt;code&gt;incus-admin&lt;/code&gt; system group instead of the legacy &lt;code&gt;lxd&lt;/code&gt;group.<br /> <br /> It is also important to update any existing automation scripts, CI/CD pipelines, Ansible playbooks, or Terraform providers that previously referenced LXD REST API endpoints or socket locations. Incus listens on its own dedicated UNIX socket at &lt;code&gt;/var/lib/incus/unix.socket&lt;/code&gt; and uses updated environment variables. Ipdating these automation hooks to point to Incus, your infrastructure management pipeline will be aligned with the active, community-driven future of system containerization.<br /> <br /> The shift from LXD to Incus is an important turning point in the Linux container ecosystem. What began as a corporate restructuring and licensing overhaul by Canonical ultimately catalyzed the creation of a vibrant, independent, and standard-setting open-source project. Incus preserves the vision of flexible, high-performance system containers and lightweight virtual machines under open governance and permissive licensing. With a mature migration path and toolsets available, transitioning from LXD to Incus ensures that your server infrastructure remains secure, community-supported, and future-proof.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_23_2026&diff=4213 2026-07-23T01:02:58Z

<p>Tommy: </p> <hr /> <div>=Migrating from LXD to Incus=<br /> For years, containerization on Linux was dominated by two primary paradigms. On one side stood application container engines like Docker and Podman, designed to package isolated, single-process microservices. On the other side stood system container technologies, which provide lightweight virtual environments that behave, look, and feel like full-blown Linux operating systems without the performance overhead of full hardware virtualization. At the center of this system container realm was LXD. However, significant governance shifts, licensing changes, and strategic corporate decisions have changed that cuased the fork to Incus as the new standard bearer for open-source system containers and lightweight virtual machines. Understanding this evolution, why the ecosystem split, and how to execute a migration is important for sysadmins, DevOps engineers, and infrastructure architects.<br /> <br /> ==Understanding LXD==<br /> To understand the current state of system container management, you must first look at LXD. Originally launched under the umbrella of the Linux Containers project with primary sponsorship from Canonical, LXD was built as a REST API-driven daemon built on top of LXC (Linux Containers). Bare LXC provided low-level primitives for interacting with kernel namespaces, cgroups, and capabilities, LXD brought a polished, user-friendly interface to manage container lifecycles, storage pools, networks, and cluster deployments.<br /> <br /> LXD filled a niche between traditional hypervisors like KVM or VMware and application containers like Docker. It allowed users to run entire Linux distributions complete with init systems like systemd, SSH daemons, package managers, and cron jobs inside isolated kernel containers that booted in seconds and consumed minimal memory. Later versions of LXD even expanded to manage full QEMU-based virtual machines through the exact same unified REST API and command-line interface, giving operators a single tool to manage both light containers and heavy virtual machines.<br /> <br /> ==Enter Incus==<br /> Incus is a fully open-source, community-driven daemon designed to manage system containers and virtual machines. Created in mid-2023 under the Linux Containers project umbrella, Incus is a direct fork of LXD. It retains the underlying architectural strengths that made LXD popular while steering the project back toward community-led development, open governance, and traditional open-source software licensing.<br /> <br /> The project was spearheaded by Aleksa Sarai and longtime LXD lead developer Stéphane Graber, along with other core contributors from the original project. Incus aims to provide a reliable, flexible platform for running containers and virtual machines across diverse deployment environments, ranging from single-node homelabs to multi-node enterprise production clusters. Maintaining familiar operational paradigms, Incus has diverged from LXD by removing legacy tech debt, improving security defaults, introducing native support for OCI container images, and expanding integration with identity providers like OpenFGA and OpenID Connect.<br /> <br /> ==The Rift==<br /> The split between LXD and Incus was not caused by technical disagreements over software architecture, but rather by fundamental shifts in corporate strategy and project governance. In July 2023, Canonical made the sudden corporate decision to take direct control of the LXD project. Prior to this decision, LXD had operated as a community project under the Linux Containers umbrella, even though Canonical was its primary funder and employed most of its core maintainers. Canonical moved the LXD codebase out of the Linux Containers repository, relocated discussion forums to Canonical platforms, and required contributors to sign a Canonical Contributor License Agreement.<br /> <br /> Canonical's strategic rationale stemmed from a desire to integrate LXD into its commercial product portfolio, particularly Ubuntu Server, MicroCloud, and enterprise support offerings. Canonical sought to unify its container story under corporate governance to streamline enterprise packaging, commercial SLA delivery, and product roadmaps.<br /> <br /> However, the friction intensified a few months later when Canonical relicensed the entire LXD codebase from the permissive Apache 2.0 license to the Copyleft AGPLv3 (Affero General Public License). This licensing shift created substantial hurdles for third-party integrators, cloud providers, and open-source projects that embedded LXD into their platforms without wishing to adopt AGPL restrictions. Furthermore, Canonical restricted access to the public images.linuxcontainers.org image server for LXD clients, effectively cutting non-Incus users off from community-maintained distribution images. In response, the core maintainers, led by Stéphane Graber, created Incus as a permanent fork, retaining the original Apache 2.0 license and preserving independent governance within the Linux Containers project.<br /> <br /> ==The Future of the Incus Project==<br /> The future of Incus is defined by community-centric innovation and neutral open-source governance. Unlike LXD, which is now tied to Canonical's commercial ecosystem and Ubuntu-centric deployment models, Incus is distribution-agnostic. It receives first-class packaging across major Linux distributions, including Debian, Fedora, Arch Linux, Alpine, and Ubuntu via independent repositories.<br /> <br /> Incus is moving forward with several roadmap priorities. First, it is enhancing support for running OCI container images directly alongside system containers, bridging the gap between application container runtimes and system container managers. Second, Incus is pushing forward with enterprise identity and access management features, integrating fine-grained role-based access controls via OpenFGA. Third, the project is introducing live hot-plugging features for shared storage paths and devices in virtual machines, along with deeper integration for advanced networking stacks like OVN and BGP. Because Incus remains licensed under Apache 2.0, downstream developers and software vendors can freely build commercial and open-source infrastructure services on top of Incus without licensing friction.<br /> <br /> ==Why You Should Migrate from LXD to Incus==<br /> For administrators currently running LXD, staying on Canonical's stack presents growing long-term operational risks and limitations. The primary reason to switch is long-term sustainability and access to the broader open-source ecosystem. Canonical's decision to block LXD clients from accessing the official Linux Containers image repository means LXD users must rely solely on Canonical's image infrastructure or build custom image delivery pipelines. In contrast, Incus natively retains access to the complete library of community-built Linux distribution images.<br /> <br /> Another reason is developer momentum. The original core maintainers and primary community contributors moved their focus entirely to Incus. As a result, new feature development, performance optimization, and bug fixes are happening primarily within the Incus codebase. Additionally, Incus avoids forcing users into Canonical's Snap package ecosystem, allowing operators to run natively packaged binaries from distribution repositories or custom build pipelines, which improves system stability, startup performance, and backup flexibility.<br /> <br /> ==Preparation and Prerequisites==<br /> Before performing a migration, proper preparation is necessary to ensure zero data loss. The migration process is designed as an in-place conversion using an official tool named lxd-to-incus, which inspects existing LXD storage, networks, profiles, and instances, and converts them directly into Incus resources.<br /> <br /> To prepare your system, you should first audit your current LXD setup. Take complete inventory of running containers, virtual machines, storage pools (such as ZFS, Btrfs, or LVM), custom network bridges, and configuration profiles. Ensure that your host operating system is fully updated and that your LXD daemon is running a compatible version. It is important to create off-site backups or storage-level snapshots of all essential container data prior to starting the automated migration script.<br /> <br /> You must also install the Incus daemon packages on your host system before running the migration. When installing Incus, it is important that you do not run the initial setup command (incus admin init), because the automated migration utility expects a fresh, uninitialized Incus installation so that it can populate the database with your existing LXD configurations.<br /> <br /> ==Migration Process with lxd-to-incus==<br /> The migration process is streamlined thanks to the &lt;code&gt;lxd-to-incus&lt;/code&gt; utility provided by the Incus team. The first step in the execution phase is to install the migration package on your system, which is typically distributed alongside Incus tools. Once installed, you execute the &lt;code&gt;lxd-to-incus&lt;/code&gt; command with root privileges.<br /> <br /> When launched, the migration tool performs a thorough dry-run validation check. It connects to both the running LXD daemon and the installed Incus service to compare API versions, inspect database schemas, verify storage drivers, and check network configurations. If any incompatibilities are detected such as unsupported custom profile keys or version mismatches the tool halts before making any destructive changes and provides feedback on what must be resolved.<br /> <br /> Once validation succeeds, the script asks for confirmation to proceed. Upon confirmation, the migration tool systematically stops all active LXD containers and virtual machines to prevent data corruption. It then migrates database records, updates mount paths for storage pools, transfers network bridge definitions, and updates configuration profiles. After data structures are moved, the tool rewrites paths from the old LXD directory structures to the new Incus locations under &lt;code&gt;/var/lib/incus&lt;/code&gt;. Finally, the tool shuts down the LXD daemon service, starts the Incus service, and offers to automatically uninstall or purge the old LXD package from your host system.<br /> <br /> ==Post-Migration Verification and Adapting to the Incus Ecosystem==<br /> Once the migration tool completes its work, you must verify the operational status of your migrated environment. The fundamental shift for command-line interaction is transitioning from the &lt;code&gt;lxc&lt;/code&gt; CLI command to the &lt;code&gt;incus&lt;/code&gt; CLI tool. System administrators should test instance management by querying instance listings, checking storage pool statuses, and verifying network interfaces.<br /> <br /> You should start your migrated instances and execute internal health checks to verify that services, IP address assignments, DNS resolution, and mounted storage volumes are functioning properly. If your host user accounts need administration privileges, make sure to add them to the &lt;code&gt;incus-admin&lt;/code&gt; system group instead of the legacy &lt;code&gt;lxd&lt;/code&gt;group.<br /> <br /> It is also important to update any existing automation scripts, CI/CD pipelines, Ansible playbooks, or Terraform providers that previously referenced LXD REST API endpoints or socket locations. Incus listens on its own dedicated UNIX socket at &lt;code&gt;/var/lib/incus/unix.socket&lt;/code&gt; and uses updated environment variables. Ipdating these automation hooks to point to Incus, your infrastructure management pipeline will be aligned with the active, community-driven future of system containerization.<br /> <br /> The shift from LXD to Incus is an important turning point in the Linux container ecosystem. What began as a corporate restructuring and licensing overhaul by Canonical ultimately catalyzed the creation of a vibrant, independent, and standard-setting open-source project. Incus preserves the vision of flexible, high-performance system containers and lightweight virtual machines under open governance and permissive licensing. With a mature migration path and toolsets available, transitioning from LXD to Incus ensures that your server infrastructure remains secure, community-supported, and future-proof.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_23_2026&diff=4212 2026-07-23T00:59:33Z

<p>Tommy: /* Post-Migration Verification and Adapting to the Incus Ecosystem */</p> <hr /> <div>=Migrating from LXD to Incus=<br /> For years, containerization on Linux was dominated by two primary paradigms. On one side stood application container engines like Docker and Podman, designed to package isolated, single-process microservices. On the other side stood system container technologies, which provide lightweight virtual environments that behave, look, and feel like full-blown Linux operating systems without the performance overhead of full hardware virtualization. At the center of this system container realm was LXD. However, significant governance shifts, licensing changes, and strategic corporate decisions have changed that cuased the fork to Incus as the new standard bearer for open-source system containers and lightweight virtual machines. Understanding this evolution, why the ecosystem split, and how to execute a migration is important for sysadmins, DevOps engineers, and infrastructure architects.<br /> <br /> ==Understanding LXD==<br /> To understand the current state of system container management, you must first look at LXD. Originally launched under the umbrella of the Linux Containers project with primary sponsorship from Canonical, LXD was built as a REST API-driven daemon built on top of LXC (Linux Containers). Bare LXC provided low-level primitives for interacting with kernel namespaces, cgroups, and capabilities, LXD brought a polished, user-friendly interface to manage container lifecycles, storage pools, networks, and cluster deployments.<br /> <br /> LXD filled a niche between traditional hypervisors like KVM or VMware and application containers like Docker. It allowed users to run entire Linux distributions complete with init systems like systemd, SSH daemons, package managers, and cron jobs inside isolated kernel containers that booted in seconds and consumed minimal memory. Later versions of LXD even expanded to manage full QEMU-based virtual machines through the exact same unified REST API and command-line interface, giving operators a single tool to manage both light containers and heavy virtual machines.<br /> <br /> ==Enter Incus==<br /> Incus is a fully open-source, community-driven daemon designed to manage system containers and virtual machines. Created in mid-2023 under the Linux Containers project umbrella, Incus is a direct fork of LXD. It retains the underlying architectural strengths that made LXD popular while steering the project back toward community-led development, open governance, and traditional open-source software licensing.<br /> <br /> The project was spearheaded by Aleksa Sarai and longtime LXD lead developer Stéphane Graber, along with other core contributors from the original project. Incus aims to provide a reliable, flexible platform for running containers and virtual machines across diverse deployment environments, ranging from single-node homelabs to multi-node enterprise production clusters. Maintaining familiar operational paradigms, Incus has diverged from LXD by removing legacy tech debt, improving security defaults, introducing native support for OCI container images, and expanding integration with identity providers like OpenFGA and OpenID Connect.<br /> <br /> ==The Rift==<br /> The split between LXD and Incus was not caused by technical disagreements over software architecture, but rather by fundamental shifts in corporate strategy and project governance. In July 2023, Canonical made the sudden corporate decision to take direct control of the LXD project. Prior to this decision, LXD had operated as a community project under the Linux Containers umbrella, even though Canonical was its primary funder and employed most of its core maintainers. Canonical moved the LXD codebase out of the Linux Containers repository, relocated discussion forums to Canonical platforms, and required contributors to sign a Canonical Contributor License Agreement.<br /> <br /> Canonical's strategic rationale stemmed from a desire to integrate LXD into its commercial product portfolio, particularly Ubuntu Server, MicroCloud, and enterprise support offerings. Canonical sought to unify its container story under corporate governance to streamline enterprise packaging, commercial SLA delivery, and product roadmaps.<br /> <br /> However, the friction intensified a few months later when Canonical relicensed the entire LXD codebase from the permissive Apache 2.0 license to the Copyleft AGPLv3 (Affero General Public License). This licensing shift created substantial hurdles for third-party integrators, cloud providers, and open-source projects that embedded LXD into their platforms without wishing to adopt AGPL restrictions. Furthermore, Canonical restricted access to the public images.linuxcontainers.org image server for LXD clients, effectively cutting non-Incus users off from community-maintained distribution images. In response, the core maintainers, led by Stéphane Graber, created Incus as a permanent fork, retaining the original Apache 2.0 license and preserving independent governance within the Linux Containers project.<br /> <br /> ==The Future of the Incus Project==<br /> The future of Incus is defined by community-centric innovation and neutral open-source governance. Unlike LXD, which is now tied to Canonical's commercial ecosystem and Ubuntu-centric deployment models, Incus is distribution-agnostic. It receives first-class packaging across major Linux distributions, including Debian, Fedora, Arch Linux, Alpine, and Ubuntu via independent repositories.<br /> <br /> Incus is moving forward with several roadmap priorities. First, it is enhancing support for running OCI container images directly alongside system containers, bridging the gap between application container runtimes and system container managers. Second, Incus is pushing forward with enterprise identity and access management features, integrating fine-grained role-based access controls via OpenFGA. Third, the project is introducing live hot-plugging features for shared storage paths and devices in virtual machines, along with deeper integration for advanced networking stacks like OVN and BGP. Because Incus remains licensed under Apache 2.0, downstream developers and software vendors can freely build commercial and open-source infrastructure services on top of Incus without licensing friction.<br /> <br /> ==Why You Should Migrate from LXD to Incus==<br /> For administrators currently running LXD, staying on Canonical's stack presents growing long-term operational risks and limitations. The primary reason to switch is long-term sustainability and access to the broader open-source ecosystem. Canonical's decision to block LXD clients from accessing the official Linux Containers image repository means LXD users must rely solely on Canonical's image infrastructure or build custom image delivery pipelines. In contrast, Incus natively retains access to the complete library of community-built Linux distribution images.<br /> <br /> Another reason is developer momentum. The original core maintainers and primary community contributors moved their focus entirely to Incus. As a result, new feature development, performance optimization, and bug fixes are happening primarily within the Incus codebase. Additionally, Incus avoids forcing users into Canonical's Snap package ecosystem, allowing operators to run natively packaged binaries from distribution repositories or custom build pipelines, which improves system stability, startup performance, and backup flexibility.<br /> <br /> ==Preparation and Prerequisites==<br /> Before performing a migration, proper preparation is necessary to ensure zero data loss. The migration process is designed as an in-place conversion using an official tool named lxd-to-incus, which inspects existing LXD storage, networks, profiles, and instances, and converts them directly into Incus resources.<br /> <br /> To prepare your system, you should first audit your current LXD setup. Take complete inventory of running containers, virtual machines, storage pools (such as ZFS, Btrfs, or LVM), custom network bridges, and configuration profiles. Ensure that your host operating system is fully updated and that your LXD daemon is running a compatible version. It is important to create off-site backups or storage-level snapshots of all essential container data prior to starting the automated migration script.<br /> <br /> You must also install the Incus daemon packages on your host system before running the migration. When installing Incus, it is important that you do not run the initial setup command (incus admin init), because the automated migration utility expects a fresh, uninitialized Incus installation so that it can populate the database with your existing LXD configurations.<br /> <br /> ==Migration Process with lxd-to-incus==<br /> The migration process is streamlined thanks to the lxd-to-incus utility provided by the Incus team. The first step in the execution phase is to install the migration package on your system, which is typically distributed alongside Incus tools. Once installed, you execute the lxd-to-incus command with root privileges.<br /> <br /> When launched, the migration tool performs a thorough dry-run validation check. It connects to both the running LXD daemon and the installed Incus service to compare API versions, inspect database schemas, verify storage drivers, and check network configurations. If any incompatibilities are detected—such as unsupported custom profile keys or version mismatches the tool halts before making any destructive changes and provides feedback on what must be resolved.<br /> <br /> Once validation succeeds, the script asks for confirmation to proceed. Upon confirmation, the migration tool systematically stops all active LXD containers and virtual machines to prevent data corruption. It then migrates database records, updates mount paths for storage pools, transfers network bridge definitions, and updates configuration profiles. After data structures are moved, the tool rewrites paths from the old LXD directory structures to the new Incus locations under /var/lib/incus. Finally, the tool shuts down the LXD daemon service, starts the Incus service, and offers to automatically uninstall or purge the old LXD package from your host system.<br /> <br /> ==Post-Migration Verification and Adapting to the Incus Ecosystem==<br /> Once the migration tool completes its work, you must verify the operational status of your migrated environment. The fundamental shift for command-line interaction is transitioning from the lxc CLI command to the incus CLI tool. System administrators should test instance management by querying instance listings, checking storage pool statuses, and verifying network interfaces.<br /> <br /> You should start your migrated instances and execute internal health checks to verify that services, IP address assignments, DNS resolution, and mounted storage volumes are functioning properly. If your host user accounts need administration privileges, make sure to add them to the incus-admin system group instead of the legacy &lt;code&gt;lxd&lt;/code&gt;group.<br /> <br /> It is also important to update any existing automation scripts, CI/CD pipelines, Ansible playbooks, or Terraform providers that previously referenced LXD REST API endpoints or socket locations. Incus listens on its own dedicated UNIX socket at /var/lib/incus/unix.socket and uses updated environment variables. Ipdating these automation hooks to point to Incus, your infrastructure management pipeline will be aligned with the active, community-driven future of system containerization.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_23_2026&diff=4211 2026-07-23T00:57:54Z

<p>Tommy: /* Post-Migration Verification and Adapting to the Incus Ecosystem */</p> <hr /> <div>=Migrating from LXD to Incus=<br /> For years, containerization on Linux was dominated by two primary paradigms. On one side stood application container engines like Docker and Podman, designed to package isolated, single-process microservices. On the other side stood system container technologies, which provide lightweight virtual environments that behave, look, and feel like full-blown Linux operating systems without the performance overhead of full hardware virtualization. At the center of this system container realm was LXD. However, significant governance shifts, licensing changes, and strategic corporate decisions have changed that cuased the fork to Incus as the new standard bearer for open-source system containers and lightweight virtual machines. Understanding this evolution, why the ecosystem split, and how to execute a migration is important for sysadmins, DevOps engineers, and infrastructure architects.<br /> <br /> ==Understanding LXD==<br /> To understand the current state of system container management, you must first look at LXD. Originally launched under the umbrella of the Linux Containers project with primary sponsorship from Canonical, LXD was built as a REST API-driven daemon built on top of LXC (Linux Containers). Bare LXC provided low-level primitives for interacting with kernel namespaces, cgroups, and capabilities, LXD brought a polished, user-friendly interface to manage container lifecycles, storage pools, networks, and cluster deployments.<br /> <br /> LXD filled a niche between traditional hypervisors like KVM or VMware and application containers like Docker. It allowed users to run entire Linux distributions complete with init systems like systemd, SSH daemons, package managers, and cron jobs inside isolated kernel containers that booted in seconds and consumed minimal memory. Later versions of LXD even expanded to manage full QEMU-based virtual machines through the exact same unified REST API and command-line interface, giving operators a single tool to manage both light containers and heavy virtual machines.<br /> <br /> ==Enter Incus==<br /> Incus is a fully open-source, community-driven daemon designed to manage system containers and virtual machines. Created in mid-2023 under the Linux Containers project umbrella, Incus is a direct fork of LXD. It retains the underlying architectural strengths that made LXD popular while steering the project back toward community-led development, open governance, and traditional open-source software licensing.<br /> <br /> The project was spearheaded by Aleksa Sarai and longtime LXD lead developer Stéphane Graber, along with other core contributors from the original project. Incus aims to provide a reliable, flexible platform for running containers and virtual machines across diverse deployment environments, ranging from single-node homelabs to multi-node enterprise production clusters. Maintaining familiar operational paradigms, Incus has diverged from LXD by removing legacy tech debt, improving security defaults, introducing native support for OCI container images, and expanding integration with identity providers like OpenFGA and OpenID Connect.<br /> <br /> ==The Rift==<br /> The split between LXD and Incus was not caused by technical disagreements over software architecture, but rather by fundamental shifts in corporate strategy and project governance. In July 2023, Canonical made the sudden corporate decision to take direct control of the LXD project. Prior to this decision, LXD had operated as a community project under the Linux Containers umbrella, even though Canonical was its primary funder and employed most of its core maintainers. Canonical moved the LXD codebase out of the Linux Containers repository, relocated discussion forums to Canonical platforms, and required contributors to sign a Canonical Contributor License Agreement.<br /> <br /> Canonical's strategic rationale stemmed from a desire to integrate LXD into its commercial product portfolio, particularly Ubuntu Server, MicroCloud, and enterprise support offerings. Canonical sought to unify its container story under corporate governance to streamline enterprise packaging, commercial SLA delivery, and product roadmaps.<br /> <br /> However, the friction intensified a few months later when Canonical relicensed the entire LXD codebase from the permissive Apache 2.0 license to the Copyleft AGPLv3 (Affero General Public License). This licensing shift created substantial hurdles for third-party integrators, cloud providers, and open-source projects that embedded LXD into their platforms without wishing to adopt AGPL restrictions. Furthermore, Canonical restricted access to the public images.linuxcontainers.org image server for LXD clients, effectively cutting non-Incus users off from community-maintained distribution images. In response, the core maintainers, led by Stéphane Graber, created Incus as a permanent fork, retaining the original Apache 2.0 license and preserving independent governance within the Linux Containers project.<br /> <br /> ==The Future of the Incus Project==<br /> The future of Incus is defined by community-centric innovation and neutral open-source governance. Unlike LXD, which is now tied to Canonical's commercial ecosystem and Ubuntu-centric deployment models, Incus is distribution-agnostic. It receives first-class packaging across major Linux distributions, including Debian, Fedora, Arch Linux, Alpine, and Ubuntu via independent repositories.<br /> <br /> Incus is moving forward with several roadmap priorities. First, it is enhancing support for running OCI container images directly alongside system containers, bridging the gap between application container runtimes and system container managers. Second, Incus is pushing forward with enterprise identity and access management features, integrating fine-grained role-based access controls via OpenFGA. Third, the project is introducing live hot-plugging features for shared storage paths and devices in virtual machines, along with deeper integration for advanced networking stacks like OVN and BGP. Because Incus remains licensed under Apache 2.0, downstream developers and software vendors can freely build commercial and open-source infrastructure services on top of Incus without licensing friction.<br /> <br /> ==Why You Should Migrate from LXD to Incus==<br /> For administrators currently running LXD, staying on Canonical's stack presents growing long-term operational risks and limitations. The primary reason to switch is long-term sustainability and access to the broader open-source ecosystem. Canonical's decision to block LXD clients from accessing the official Linux Containers image repository means LXD users must rely solely on Canonical's image infrastructure or build custom image delivery pipelines. In contrast, Incus natively retains access to the complete library of community-built Linux distribution images.<br /> <br /> Another reason is developer momentum. The original core maintainers and primary community contributors moved their focus entirely to Incus. As a result, new feature development, performance optimization, and bug fixes are happening primarily within the Incus codebase. Additionally, Incus avoids forcing users into Canonical's Snap package ecosystem, allowing operators to run natively packaged binaries from distribution repositories or custom build pipelines, which improves system stability, startup performance, and backup flexibility.<br /> <br /> ==Preparation and Prerequisites==<br /> Before performing a migration, proper preparation is necessary to ensure zero data loss. The migration process is designed as an in-place conversion using an official tool named lxd-to-incus, which inspects existing LXD storage, networks, profiles, and instances, and converts them directly into Incus resources.<br /> <br /> To prepare your system, you should first audit your current LXD setup. Take complete inventory of running containers, virtual machines, storage pools (such as ZFS, Btrfs, or LVM), custom network bridges, and configuration profiles. Ensure that your host operating system is fully updated and that your LXD daemon is running a compatible version. It is important to create off-site backups or storage-level snapshots of all essential container data prior to starting the automated migration script.<br /> <br /> You must also install the Incus daemon packages on your host system before running the migration. When installing Incus, it is important that you do not run the initial setup command (incus admin init), because the automated migration utility expects a fresh, uninitialized Incus installation so that it can populate the database with your existing LXD configurations.<br /> <br /> ==Migration Process with lxd-to-incus==<br /> The migration process is streamlined thanks to the lxd-to-incus utility provided by the Incus team. The first step in the execution phase is to install the migration package on your system, which is typically distributed alongside Incus tools. Once installed, you execute the lxd-to-incus command with root privileges.<br /> <br /> When launched, the migration tool performs a thorough dry-run validation check. It connects to both the running LXD daemon and the installed Incus service to compare API versions, inspect database schemas, verify storage drivers, and check network configurations. If any incompatibilities are detected—such as unsupported custom profile keys or version mismatches the tool halts before making any destructive changes and provides feedback on what must be resolved.<br /> <br /> Once validation succeeds, the script asks for confirmation to proceed. Upon confirmation, the migration tool systematically stops all active LXD containers and virtual machines to prevent data corruption. It then migrates database records, updates mount paths for storage pools, transfers network bridge definitions, and updates configuration profiles. After data structures are moved, the tool rewrites paths from the old LXD directory structures to the new Incus locations under /var/lib/incus. Finally, the tool shuts down the LXD daemon service, starts the Incus service, and offers to automatically uninstall or purge the old LXD package from your host system.<br /> <br /> ==Post-Migration Verification and Adapting to the Incus Ecosystem==<br /> Once the migration tool completes its work, you must verify the operational status of your migrated environment. The fundamental shift for command-line interaction is transitioning from the lxc CLI command to the incus CLI tool. System administrators should test instance management by querying instance listings, checking storage pool statuses, and verifying network interfaces.<br /> <br /> You should start your migrated instances and execute internal health checks to verify that services, IP address assignments, DNS resolution, and mounted storage volumes are functioning properly. If your host user accounts need administration privileges, make sure to add them to the incus-admin system group instead of the legacy {{lxd}}group.<br /> <br /> It is also important to update any existing automation scripts, CI/CD pipelines, Ansible playbooks, or Terraform providers that previously referenced LXD REST API endpoints or socket locations. Incus listens on its own dedicated UNIX socket at /var/lib/incus/unix.socket and uses updated environment variables. Ipdating these automation hooks to point to Incus, your infrastructure management pipeline will be aligned with the active, community-driven future of system containerization.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_23_2026&diff=4210 2026-07-23T00:56:13Z

<p>Tommy: Created page with &quot;=Migrating from LXD to Incus= For years, containerization on Linux was dominated by two primary paradigms. On one side stood application container engines like Docker and Podman, designed to package isolated, single-process microservices. On the other side stood system container technologies, which provide lightweight virtual environments that behave, look, and feel like full-blown Linux operating systems without the performance overhead of full hardware virtualization....&quot;</p> <hr /> <div>=Migrating from LXD to Incus=<br /> For years, containerization on Linux was dominated by two primary paradigms. On one side stood application container engines like Docker and Podman, designed to package isolated, single-process microservices. On the other side stood system container technologies, which provide lightweight virtual environments that behave, look, and feel like full-blown Linux operating systems without the performance overhead of full hardware virtualization. At the center of this system container realm was LXD. However, significant governance shifts, licensing changes, and strategic corporate decisions have changed that cuased the fork to Incus as the new standard bearer for open-source system containers and lightweight virtual machines. Understanding this evolution, why the ecosystem split, and how to execute a migration is important for sysadmins, DevOps engineers, and infrastructure architects.<br /> <br /> ==Understanding LXD==<br /> To understand the current state of system container management, you must first look at LXD. Originally launched under the umbrella of the Linux Containers project with primary sponsorship from Canonical, LXD was built as a REST API-driven daemon built on top of LXC (Linux Containers). Bare LXC provided low-level primitives for interacting with kernel namespaces, cgroups, and capabilities, LXD brought a polished, user-friendly interface to manage container lifecycles, storage pools, networks, and cluster deployments.<br /> <br /> LXD filled a niche between traditional hypervisors like KVM or VMware and application containers like Docker. It allowed users to run entire Linux distributions complete with init systems like systemd, SSH daemons, package managers, and cron jobs inside isolated kernel containers that booted in seconds and consumed minimal memory. Later versions of LXD even expanded to manage full QEMU-based virtual machines through the exact same unified REST API and command-line interface, giving operators a single tool to manage both light containers and heavy virtual machines.<br /> <br /> ==Enter Incus==<br /> Incus is a fully open-source, community-driven daemon designed to manage system containers and virtual machines. Created in mid-2023 under the Linux Containers project umbrella, Incus is a direct fork of LXD. It retains the underlying architectural strengths that made LXD popular while steering the project back toward community-led development, open governance, and traditional open-source software licensing.<br /> <br /> The project was spearheaded by Aleksa Sarai and longtime LXD lead developer Stéphane Graber, along with other core contributors from the original project. Incus aims to provide a reliable, flexible platform for running containers and virtual machines across diverse deployment environments, ranging from single-node homelabs to multi-node enterprise production clusters. Maintaining familiar operational paradigms, Incus has diverged from LXD by removing legacy tech debt, improving security defaults, introducing native support for OCI container images, and expanding integration with identity providers like OpenFGA and OpenID Connect.<br /> <br /> ==The Rift==<br /> The split between LXD and Incus was not caused by technical disagreements over software architecture, but rather by fundamental shifts in corporate strategy and project governance. In July 2023, Canonical made the sudden corporate decision to take direct control of the LXD project. Prior to this decision, LXD had operated as a community project under the Linux Containers umbrella, even though Canonical was its primary funder and employed most of its core maintainers. Canonical moved the LXD codebase out of the Linux Containers repository, relocated discussion forums to Canonical platforms, and required contributors to sign a Canonical Contributor License Agreement.<br /> <br /> Canonical's strategic rationale stemmed from a desire to integrate LXD into its commercial product portfolio, particularly Ubuntu Server, MicroCloud, and enterprise support offerings. Canonical sought to unify its container story under corporate governance to streamline enterprise packaging, commercial SLA delivery, and product roadmaps.<br /> <br /> However, the friction intensified a few months later when Canonical relicensed the entire LXD codebase from the permissive Apache 2.0 license to the Copyleft AGPLv3 (Affero General Public License). This licensing shift created substantial hurdles for third-party integrators, cloud providers, and open-source projects that embedded LXD into their platforms without wishing to adopt AGPL restrictions. Furthermore, Canonical restricted access to the public images.linuxcontainers.org image server for LXD clients, effectively cutting non-Incus users off from community-maintained distribution images. In response, the core maintainers, led by Stéphane Graber, created Incus as a permanent fork, retaining the original Apache 2.0 license and preserving independent governance within the Linux Containers project.<br /> <br /> ==The Future of the Incus Project==<br /> The future of Incus is defined by community-centric innovation and neutral open-source governance. Unlike LXD, which is now tied to Canonical's commercial ecosystem and Ubuntu-centric deployment models, Incus is distribution-agnostic. It receives first-class packaging across major Linux distributions, including Debian, Fedora, Arch Linux, Alpine, and Ubuntu via independent repositories.<br /> <br /> Incus is moving forward with several roadmap priorities. First, it is enhancing support for running OCI container images directly alongside system containers, bridging the gap between application container runtimes and system container managers. Second, Incus is pushing forward with enterprise identity and access management features, integrating fine-grained role-based access controls via OpenFGA. Third, the project is introducing live hot-plugging features for shared storage paths and devices in virtual machines, along with deeper integration for advanced networking stacks like OVN and BGP. Because Incus remains licensed under Apache 2.0, downstream developers and software vendors can freely build commercial and open-source infrastructure services on top of Incus without licensing friction.<br /> <br /> ==Why You Should Migrate from LXD to Incus==<br /> For administrators currently running LXD, staying on Canonical's stack presents growing long-term operational risks and limitations. The primary reason to switch is long-term sustainability and access to the broader open-source ecosystem. Canonical's decision to block LXD clients from accessing the official Linux Containers image repository means LXD users must rely solely on Canonical's image infrastructure or build custom image delivery pipelines. In contrast, Incus natively retains access to the complete library of community-built Linux distribution images.<br /> <br /> Another reason is developer momentum. The original core maintainers and primary community contributors moved their focus entirely to Incus. As a result, new feature development, performance optimization, and bug fixes are happening primarily within the Incus codebase. Additionally, Incus avoids forcing users into Canonical's Snap package ecosystem, allowing operators to run natively packaged binaries from distribution repositories or custom build pipelines, which improves system stability, startup performance, and backup flexibility.<br /> <br /> ==Preparation and Prerequisites==<br /> Before performing a migration, proper preparation is necessary to ensure zero data loss. The migration process is designed as an in-place conversion using an official tool named lxd-to-incus, which inspects existing LXD storage, networks, profiles, and instances, and converts them directly into Incus resources.<br /> <br /> To prepare your system, you should first audit your current LXD setup. Take complete inventory of running containers, virtual machines, storage pools (such as ZFS, Btrfs, or LVM), custom network bridges, and configuration profiles. Ensure that your host operating system is fully updated and that your LXD daemon is running a compatible version. It is important to create off-site backups or storage-level snapshots of all essential container data prior to starting the automated migration script.<br /> <br /> You must also install the Incus daemon packages on your host system before running the migration. When installing Incus, it is important that you do not run the initial setup command (incus admin init), because the automated migration utility expects a fresh, uninitialized Incus installation so that it can populate the database with your existing LXD configurations.<br /> <br /> ==Migration Process with lxd-to-incus==<br /> The migration process is streamlined thanks to the lxd-to-incus utility provided by the Incus team. The first step in the execution phase is to install the migration package on your system, which is typically distributed alongside Incus tools. Once installed, you execute the lxd-to-incus command with root privileges.<br /> <br /> When launched, the migration tool performs a thorough dry-run validation check. It connects to both the running LXD daemon and the installed Incus service to compare API versions, inspect database schemas, verify storage drivers, and check network configurations. If any incompatibilities are detected—such as unsupported custom profile keys or version mismatches the tool halts before making any destructive changes and provides feedback on what must be resolved.<br /> <br /> Once validation succeeds, the script asks for confirmation to proceed. Upon confirmation, the migration tool systematically stops all active LXD containers and virtual machines to prevent data corruption. It then migrates database records, updates mount paths for storage pools, transfers network bridge definitions, and updates configuration profiles. After data structures are moved, the tool rewrites paths from the old LXD directory structures to the new Incus locations under /var/lib/incus. Finally, the tool shuts down the LXD daemon service, starts the Incus service, and offers to automatically uninstall or purge the old LXD package from your host system.<br /> <br /> ==Post-Migration Verification and Adapting to the Incus Ecosystem==<br /> Once the migration tool completes its work, you must verify the operational status of your migrated environment. The fundamental shift for command-line interaction is transitioning from the lxc CLI command to the incus CLI tool. System administrators should test instance management by querying instance listings, checking storage pool statuses, and verifying network interfaces.<br /> <br /> You should start your migrated instances and execute internal health checks to verify that services, IP address assignments, DNS resolution, and mounted storage volumes are functioning properly. If your host user accounts need administration privileges, make sure to add them to the incus-admin system group instead of the legacy ```lxd``` group.<br /> <br /> It is also important to update any existing automation scripts, CI/CD pipelines, Ansible playbooks, or Terraform providers that previously referenced LXD REST API endpoints or socket locations. Incus listens on its own dedicated UNIX socket at /var/lib/incus/unix.socket and uses updated environment variables. Ipdating these automation hooks to point to Incus, your infrastructure management pipeline will be aligned with the active, community-driven future of system containerization.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4209 2026-07-23T00:39:30Z

<p>Tommy: /* English */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> *[[Daily_Post_July_23_2026|Daily Post July 23 2026 - Migrating from LXD to Incus]]<br /> <br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_22_2026JP&diff=4208 2026-07-22T01:45:05Z

<p>Tommy: Created page with &quot;{{#seo: |title=Proxmox VEで実現するオープンソースの高可用性（HA）の仕組みと構築ガイド |description=Proxmox VEにおける高可用性（HA）とクラスタリングの仕組みを徹底解説。Corosync、クォーラム維持、スプリットブレイン回避、Ceph・共有ストレージ戦略、no-subscriptionリポジトリの運用まで実践的に紹介。 |keywords=Proxmox VE, 高可用性, HA, クラスタリング, Corosync, ク...&quot;</p> <hr /> <div>{{#seo:<br /> |title=Proxmox VEで実現するオープンソースの高可用性（HA）の仕組みと構築ガイド<br /> |description=Proxmox VEにおける高可用性（HA）とクラスタリングの仕組みを徹底解説。Corosync、クォーラム維持、スプリットブレイン回避、Ceph・共有ストレージ戦略、no-subscriptionリポジトリの運用まで実践的に紹介。<br /> |keywords=Proxmox VE, 高可用性, HA, クラスタリング, Corosync, クォーラム, QDevice, Ceph, HCI, スプリットブレイン, ライブマイグレーション, オープンソース, 仮想化<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> |type=article<br /> |canonical=https://mintarc.com/minthome/index.php?title=Proxmox_HA_Architecture_JP<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Proxmoxで実現するオープンソースの高可用性（HA）の仕組み =<br /> 従来のプロプライエタリ（有償専有）なハイパーバイザーは、クラスタリング、ライブマイグレーション、自動フェイルオーバーといった高度な機能を、コア単位やソケット単位の高額なエンタープライズライセンスの壁で制限してきました。ライセンスモデルが変容し運用コストが上昇し続ける中、IT管理者の目はオープンソースの仮想化ソリューションへと向けられています。Proxmox Virtual Environment（Proxmox VE）は、高額なソフトウェアライセンスを必要とせず、エンタープライズクラスの高可用性（HA）を提供します。<br /> <br /> 一部の機能が有料課金の裏にロックされている従来のソフトウェアモデルとは異なり、Proxmox VEはすべてのクラスタリング機能と高可用性機能を標準で搭載しています。ソフトウェアはGPLv3の下で公開されており、有償サポートサブスクリプションの有無にかかわらず、すべてのインストールで全く同じ基盤コードベースが動作します。コアエンジンには、マルチノードクラスタリング、仮想マシンのライブマイグレーション、自動クラスター復帰の完全なサポートが含まれています。これにより、組織はソフトウェアのライセンスキーではなく、物理インフラやネットワークの冗長性に資本を再配分し、汎用ハードウェアを用いて回復力と可用性の高いインフラを構築できます。<br /> <br /> ==Proxmox VEクラスタリングのアーキテクチャ==<br /> Proxmox VEにおける高可用性クラスターの構築は、複数の物理ノードを1つの管理ユニットに統合することから始まります。内部では、低遅延のノード間通信とメンバーシップ管理を行うクラスターエンジンであるCorosyncが動作しています。Corosyncはクラスターメンバー間で絶え間なくハートビート通信を維持し、ネットワーク内の全ホストが他の全ホストの稼働状況を常に把握できるようにします。<br /> 仮想マシンやコンテナが高可用性（HA）向けに構成されると、Proxmox HA Managerがホストの正常性と共にその状態を監視します。物理ノードでハードウェア障害やネットワーク切断が発生した場合、HA Managerはハートビートの喪失を検知し、フェイルオーバー処理を開始します。障害が発生したホストに割り当てられていた仮想ワークロードは、クラスター内の正常なノード上で自動的に再起動されます。管理オーバーヘッドが分散され、コアのDebianベースシステムに統合されているため、管理者はサードパーティの管理エージェントや外部のコントロールプレーン用アプライアンスを導入することなく、クラスター制御を維持できます。<br /> <br /> ==クォーラムの維持とスプリットブレインの回避==<br /> クラスターベースの高可用性アーキテクチャにおいて必須となる要件が、「クォーラム（定足数）」の維持です。クォーラムとは、クラスターがリソースの状態に関する決定権を持つために必要な、アクティブな投票数の最小値を指します。Proxmox VEでは、通常各ノードが全体の投票プールに対して1票を保持します。正常な過半数を確立し、安全にフェイルオーバーコマンドを実行するには、設定された総投票数の過半数がアクティブであり、かつ合意に達している必要があります。<br /> <br /> クォーラムを維持するクラスター設計は、スプリットブレインと呼ばれる致命的な事態を防ぎます。スプリットブレインとは、ネットワークの分断（パーティション）によってノード間が孤立し、双方が「相手の側がダウンした」と誤認する現象です。クォーラムによる制御がない場合、孤立した両グループが同じ共有ストレージに対して同時に書き込みを試み、回復不能なデータ破損を引き起こす恐れがあります。<br /> <br /> これを回避するため、標準的なProxmox HAクラスターは最低3台の物理ノードで構成する必要があります。3台のフルスケールノードの配置が実務上難しい環境では、メインクラスター外の個々の物理マシンまたは仮想マシン上で動作する軽量の投票提供サービスQDeviceを導入し、中立的なタイブレーカー（勝敗決定者）として機能させることができます。<br /> <br /> ==高可用性を実現するためのストレージ戦略==<br /> 自動ワークロードフェイルオーバーは、生き残ったノードが仮想マシンのディスクファイルにアクセスできなければ意味がありません。そのため、高可用性アーキテクチャの成功は、共有または複製されたストレージ基盤に大きく依存します<br /> <br /> *従来の共有ストレージ: NFSやiSCSIなどのネットワークプロトコルを使用した外部ストレージアレイ、あるいはLVM-thinのような共有ボリュームマネージャーを利用するSANベースのブロックストレージにノードを接続します。全ノードが同一のストレージボリュームに読み書きできるようになる一方、ストレージアレイ自体がダウンした際に単一障害点（SPOF）となるリスクを伴います。<br /> <br /> *Cephによる統合ストレージ (HCI): Proxmox VEは、高額な外部SANハードウェアを購入することなく単一障害点を排除するため、Cephストレージをネイティブに統合しています。Cephは、全物理ノードの内部ディスクを単一の高可用性ストレージプールへと集約する、分散型のソフトウェア定義ストレージ（SDS）です。<br /> <br /> Proxmox VEと共にCephを稼働させると、定義された配置ポリシーに従ってデータが複数のホスト間に自動複製されます。物理ノードが1台故障した場合でも、Cephは残りのレプリカからデータ提供を継続し、ストレージの可用性を途断えさせません。このハイパーコンバージドインフラストラクチャ（HCI）設計により、中小規模の組織でもシンプルかつコスト効率の良い構成で、演算リソースとストレージの冗長性を両立できます。<br /> <br /> ==エンタープライズ・サブスクリプションなしでのリポジトリ管理==<br /> Proxmoxの新規管理者が頻繁に混乱する領域の1つが、パッケージリポジトリの管理とソフトウェア更新です。デフォルトでは、Proxmox VEの新規インストールは「エンタープライズ・パッケージ・リポジトリ」を参照するように設定されています。有料のサブスクリプションキーなしでクラスターを更新しようとすると、認証警告が表示されます。しかし、Proxmoxはすべてのソフトウェア更新、セキュリティパッチ、新機能を収録した、自由にアクセスできるno-subscriptionリポジトリを明示的に提供しています。<br /> <br /> no-subscriptionリポジトリを使用してHAクラスターを運用するには、各ノードのAPTソースを設定し、オープンなソフトウェアチャンネルを参照させる必要があります。no-subscriptionリポジトリのパッケージもリリース前にテストされていますが、エンタープライズチャンネルよりも短いスパンで新しいパッケージが公開されます。<br /> <br /> このブランチで本番クラスターを稼働させる場合、管理者はパッチ適用プロセスを適切に管理し、本番環境へ適用する前にステージング（非本番）環境でアップデートの検証を行うべきです。リポジトリ設定を正しく維持し、計画的にアップグレードを適用することで、ライセンス費用を一切かけることなく、セキュアで最新の安定したクラスター環境を維持できます。<br /> <br /> ==導入とメンテナンスのベストプラクティス==<br /> 高可用性Proxmoxクラスターの導入には、ソフトウェアのインストールを開始する前の綿密な計画が必要です。特にネットワークトポロジーはクラスターの安定性に直結するため、管理者はCorosyncのクラスター通信専用に、独立した物理インターフェースまたはVLAN分割されたネットワークインターフェースを割り当てる必要があります。Corosyncは極めて低い遅延と予測可能なネットワークスループットを要求するため、通信チャンネルをストレージの重いトラフィックやテナントの仮想マシントラフィックと共有すると、ノードタイムアウトの誤検知や意図しないフェイルオーバーを引き起こす原因になります。<br /> <br /> 物理ネットワークとホストのインストールが整えば、ProxmoxのWeb管理インターフェースまたはコマンドラインインターフェース（CLI）を通じて簡単にクラスターを作成できます。セキュアなトークン交換によってノードをクラスターに参加させ、その後、共有ストレージプールとHAリソースグループを設定します。<br /> <br /> カーネル更新に伴うホストの再起動といった日常的なメンテナンスも、ライブマイグレーションによって大幅に簡素化されます。ダウンタイムなしで仮想マシンをアクティブなノード間で移行できるため、サービスの提供に影響を与えることなく、ハードウェアの保守やソフトウェアのパッチ適用をスムーズに進めることが可能です。<br /> <br /> 高可用性仮想化環境の構築に、天文学的なエンタープライズライセンスの予算はもはや必要ありません。Proxmox VEを活用することで、クラスタリング、自動フェイルオーバー、ソフトウェア定義ストレージを標準で提供する完全なオープンソース・ハイパーバイザーを導入できます。Cephを使用した3台の物理サーバー構成であっても、QDeviceと従来の共有ストレージを組み合わせた構成であっても、Proxmoxはアプリケーションを稼働し続けるために必要なあらゆる技術的機能を提供します。適切なネットワーク設計、ストレージ計画、リポジトリ管理を行うことで、ITチームはハードウェアと予算を完全にコントロールしながら、エンタープライズクラスのシステム連続稼働時間を達成することができます。<br /> <br /> 現在ご検討中のインフラ環境において、用意できる物理ノードの台数や、Cephと外部共有ストレージのどちらを想定されているかなど、具体的な構成のイメージはございますか？</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4207 2026-07-22T01:38:37Z

<p>Tommy: /* 日本語の投稿 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> *[[Daily_Post_July_22_2026JP|Proxmoxで実現するオープンソースの高可用性（HA）の仕組み 7/22/2026]]<br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_22_2026&diff=4206 2026-07-22T01:10:44Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Automating VM and CT/LXC Deployments: Cloud-Init and Proxmox Templates<br /> |description= Master rapid infrastructure provisioning on Proxmox VE. Learn how to combine base templates, Cloud-Init, LXC snippets, and Infrastructure as Code for automated virtual machine and container deployment.<br /> |keywords= Proxmox VE, Cloud-Init, VM Templates, LXC Containers, Container Deployment, Infrastructure as Code, Terraform, Ansible, QEMU KVM, Linux Virtualization, Automated Provisioning<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_22_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Infrastructure Automation in Proxmox VE=<br /> Traditional hypervisor management involved manually attaching ISO installers, stepping through setup wizards, configuring disk partitions, and manually setting up network parameters for every single instance. This hands-on approach works for isolated tests, it becomes a bottleneck when scaling services or maintaining multi-node environments. Proxmox Virtual Environment provides a hypervisor platform capable of running both hardware-virtualized QEMU virtual machines and LXC system containers. To use full efficiency of this platform, administrators rely on a combination of base templates and early-boot initialization tools, turning what once took fifteen minutes of manual clicking into a fully automated process that completes in seconds.<br /> <br /> Automating guest provisioning centers around the concept of declarative baseline configurations. Rather than building every virtual machine or container from scratch, you construct a standardized base disk image containing essential OS components, optimize its virtual hardware layout, and freeze it as a reusable template. When a new virtual instance is requested, Proxmox clones this template instantly. But, cloning alone creates an exact replica, including duplicate system hostnames, identical network settings, and shared SSH host keys. The automation requires a post-cloning configuration phase that injects unique identity details into the newly created instance during its very first boot cycle.<br /> <br /> ==Virtual Machines Versus LXC Containers==<br /> Understanding how to automate deployments on Proxmox VE requires recognizing the architectural differences between virtual machines and Linux Containers. Virtual machines rely on QEMU and KVM hardware virtualization, providing complete kernel isolation and allowing administrators to run operating systems like Linux, BSD, or Windows. Because a virtual machine boots its own dedicated kernel, it initializes hardware subsystems, mounts root file systems, and runs standard cloud provisioning agents like Cloud-Init just as a public cloud instance would on AWS or OpenStack. This isolation makes virtual machines ideal for tenant isolation, specialized security workloads, and running non-Linux operating systems.<br /> <br /> On the other hand, LXC system containers share the host Linux kernel while maintaining isolated file systems, process namespaces, and network stacks. This shared kernel architecture allows containers to consume significantly fewer system resources, boot almost instantaneously, and achieve near-native disk and CPU performance. However, because containers do not execute a standard bootloader or virtual BIOS, early-boot configuration works differently. Proxmox handles container setup by directly modifying the container file system from the hypervisor host before the container process starts, injecting network parameters, root passwords, and SSH keys directly into the guest configuration files. Selecting between virtual machines and containers dictates whether your automation strategy relies on guest-side initialization tools or hypervisor-native template orchestration.<br /> <br /> ==Cloud-Init for Virtual Machine Provisioning==<br /> Cloud-Init is the industry standard multi-distribution package for handling early-boot initialization of virtual machine instances. Originally developed for cloud infrastructure, Cloud-Init runs early in the boot sequence to read metadata supplied by the hypervisor and apply local runtime configurations. In Proxmox VE, this metadata is typically passed via a virtual drive containing an ISO image formatted according to the Cloud-Init standard. When the newly cloned virtual machine boots for the first time, its internal Cloud-Init daemon detects this drive, parses the contained user-data and network-data configurations, and dynamically sets up the system environment.<br /> <br /> Building a Cloud-Init template in Proxmox VE starts with downloading an official vendor cloud image rather than a traditional installation ISO. Most major Linux distributions, including Ubuntu, Debian, Rocky Linux, and Fedora, publish lightweight, pre-installed disk images in raw or QCOW2 format specifically designed for Cloud-Init. After importing the disk image into Proxmox storage using the command-line utilities, an administrator attaches a Cloud-Init drive to the virtual hardware configuration. Proxmox exposes an intuitive Cloud-Init management interface where you can specify default usernames, inject SSH public keys, configure static or DHCP networking, and define DNS search domains. Once the virtual machine is converted into a master template, cloning it generates a fresh instance that reads these custom parameters on boot, completely eliminating manual OS installation steps.<br /> <br /> ┌────────────────────────────────────────────────────────┐<br /> │ Proxmox VE Host │<br /> │ │<br /> │ ┌─────────────────┐ qm clone ┌────────────┐ │<br /> │ │ Base CI Template│ ────────────────&gt; │ Cloned VM │ │<br /> │ └────────┬────────┘ └─────┬──────┘ │<br /> │ │ │ │<br /> │ ▼ ▼ │<br /> │ [ Cloud-Init Drive ] ──────────────&gt; [ Auto Boot ] │<br /> │ (User Data / Net) (Injects Keys, │<br /> │ IP &amp; Hostname) │<br /> └────────────────────────────────────────────────────────┘<br /> <br /> ==Containers with LXC Templates and Snippets==<br /> Cloud-Init serves as the primary engine for virtual machines, LXC container deployment relies on appliance templates and Proxmox hooks. Proxmox provides access to a library of official container templates ranging from minimal Alpine and Debian base OS builds to turnkey application stacks. Creating an LXC template involves downloading a base container tarball, launching a instance, installing necessary software dependencies, cleaning up temporary log files and machine identifiers, and finally stopping the container to convert it into a reusable template archive.<br /> <br /> To achieve custom initialization for containers similar to Cloud-Init, Proxmox supports custom hook scripts and snippet files. Snippets allow administrators to store custom Cloud-Init YAML definitions or shell execution scripts in designated storage locations on the hypervisor host. When a container or VM initializes, Proxmox passes these custom snippet configurations directly into the guest environment. This mechanism enables automated package updates, user creation, custom firewall rule injection, and automated registration with central monitoring systems without needing to modify the underlying base container image<br /> <br /> ==Orchestrating Deployments with Infrastructure as Code==<br /> Manually creating clones through the Proxmox Web UI is a great step forward, but full automation requires integrating templates with Infrastructure as Code tools like Terraform, OpenTofu, and Ansible. Terraform and OpenTofu interact directly with the Proxmox REST API using specialized providers. Writing declarative configuration files, you can define complete topology environments comprising dozens of virtual machines and containers, specifying CPU core allocations, memory sizes, network bridge attachments, and Cloud-Init parameters in code. Executing a single command prompts the IaC tool to communicate with Proxmox, clone the specified Cloud-Init templates, apply network settings, and spin up the entire cluster within minutes.<br /> <br /> Once the infrastructure layer is provisioned by Terraform, configuration management utilities like Ansible step in to manage software state. Cloud-Init handles the fundamental bootstrapping phase, such as setting up the network and authorizing SSH keys for an automation user. Ansible then connects to the newly spawned instances over SSH to perform post-deployment tasks, such as applying security patches, configuring web servers, setting up storage mounts, and deploying application containers. Combining Cloud-Init templates with IaC frameworks produces a reliable deployment pipeline where infrastructure is fully version-controlled, easily reproducible, and immune to configuration drift.<br /> <br /> ==Maintenance Strategies for Templates==<br /> Maintaining automated deployment pipelines requires ongoing image lifecycle management. Over time, static base templates become stale as software packages receive security updates and operating system distribution versions evolve. To maintain fast boot times and prevent newly deployed instances from immediately downloading hundreds of megabytes of security patches, templates must be routinely updated. Tools like HashiCorp Packer can automate template creation by regularly downloading official cloud images, booting them in temporary environments, installing updates and guest agents, and outputting fresh Proxmox templates on a scheduled basis.<br /> <br /> Proper security practices must also be maintained throughout template creation. Base images should not contain hardcoded SSH private keys, static machine IDs, or default passwords. Utilizing guest utilities like libguestfs-tools during template building ensures that machine identifiers are wiped, forcing every cloned virtual machine or container to generate its own unique host keys and network identities upon launch. By combining clean baseline images with Cloud-Init parameter injection and declarative orchestration, administrators achieve a resilient hypervisor ecosystem capable of scaling to meet any operational demand.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_21_2026&diff=4205 2026-07-22T01:10:39Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Proxmox VE High Availability and Clustering Without Licensing Costs<br /> |description= Learn how Proxmox VE delivers enterprise-grade High Availability, Corosync clustering, quorum management, and Ceph storage without expensive enterprise software licenses.<br /> |keywords= Proxmox VE, High Availability, Proxmox HA, Proxmox Clustering, Corosync, Ceph Storage, Quorum, Open Source Virtualization, Enterprise Hypervisor, No-Subscription Repository<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_21_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Understanding Proxmox and Open-Source High Availability=<br /> Proprietary hypervisors historically gated clustering, live migration, and automated failover behind expensive per-core or per-socket enterprise licensing tiers. As licensing models evolve and operational costs continue to rise, IT administrators increasingly turn to open-source virtualization solutions. Proxmox Virtual Environment platform gives enterprise-grade high availability without requiring costly software licenses.<br /> <br /> This is different from proprietary software models where features are locked behind paywalls, Proxmox VE includes all clustering and high-availability functionality out of the box. The software is published under the GPLv3, meaning every installation contains the exact same underlying codebase regardless of whether a paid support subscription is attached. The core engine includes full support for multi-node clustering, live virtual machine migration, and automated cluster recovery. Organizations can deploy resilient, available infrastructures using commodity hardware while reallocating capital toward physical infrastructure or network redundancy rather than software license keys.<br /> <br /> ==Architecture of Proxmox VE Clustering==<br /> Building a high-availability cluster in Proxmox VE begins with joining multiple physical nodes into a management unit. Under the hood, Proxmox relies on Corosync, a cluster engine that handles low-latency node communication and membership tracking. Corosync maintains constant heartbeat communication between cluster members, ensuring that every host remains aware of the operational status of every other host in the network.<br /> <br /> When a virtual machine or container is configured for high availability, the Proxmox HA Manager constantly monitors its state alongside host health. If a physical node experiences a hardware failure or network disconnect, the HA Manager detects the loss of heartbeat and initiates failover operations. The virtual workloads assigned to the failed host are automatically restarted on healthy nodes within the cluster. Because the management overhead is distributed and integrated into the core Debian base system, administrators gain cluster control without installing third-party management agents or secondary control plane appliances.<br /> <br /> ==Quorum and Avoiding Split-Brain Scenarios==<br /> A requirement for any cluster-based high availability architecture is maintaining quorum. Quorum represents the minimum number of active votes required for the cluster to make authoritative decisions about resource state. In Proxmox VE, each node typically contributes one vote to the total pool. To establish a healthy majority and safely execute failover commands, more than half of the total configured votes must be active and in agreement.<br /> <br /> Designing a cluster to maintain quorum prevents the catastrophic scenario known as a split-brain state. In a split-brain scenario, a network partition isolates nodes from one another, causing both sides of the network to believe the other has failed. Without quorum enforcement, both isolated groups might attempt to write to the same shared storage simultaneously, leading to unrecoverable data corruption. To avoid this, a standard Proxmox HA cluster should consist of at least three physical nodes. In environments where deploying three full-scale nodes is impractical, administrators can introduce a QDevice, an external lightweight vote-providing service running on a separate physical or virtual machine outside the main cluster, to serve as an impartial tie-breaker.<br /> <br /> ==Storage Strategy for High Availability==<br /> Automatic workload failover is only useful if the surviving nodes have access to the virtual machine disk files. Therefore, a successful high-availability architecture depends heavily on a shared or replicated storage foundation. Traditional deployments connect cluster nodes to external storage arrays using network protocols such as NFS or iSCSI, or SAN-based block storage utilizing shared volume managers like LVM-thin. While this centralized approach ensures all nodes can read and write to the same storage volumes, it introduces a potential single point of failure if the storage array itself goes down.<br /> <br /> To eliminate central storage bottlenecks and single points of failure without purchasing expensive external SAN hardware, Proxmox VE natively integrates Ceph storage. Ceph is a distributed, software-defined storage cluster that aggregates internal disks across all physical nodes into a single, highly available storage pool. When running Ceph alongside Proxmox VE, data is automatically replicated across multiple hosts according to defined placement policies. If a physical node fails, Ceph continues serving data from remaining replicas without interrupting storage availability. This hyperconverged infrastructure design allows small and medium-sized organizations to achieve compute and storage redundancy in a unified, cost-effective deployment.<br /> <br /> ==Managing Software Repositories Without Enterprise Subscriptions==<br /> One area that frequently causes confusion for new Proxmox administrators is package repository management and software updates. By default, a fresh Proxmox VE installation points to the enterprise package repository. When updating a cluster without an active paid subscription key, the system returns authentication warnings. However, Proxmox explicitly provides a freely accessible no-subscription repository containing all software updates, security patches, and new features.<br /> <br /> Operating an HA cluster using the no-subscription repository requires configuring the APT sources on each node to point to the open software channels. While packages in the no-subscription repository undergo testing before release, they are published on a faster cadence than those in the enterprise channel. For production clusters operating on the no-subscription branch, administrators should implement a controlled patching process, validating updates in a non-production environment before applying them to primary infrastructure. By properly maintaining repository configurations and applying upgrades methodically, teams can maintain a secure, updated, and stable cluster environment completely free of licensing charges.<br /> <br /> ==Deployment and Maintenance==<br /> Deploying a high-availability Proxmox cluster requires careful planning prior to initiating software installation. Network topology plays a role in cluster stability; administrators should dedicate separate physical or VLAN-segmented network interfaces exclusively for Corosync cluster communication. Because Corosync requires extremely low latency and predictable network throughput, sharing cluster communication channels with heavy storage traffic or tenant virtual machine traffic can trigger false-positive node timeouts and unintended failover events.<br /> <br /> Once the physical network and host installations are in place, creating the cluster is straightforward through either the Proxmox web management interface or the command line interface. Nodes are joined into the cluster using secure token exchange, after which shared storage pools and HA resource groups can be designated. Routine maintenance, such as host rebooting for kernel updates, is simplified through live migration. Virtual machines can be migrated between active nodes without downtime, allowing hardware maintenance or software patching to proceed smoothly without impacting service delivery.<br /> <br /> ==Enterprise-Grade Reliability==<br /> High availability virtualization no longer requires astronomical enterprise licensing budgets. By leveraging Proxmox VE, organizations gain access to a complete, open-source hypervisor capable of delivering clustering, automated failover, and software-defined storage out of the box. Whether deployed across three physical servers using Ceph or structured around a traditional shared storage backend with a QDevice, Proxmox provides all the technical capabilities required to keep applications online. With proper network design, storage planning, and repository management, IT teams can achieve enterprise-grade uptime while retaining complete control over their hardware and budget.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_22_2026&diff=4204 2026-07-22T01:09:10Z

<p>Tommy: Created page with &quot;=Infrastructure Automation in Proxmox VE= Traditional hypervisor management involved manually attaching ISO installers, stepping through setup wizards, configuring disk partitions, and manually setting up network parameters for every single instance. This hands-on approach works for isolated tests, it becomes a bottleneck when scaling services or maintaining multi-node environments. Proxmox Virtual Environment provides a hypervisor platform capable of running both hardwa...&quot;</p> <hr /> <div>=Infrastructure Automation in Proxmox VE=<br /> Traditional hypervisor management involved manually attaching ISO installers, stepping through setup wizards, configuring disk partitions, and manually setting up network parameters for every single instance. This hands-on approach works for isolated tests, it becomes a bottleneck when scaling services or maintaining multi-node environments. Proxmox Virtual Environment provides a hypervisor platform capable of running both hardware-virtualized QEMU virtual machines and LXC system containers. To use full efficiency of this platform, administrators rely on a combination of base templates and early-boot initialization tools, turning what once took fifteen minutes of manual clicking into a fully automated process that completes in seconds.<br /> <br /> Automating guest provisioning centers around the concept of declarative baseline configurations. Rather than building every virtual machine or container from scratch, you construct a standardized base disk image containing essential OS components, optimize its virtual hardware layout, and freeze it as a reusable template. When a new virtual instance is requested, Proxmox clones this template instantly. But, cloning alone creates an exact replica, including duplicate system hostnames, identical network settings, and shared SSH host keys. The automation requires a post-cloning configuration phase that injects unique identity details into the newly created instance during its very first boot cycle.<br /> <br /> ==Virtual Machines Versus LXC Containers==<br /> Understanding how to automate deployments on Proxmox VE requires recognizing the architectural differences between virtual machines and Linux Containers. Virtual machines rely on QEMU and KVM hardware virtualization, providing complete kernel isolation and allowing administrators to run operating systems like Linux, BSD, or Windows. Because a virtual machine boots its own dedicated kernel, it initializes hardware subsystems, mounts root file systems, and runs standard cloud provisioning agents like Cloud-Init just as a public cloud instance would on AWS or OpenStack. This isolation makes virtual machines ideal for tenant isolation, specialized security workloads, and running non-Linux operating systems.<br /> <br /> On the other hand, LXC system containers share the host Linux kernel while maintaining isolated file systems, process namespaces, and network stacks. This shared kernel architecture allows containers to consume significantly fewer system resources, boot almost instantaneously, and achieve near-native disk and CPU performance. However, because containers do not execute a standard bootloader or virtual BIOS, early-boot configuration works differently. Proxmox handles container setup by directly modifying the container file system from the hypervisor host before the container process starts, injecting network parameters, root passwords, and SSH keys directly into the guest configuration files. Selecting between virtual machines and containers dictates whether your automation strategy relies on guest-side initialization tools or hypervisor-native template orchestration.<br /> <br /> ==Cloud-Init for Virtual Machine Provisioning==<br /> Cloud-Init is the industry standard multi-distribution package for handling early-boot initialization of virtual machine instances. Originally developed for cloud infrastructure, Cloud-Init runs early in the boot sequence to read metadata supplied by the hypervisor and apply local runtime configurations. In Proxmox VE, this metadata is typically passed via a virtual drive containing an ISO image formatted according to the Cloud-Init standard. When the newly cloned virtual machine boots for the first time, its internal Cloud-Init daemon detects this drive, parses the contained user-data and network-data configurations, and dynamically sets up the system environment.<br /> <br /> Building a Cloud-Init template in Proxmox VE starts with downloading an official vendor cloud image rather than a traditional installation ISO. Most major Linux distributions, including Ubuntu, Debian, Rocky Linux, and Fedora, publish lightweight, pre-installed disk images in raw or QCOW2 format specifically designed for Cloud-Init. After importing the disk image into Proxmox storage using the command-line utilities, an administrator attaches a Cloud-Init drive to the virtual hardware configuration. Proxmox exposes an intuitive Cloud-Init management interface where you can specify default usernames, inject SSH public keys, configure static or DHCP networking, and define DNS search domains. Once the virtual machine is converted into a master template, cloning it generates a fresh instance that reads these custom parameters on boot, completely eliminating manual OS installation steps.<br /> <br /> ┌────────────────────────────────────────────────────────┐<br /> │ Proxmox VE Host │<br /> │ │<br /> │ ┌─────────────────┐ qm clone ┌────────────┐ │<br /> │ │ Base CI Template│ ────────────────&gt; │ Cloned VM │ │<br /> │ └────────┬────────┘ └─────┬──────┘ │<br /> │ │ │ │<br /> │ ▼ ▼ │<br /> │ [ Cloud-Init Drive ] ──────────────&gt; [ Auto Boot ] │<br /> │ (User Data / Net) (Injects Keys, │<br /> │ IP &amp; Hostname) │<br /> └────────────────────────────────────────────────────────┘<br /> <br /> ==Containers with LXC Templates and Snippets==<br /> Cloud-Init serves as the primary engine for virtual machines, LXC container deployment relies on appliance templates and Proxmox hooks. Proxmox provides access to a library of official container templates ranging from minimal Alpine and Debian base OS builds to turnkey application stacks. Creating an LXC template involves downloading a base container tarball, launching a instance, installing necessary software dependencies, cleaning up temporary log files and machine identifiers, and finally stopping the container to convert it into a reusable template archive.<br /> <br /> To achieve custom initialization for containers similar to Cloud-Init, Proxmox supports custom hook scripts and snippet files. Snippets allow administrators to store custom Cloud-Init YAML definitions or shell execution scripts in designated storage locations on the hypervisor host. When a container or VM initializes, Proxmox passes these custom snippet configurations directly into the guest environment. This mechanism enables automated package updates, user creation, custom firewall rule injection, and automated registration with central monitoring systems without needing to modify the underlying base container image<br /> <br /> ==Orchestrating Deployments with Infrastructure as Code==<br /> Manually creating clones through the Proxmox Web UI is a great step forward, but full automation requires integrating templates with Infrastructure as Code tools like Terraform, OpenTofu, and Ansible. Terraform and OpenTofu interact directly with the Proxmox REST API using specialized providers. Writing declarative configuration files, you can define complete topology environments comprising dozens of virtual machines and containers, specifying CPU core allocations, memory sizes, network bridge attachments, and Cloud-Init parameters in code. Executing a single command prompts the IaC tool to communicate with Proxmox, clone the specified Cloud-Init templates, apply network settings, and spin up the entire cluster within minutes.<br /> <br /> Once the infrastructure layer is provisioned by Terraform, configuration management utilities like Ansible step in to manage software state. Cloud-Init handles the fundamental bootstrapping phase, such as setting up the network and authorizing SSH keys for an automation user. Ansible then connects to the newly spawned instances over SSH to perform post-deployment tasks, such as applying security patches, configuring web servers, setting up storage mounts, and deploying application containers. Combining Cloud-Init templates with IaC frameworks produces a reliable deployment pipeline where infrastructure is fully version-controlled, easily reproducible, and immune to configuration drift.<br /> <br /> ==Maintenance Strategies for Templates==<br /> Maintaining automated deployment pipelines requires ongoing image lifecycle management. Over time, static base templates become stale as software packages receive security updates and operating system distribution versions evolve. To maintain fast boot times and prevent newly deployed instances from immediately downloading hundreds of megabytes of security patches, templates must be routinely updated. Tools like HashiCorp Packer can automate template creation by regularly downloading official cloud images, booting them in temporary environments, installing updates and guest agents, and outputting fresh Proxmox templates on a scheduled basis.<br /> <br /> Proper security practices must also be maintained throughout template creation. Base images should not contain hardcoded SSH private keys, static machine IDs, or default passwords. Utilizing guest utilities like libguestfs-tools during template building ensures that machine identifiers are wiped, forcing every cloned virtual machine or container to generate its own unique host keys and network identities upon launch. By combining clean baseline images with Cloud-Init parameter injection and declarative orchestration, administrators achieve a resilient hypervisor ecosystem capable of scaling to meet any operational demand.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4203 2026-07-22T00:53:41Z

<p>Tommy: /* July 2026 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> *[[Daily_Post_July_22_2026|Daily Post July 22 2026 - Infrastructure Automation in Proxmox VE]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_21_2026&diff=4202 2026-07-21T01:02:04Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Proxmox VE High Availability and Clustering Without Licensing Costs<br /> |description= Learn how Proxmox VE delivers enterprise-grade High Availability, Corosync clustering, quorum management, and Ceph storage without expensive enterprise software licenses.<br /> |keywords= Proxmox VE, High Availability, Proxmox HA, Proxmox Clustering, Corosync, Ceph Storage, Quorum, Open Source Virtualization, Enterprise Hypervisor, No-Subscription Repository<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_17_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Understanding Proxmox and Open-Source High Availability=<br /> Proprietary hypervisors historically gated clustering, live migration, and automated failover behind expensive per-core or per-socket enterprise licensing tiers. As licensing models evolve and operational costs continue to rise, IT administrators increasingly turn to open-source virtualization solutions. Proxmox Virtual Environment platform gives enterprise-grade high availability without requiring costly software licenses.<br /> <br /> This is different from proprietary software models where features are locked behind paywalls, Proxmox VE includes all clustering and high-availability functionality out of the box. The software is published under the GPLv3, meaning every installation contains the exact same underlying codebase regardless of whether a paid support subscription is attached. The core engine includes full support for multi-node clustering, live virtual machine migration, and automated cluster recovery. Organizations can deploy resilient, available infrastructures using commodity hardware while reallocating capital toward physical infrastructure or network redundancy rather than software license keys.<br /> <br /> ==Architecture of Proxmox VE Clustering==<br /> Building a high-availability cluster in Proxmox VE begins with joining multiple physical nodes into a management unit. Under the hood, Proxmox relies on Corosync, a cluster engine that handles low-latency node communication and membership tracking. Corosync maintains constant heartbeat communication between cluster members, ensuring that every host remains aware of the operational status of every other host in the network.<br /> <br /> When a virtual machine or container is configured for high availability, the Proxmox HA Manager constantly monitors its state alongside host health. If a physical node experiences a hardware failure or network disconnect, the HA Manager detects the loss of heartbeat and initiates failover operations. The virtual workloads assigned to the failed host are automatically restarted on healthy nodes within the cluster. Because the management overhead is distributed and integrated into the core Debian base system, administrators gain cluster control without installing third-party management agents or secondary control plane appliances.<br /> <br /> ==Quorum and Avoiding Split-Brain Scenarios==<br /> A requirement for any cluster-based high availability architecture is maintaining quorum. Quorum represents the minimum number of active votes required for the cluster to make authoritative decisions about resource state. In Proxmox VE, each node typically contributes one vote to the total pool. To establish a healthy majority and safely execute failover commands, more than half of the total configured votes must be active and in agreement.<br /> <br /> Designing a cluster to maintain quorum prevents the catastrophic scenario known as a split-brain state. In a split-brain scenario, a network partition isolates nodes from one another, causing both sides of the network to believe the other has failed. Without quorum enforcement, both isolated groups might attempt to write to the same shared storage simultaneously, leading to unrecoverable data corruption. To avoid this, a standard Proxmox HA cluster should consist of at least three physical nodes. In environments where deploying three full-scale nodes is impractical, administrators can introduce a QDevice, an external lightweight vote-providing service running on a separate physical or virtual machine outside the main cluster, to serve as an impartial tie-breaker.<br /> <br /> ==Storage Strategy for High Availability==<br /> Automatic workload failover is only useful if the surviving nodes have access to the virtual machine disk files. Therefore, a successful high-availability architecture depends heavily on a shared or replicated storage foundation. Traditional deployments connect cluster nodes to external storage arrays using network protocols such as NFS or iSCSI, or SAN-based block storage utilizing shared volume managers like LVM-thin. While this centralized approach ensures all nodes can read and write to the same storage volumes, it introduces a potential single point of failure if the storage array itself goes down.<br /> <br /> To eliminate central storage bottlenecks and single points of failure without purchasing expensive external SAN hardware, Proxmox VE natively integrates Ceph storage. Ceph is a distributed, software-defined storage cluster that aggregates internal disks across all physical nodes into a single, highly available storage pool. When running Ceph alongside Proxmox VE, data is automatically replicated across multiple hosts according to defined placement policies. If a physical node fails, Ceph continues serving data from remaining replicas without interrupting storage availability. This hyperconverged infrastructure design allows small and medium-sized organizations to achieve compute and storage redundancy in a unified, cost-effective deployment.<br /> <br /> ==Managing Software Repositories Without Enterprise Subscriptions==<br /> One area that frequently causes confusion for new Proxmox administrators is package repository management and software updates. By default, a fresh Proxmox VE installation points to the enterprise package repository. When updating a cluster without an active paid subscription key, the system returns authentication warnings. However, Proxmox explicitly provides a freely accessible no-subscription repository containing all software updates, security patches, and new features.<br /> <br /> Operating an HA cluster using the no-subscription repository requires configuring the APT sources on each node to point to the open software channels. While packages in the no-subscription repository undergo testing before release, they are published on a faster cadence than those in the enterprise channel. For production clusters operating on the no-subscription branch, administrators should implement a controlled patching process, validating updates in a non-production environment before applying them to primary infrastructure. By properly maintaining repository configurations and applying upgrades methodically, teams can maintain a secure, updated, and stable cluster environment completely free of licensing charges.<br /> <br /> ==Deployment and Maintenance==<br /> Deploying a high-availability Proxmox cluster requires careful planning prior to initiating software installation. Network topology plays a role in cluster stability; administrators should dedicate separate physical or VLAN-segmented network interfaces exclusively for Corosync cluster communication. Because Corosync requires extremely low latency and predictable network throughput, sharing cluster communication channels with heavy storage traffic or tenant virtual machine traffic can trigger false-positive node timeouts and unintended failover events.<br /> <br /> Once the physical network and host installations are in place, creating the cluster is straightforward through either the Proxmox web management interface or the command line interface. Nodes are joined into the cluster using secure token exchange, after which shared storage pools and HA resource groups can be designated. Routine maintenance, such as host rebooting for kernel updates, is simplified through live migration. Virtual machines can be migrated between active nodes without downtime, allowing hardware maintenance or software patching to proceed smoothly without impacting service delivery.<br /> <br /> ==Enterprise-Grade Reliability==<br /> High availability virtualization no longer requires astronomical enterprise licensing budgets. By leveraging Proxmox VE, organizations gain access to a complete, open-source hypervisor capable of delivering clustering, automated failover, and software-defined storage out of the box. Whether deployed across three physical servers using Ceph or structured around a traditional shared storage backend with a QDevice, Proxmox provides all the technical capabilities required to keep applications online. With proper network design, storage planning, and repository management, IT teams can achieve enterprise-grade uptime while retaining complete control over their hardware and budget.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_21_2026&diff=4201 2026-07-21T01:00:58Z

<p>Tommy: Created page with &quot;=Understanding Proxmox and Open-Source High Availability= Proprietary hypervisors historically gated clustering, live migration, and automated failover behind expensive per-core or per-socket enterprise licensing tiers. As licensing models evolve and operational costs continue to rise, IT administrators increasingly turn to open-source virtualization solutions. Proxmox Virtual Environment platform gives enterprise-grade high availability without requiring costly software...&quot;</p> <hr /> <div>=Understanding Proxmox and Open-Source High Availability=<br /> Proprietary hypervisors historically gated clustering, live migration, and automated failover behind expensive per-core or per-socket enterprise licensing tiers. As licensing models evolve and operational costs continue to rise, IT administrators increasingly turn to open-source virtualization solutions. Proxmox Virtual Environment platform gives enterprise-grade high availability without requiring costly software licenses.<br /> <br /> This is different from proprietary software models where features are locked behind paywalls, Proxmox VE includes all clustering and high-availability functionality out of the box. The software is published under the GPLv3, meaning every installation contains the exact same underlying codebase regardless of whether a paid support subscription is attached. The core engine includes full support for multi-node clustering, live virtual machine migration, and automated cluster recovery. Organizations can deploy resilient, available infrastructures using commodity hardware while reallocating capital toward physical infrastructure or network redundancy rather than software license keys.<br /> <br /> ==Architecture of Proxmox VE Clustering==<br /> Building a high-availability cluster in Proxmox VE begins with joining multiple physical nodes into a management unit. Under the hood, Proxmox relies on Corosync, a cluster engine that handles low-latency node communication and membership tracking. Corosync maintains constant heartbeat communication between cluster members, ensuring that every host remains aware of the operational status of every other host in the network.<br /> <br /> When a virtual machine or container is configured for high availability, the Proxmox HA Manager constantly monitors its state alongside host health. If a physical node experiences a hardware failure or network disconnect, the HA Manager detects the loss of heartbeat and initiates failover operations. The virtual workloads assigned to the failed host are automatically restarted on healthy nodes within the cluster. Because the management overhead is distributed and integrated into the core Debian base system, administrators gain cluster control without installing third-party management agents or secondary control plane appliances.<br /> <br /> ==Quorum and Avoiding Split-Brain Scenarios==<br /> A requirement for any cluster-based high availability architecture is maintaining quorum. Quorum represents the minimum number of active votes required for the cluster to make authoritative decisions about resource state. In Proxmox VE, each node typically contributes one vote to the total pool. To establish a healthy majority and safely execute failover commands, more than half of the total configured votes must be active and in agreement.<br /> <br /> Designing a cluster to maintain quorum prevents the catastrophic scenario known as a split-brain state. In a split-brain scenario, a network partition isolates nodes from one another, causing both sides of the network to believe the other has failed. Without quorum enforcement, both isolated groups might attempt to write to the same shared storage simultaneously, leading to unrecoverable data corruption. To avoid this, a standard Proxmox HA cluster should consist of at least three physical nodes. In environments where deploying three full-scale nodes is impractical, administrators can introduce a QDevice, an external lightweight vote-providing service running on a separate physical or virtual machine outside the main cluster, to serve as an impartial tie-breaker.<br /> <br /> ==Storage Strategy for High Availability==<br /> Automatic workload failover is only useful if the surviving nodes have access to the virtual machine disk files. Therefore, a successful high-availability architecture depends heavily on a shared or replicated storage foundation. Traditional deployments connect cluster nodes to external storage arrays using network protocols such as NFS or iSCSI, or SAN-based block storage utilizing shared volume managers like LVM-thin. While this centralized approach ensures all nodes can read and write to the same storage volumes, it introduces a potential single point of failure if the storage array itself goes down.<br /> <br /> To eliminate central storage bottlenecks and single points of failure without purchasing expensive external SAN hardware, Proxmox VE natively integrates Ceph storage. Ceph is a distributed, software-defined storage cluster that aggregates internal disks across all physical nodes into a single, highly available storage pool. When running Ceph alongside Proxmox VE, data is automatically replicated across multiple hosts according to defined placement policies. If a physical node fails, Ceph continues serving data from remaining replicas without interrupting storage availability. This hyperconverged infrastructure design allows small and medium-sized organizations to achieve compute and storage redundancy in a unified, cost-effective deployment.<br /> <br /> ==Managing Software Repositories Without Enterprise Subscriptions==<br /> One area that frequently causes confusion for new Proxmox administrators is package repository management and software updates. By default, a fresh Proxmox VE installation points to the enterprise package repository. When updating a cluster without an active paid subscription key, the system returns authentication warnings. However, Proxmox explicitly provides a freely accessible no-subscription repository containing all software updates, security patches, and new features.<br /> <br /> Operating an HA cluster using the no-subscription repository requires configuring the APT sources on each node to point to the open software channels. While packages in the no-subscription repository undergo testing before release, they are published on a faster cadence than those in the enterprise channel. For production clusters operating on the no-subscription branch, administrators should implement a controlled patching process, validating updates in a non-production environment before applying them to primary infrastructure. By properly maintaining repository configurations and applying upgrades methodically, teams can maintain a secure, updated, and stable cluster environment completely free of licensing charges.<br /> <br /> ==Deployment and Maintenance==<br /> Deploying a high-availability Proxmox cluster requires careful planning prior to initiating software installation. Network topology plays a role in cluster stability; administrators should dedicate separate physical or VLAN-segmented network interfaces exclusively for Corosync cluster communication. Because Corosync requires extremely low latency and predictable network throughput, sharing cluster communication channels with heavy storage traffic or tenant virtual machine traffic can trigger false-positive node timeouts and unintended failover events.<br /> <br /> Once the physical network and host installations are in place, creating the cluster is straightforward through either the Proxmox web management interface or the command line interface. Nodes are joined into the cluster using secure token exchange, after which shared storage pools and HA resource groups can be designated. Routine maintenance, such as host rebooting for kernel updates, is simplified through live migration. Virtual machines can be migrated between active nodes without downtime, allowing hardware maintenance or software patching to proceed smoothly without impacting service delivery.<br /> <br /> ==Enterprise-Grade Reliability==<br /> High availability virtualization no longer requires astronomical enterprise licensing budgets. By leveraging Proxmox VE, organizations gain access to a complete, open-source hypervisor capable of delivering clustering, automated failover, and software-defined storage out of the box. Whether deployed across three physical servers using Ceph or structured around a traditional shared storage backend with a QDevice, Proxmox provides all the technical capabilities required to keep applications online. With proper network design, storage planning, and repository management, IT teams can achieve enterprise-grade uptime while retaining complete control over their hardware and budget.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4200 2026-07-21T00:48:08Z

<p>Tommy: /* July 2026 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> *[[Daily_Post_July_21_2026|Daily Post July 21 2026 - Understanding Proxmox Open-Source High Availability]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc&diff=4199 2026-07-20T02:22:43Z

<p>Tommy: /* FOSS Consulting &amp; Open Source Solutions for SMEs in Japan */</p> <hr /> <div>{{#seo:<br /> |title=mintarc | FOSS Consulting &amp; IT Infrastructure for SMEs in Japan<br /> |description=Discover how mintarc specializes in FOSS/OSS consulting, Linux systems, Kubernetes, cloud solutions, and IT infrastructure to empower your business.<br /> |keywords=FOSS, OSS, open-source consulting, Linux systems, Kubernetes solutions, cloud infrastructure, IT consulting, open-source software<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |site_name=mintarc<br /> |locale=en_US<br /> |type=website<br /> }}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> <br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> <br /> = FOSS Consulting &amp; Open Source Solutions for SMEs in Japan =<br /> === Innovation Through Openness ===<br /> [[File:FossPenguin.png|frameless|right|upright=0.5|alt=Character|link=https://matomo.mintarc.com/mautic/qaeng]]<br /> <br /> The value of open collaboration, transparency, and innovation is at the heart of everything we do. Whether you’re looking to streamline your IT infrastructure, gain the potential of cloud solutions, or unlock the benefits of Free and Open-Source Software (FOSS), we’re here to help you take your business to the next level.<br /> <br /> FOSS is software that is:<br /> *Free to Use No licensing fees or restrictions on usage.<br /> *Open for Collaboration The source code is publicly available for inspection, modification, and distribution.<br /> *Community-Driven Developed by a global community of contributors who prioritize transparency and innovation.<br /> <br /> With FOSS, businesses can reduce costs, improve security through peer-reviewed code, and maintain greater control over their technology stack.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Explain_FOSS# &amp;nbsp;&amp;nbsp;&amp;nbsp;Learn more about FOSS]&lt;/span&gt;<br /> <br /> == How Can mintarc Help Your Business? ==<br /> === Your Partner in FOSS Integration ===<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 100%; border-collapse: collapse; font-family: Arial, sans-serif; font-size: 14px; text-align: center; background-color: #f9f9f9; border: 1px solid #ddd;&quot;<br /> |-<br /> ! style=&quot;background-color: #3eb489; color: white; padding: 10px; border: 1px solid #ddd;&quot; | FOSS Consulting &amp; Strategy Development, Transform Your business<br /> ! style=&quot;background-color: #3eb489; color: white; padding: 10px; border: 1px solid #ddd;&quot; | Cloud &amp; On-Premise Deployments, Customise solutions<br /> ! style=&quot;background-color: #3eb489; color: white; padding: 10px; border: 1px solid #ddd;&quot; | Training &amp; Support, Maintain Momentum<br /> |-<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | Assess your current IT infrastructure.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | Deploy open-source solutions on mintarc Cloud or other providers like Akamai.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | Equip your team with the skills to use and manage FOSS effectively.<br /> |-<br /> | style=&quot;padding: 8px; border: 1px solid #ddd; background-color:#f2f2f2;&quot; | Identify opportunities to incorporate FOSS tools.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd; background-color:#f2f2f2;&quot; | Design hybrid or fully on-premise systems for maximum control.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd; background-color:#f2f2f2;&quot; | Provide ongoing support for maintenance and updates.<br /> |-<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | Develop a roadmap for integration.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | <br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | <br /> |}<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Explore_our_Services &amp;nbsp;&amp;nbsp;&amp;nbsp;Explore our Services]&lt;/span&gt;<br /> <br /> === The Process ===<br /> [[File:Foss_process.png|frameless|center|upright=3|alt=Process Flow for a Transition|link=https://mintarc.com/minthome/images/2/2c/Foss_process.png|Flow for a Transition]]<br /> <br /> == Why Consider Free and Open-Source Software? ==<br /> '''The World Runs on Open Technology.'''<br /> &lt;div style=&quot;border: 1px solid blue; background-color: #e6f7ff; padding: 10px; margin: 5px; color: inherit;&quot;&gt;<br /> Open-source software powers a significant portion of the world's infrastructure. For example, Linux, an open-source operating system, runs the majority of servers globally, forming the backbone of web services and cloud platforms. Similarly, open-source projects like Kubernetes and OpenStack are integral to cloud computing.<br /> &lt;/div&gt;<br /> <br /> Adopting FOSS brings numerous advantages:<br /> *Cost Efficiency eliminate expensive licensing fees.<br /> *Flexibility customize software to meet specific business requirements.<br /> *Security benefit from peer-reviewed code that ensures greater reliability.<br /> *Scalability scale your operations without worrying about restrictive licenses.<br /> *Community support join a global network of developers and users.<br /> <br /> You're not adopting software you’re embracing a philosophy of innovation and collaboration.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Discover_the_benefits_of_FOSS# &amp;nbsp;&amp;nbsp;&amp;nbsp;Discover the benefits of FOSS]&lt;/span&gt;<br /> <br /> ==Our Partners==<br /> === Collabora Online Partnership ===<br /> [[File:Collabora-logo.png|frameless|right|upright=0.3|alt=Collabora Online|link=https://www.collaboraonline.com/]]<br /> <br /> Our partnership with Collabora Online underscores our commitment to championing tools like Collabora Online, helping users with document editing and collaboration capabilities. We believe this partnership will enable us to provide greater value to our clients looking for flexible open-source solutions<br /> <br /> Checkout Support [https://mintarc.com/minthome/index.php?title=Collabora_Offerings#What_are_the_Costs_Associated_with_Collabora_online '''Pricing'''] |<br /> You can also visit the [https://mintarc.com/minthome/index.php?title=Collabora_FAQ '''FAQ'''] | [[Collabora_Tutorials | '''Tutorials''']]<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Our_collabora_online_partnership &amp;nbsp;&amp;nbsp;&amp;nbsp;Our Collabora Online Partnership]&lt;/span&gt;<br /> <br /> === Cybersecurity Consulting Services (CS2)===<br /> [[File:Cs2-logo4.png|frameless|right|upright=0.3|alt=CS2|link=https://www.cybers2.com/]]<br /> <br /> Partnering with Cybers2, we reaffirm our dedication to helping Japanese SMEs with trusted, transparent, and future-ready IT solutions that address evolving security challenges and business demands with professionalism and care. We invite businesses interested in strengthening their IT resilience and open-source adoption to engage with us for tailored consultation and support<br /> <br /> You can also review the presentation [https://matomo.mintarc.com/mautic/asset/6:cs2partnerpresentationpdf '''Presention'''] <br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Our_CS2_partnership Our CS2 Partnership]&lt;/span&gt;<br /> <br /> == Our Open Source Commitment with PeppermintOS ==<br /> '''A Testament to Our Passion for Open Source'''<br /> [[File:PepperMintOS_screenshot.png|frameless|right|upright=1.5|alt=Peppermint OS Screenshot| PeppermintOS Screenshot]]<br /> <br /> We support the development of PeppermintOS, a lightweight Linux distribution designed for speed and simplicity. Built on open-source principles, PeppermintOS demonstrates our commitment to helping users with accessible technology.<br /> <br /> PeppermintOS has:<br /> *Lightweight design optimized for performance.<br /> *Integration with web apps and cloud services.<br /> *Customizable interface tailored to user preferences.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://peppermintos.com/ &amp;nbsp;&amp;nbsp;&amp;nbsp;Learn more about PeppermintOS]&lt;/span&gt;<br /> <br /> == Transparent, Flexible Pricing for FOSS Deployments in Japan&quot; ==<br /> === Save on licensing fees, reduce ownership costs, and gain freedom with tailored open-source solutions. ===<br /> We specialize in helping businesses gain the potential of FOSS. Our pricing reflects the flexibility, transparency, and long-term value that FOSS brings to organizations.<br /> <br /> * '''No Licensing Fees:''' Eliminate costly SaaS software licenses.<br /> * '''Cost Efficiency:''' Reduce total cost of ownership while scaling your operations.<br /> * '''Freedom &amp; Customization:''' Avoid vendor lock-in and tailor solutions to your unique needs.<br /> * '''Localized Support:''' Overcome language barriers with our Japanese-language support.<br /> <br /> FOSS offers SMBs an opportunity to improve competitiveness while streamlining operations. Whether you're looking to reduce costs or drive flexibility, we’re here to guide you every step of the way.<br /> <br /> ''Explore our flexible pricing tiers designed for businesses of all sizes. Learn how FOSS can save you money.''<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Pring_Page &amp;nbsp;&amp;nbsp;&amp;nbsp;Read More About Pricing]&lt;/span&gt;<br /> <br /> == Migrating to FOSS: A Simple Guide for Small Businesses ==<br /> Many small and medium-sized enterprises (SMEs) are increasingly considering a transition to open-source solutions as a means to reduce costs, gain greater control over their operations, and enhance security. This shift is driven by the growing need for digital transformation in a competitive and resource-constrained environment. However, the journey to adopting FOSS is multifaceted, offering both opportunities and challenges.<br /> <br /> FOSS solutions provide SMEs with significant cost advantages by eliminating licensing fees associated with proprietary software. This allows businesses to allocate resources to other critical areas of operation. For example, tools like Joomla for website management, Asterisk for telecommunication, and SuiteCRM for customer relationship management enable SMEs to streamline operations without incurring high costs. FOSS offers flexibility and customization, allowing businesses to tailor software to their unique needs. This adaptability is particularly valuable for SMEs with specialized requirements or limited budgets.<br /> <br /> Despite these advantages, transitioning to open-source solutions is not without challenges. One major hurdle is the complexity of implementation and maintenance. While FOSS reduces upfront costs, it may require technical expertise for customization, integration, and ongoing support. Many SMEs address this by partnering with third-party providers who specialize in managing open-source technologies. These providers can help minimize downtime, ensure scalability, and handle updates efficiently.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Migration_Guide &amp;nbsp;&amp;nbsp;&amp;nbsp;Continue to the Guide]&lt;/span&gt;<br /> <br /> == FrequentlyAsked Questions (FAQ) ==<br /> The questions in the FAQ for small to medium enterprise (SMEs) looking to migrate to OSS/FOSS/FLOSS are designed to address the most common concerns and considerations during the decision-making and implementation process. <br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=FAQ &amp;nbsp;&amp;nbsp;&amp;nbsp;Continue to the FAQ]&lt;/span&gt;<br /> <br /> == Case Studies ==<br /> === mintarc: A Case Study in FOSS-Driven Success ===<br /> A technology company in Japan completely dedicated to championing Free and Open Source Software (FOSS), has built its entire operational infrastructure on these principles. This case study explores mintarc's process, strategies, challenges, and successes achieved through its dedication to FOSS.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_Case &amp;nbsp;&amp;nbsp;&amp;nbsp;Continue to mintarc case]&lt;/span&gt;<br /> <br /> ==White Papers==<br /> <br /> *[https://mintarc.com/minthome/images/2/2a/TheSovereignSME.pdf '''The Sovereign Small and medium enterprises (SME)''']<br /> <br /> <br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us'''] | TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']</div>

Tommy https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc&diff=4198 2026-07-20T02:22:34Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title=mintarc | FOSS Consulting &amp; IT Infrastructure for SMEs in Japan<br /> |description=Discover how mintarc specializes in FOSS/OSS consulting, Linux systems, Kubernetes, cloud solutions, and IT infrastructure to empower your business.<br /> |keywords=FOSS, OSS, open-source consulting, Linux systems, Kubernetes solutions, cloud infrastructure, IT consulting, open-source software<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |site_name=mintarc<br /> |locale=en_US<br /> |type=website<br /> }}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> <br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> <br /> = FOSS Consulting &amp; Open Source Solutions for SMEs in Japan =<br /> === Innovation Through Openness ===<br /> [[File:FossPenguin.png|frameless|right|upright=0.5|alt=Character|link=https://matomo.mintarc.com/mautic/qaeng]]<br /> <br /> The value of open collaboration, transparency, and innovation is at the heart of everything we do. Whether you’re looking to streamline your IT infrastructure, gain the potential of cloud solutions, or unlock the benefits of Free and Open-Source Software (FOSS), we’re here to help you take your business to the next level.<br /> <br /> FOSS is software that is:<br /> *Free to Use No licensing fees or restrictions on usage.<br /> *Open for Collaboration The source code is publicly available for inspection, modification, and distribution..<br /> *Community-Driven Developed by a global community of contributors who prioritize transparency and innovation.<br /> <br /> With FOSS, businesses can reduce costs, improve security through peer-reviewed code, and maintain greater control over their technology stack.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Explain_FOSS# &amp;nbsp;&amp;nbsp;&amp;nbsp;Learn more about FOSS]&lt;/span&gt;<br /> <br /> == How Can mintarc Help Your Business? ==<br /> === Your Partner in FOSS Integration ===<br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 100%; border-collapse: collapse; font-family: Arial, sans-serif; font-size: 14px; text-align: center; background-color: #f9f9f9; border: 1px solid #ddd;&quot;<br /> |-<br /> ! style=&quot;background-color: #3eb489; color: white; padding: 10px; border: 1px solid #ddd;&quot; | FOSS Consulting &amp; Strategy Development, Transform Your business<br /> ! style=&quot;background-color: #3eb489; color: white; padding: 10px; border: 1px solid #ddd;&quot; | Cloud &amp; On-Premise Deployments, Customise solutions<br /> ! style=&quot;background-color: #3eb489; color: white; padding: 10px; border: 1px solid #ddd;&quot; | Training &amp; Support, Maintain Momentum<br /> |-<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | Assess your current IT infrastructure.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | Deploy open-source solutions on mintarc Cloud or other providers like Akamai.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | Equip your team with the skills to use and manage FOSS effectively.<br /> |-<br /> | style=&quot;padding: 8px; border: 1px solid #ddd; background-color:#f2f2f2;&quot; | Identify opportunities to incorporate FOSS tools.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd; background-color:#f2f2f2;&quot; | Design hybrid or fully on-premise systems for maximum control.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd; background-color:#f2f2f2;&quot; | Provide ongoing support for maintenance and updates.<br /> |-<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | Develop a roadmap for integration.<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | <br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | <br /> |}<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Explore_our_Services &amp;nbsp;&amp;nbsp;&amp;nbsp;Explore our Services]&lt;/span&gt;<br /> <br /> === The Process ===<br /> [[File:Foss_process.png|frameless|center|upright=3|alt=Process Flow for a Transition|link=https://mintarc.com/minthome/images/2/2c/Foss_process.png|Flow for a Transition]]<br /> <br /> == Why Consider Free and Open-Source Software? ==<br /> '''The World Runs on Open Technology.'''<br /> &lt;div style=&quot;border: 1px solid blue; background-color: #e6f7ff; padding: 10px; margin: 5px; color: inherit;&quot;&gt;<br /> Open-source software powers a significant portion of the world's infrastructure. For example, Linux, an open-source operating system, runs the majority of servers globally, forming the backbone of web services and cloud platforms. Similarly, open-source projects like Kubernetes and OpenStack are integral to cloud computing.<br /> &lt;/div&gt;<br /> <br /> Adopting FOSS brings numerous advantages:<br /> *Cost Efficiency eliminate expensive licensing fees.<br /> *Flexibility customize software to meet specific business requirements.<br /> *Security benefit from peer-reviewed code that ensures greater reliability.<br /> *Scalability scale your operations without worrying about restrictive licenses.<br /> *Community support join a global network of developers and users.<br /> <br /> You're not adopting software you’re embracing a philosophy of innovation and collaboration.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Discover_the_benefits_of_FOSS# &amp;nbsp;&amp;nbsp;&amp;nbsp;Discover the benefits of FOSS]&lt;/span&gt;<br /> <br /> ==Our Partners==<br /> === Collabora Online Partnership ===<br /> [[File:Collabora-logo.png|frameless|right|upright=0.3|alt=Collabora Online|link=https://www.collaboraonline.com/]]<br /> <br /> Our partnership with Collabora Online underscores our commitment to championing tools like Collabora Online, helping users with document editing and collaboration capabilities. We believe this partnership will enable us to provide greater value to our clients looking for flexible open-source solutions<br /> <br /> Checkout Support [https://mintarc.com/minthome/index.php?title=Collabora_Offerings#What_are_the_Costs_Associated_with_Collabora_online '''Pricing'''] |<br /> You can also visit the [https://mintarc.com/minthome/index.php?title=Collabora_FAQ '''FAQ'''] | [[Collabora_Tutorials | '''Tutorials''']]<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Our_collabora_online_partnership &amp;nbsp;&amp;nbsp;&amp;nbsp;Our Collabora Online Partnership]&lt;/span&gt;<br /> <br /> === Cybersecurity Consulting Services (CS2)===<br /> [[File:Cs2-logo4.png|frameless|right|upright=0.3|alt=CS2|link=https://www.cybers2.com/]]<br /> <br /> Partnering with Cybers2, we reaffirm our dedication to helping Japanese SMEs with trusted, transparent, and future-ready IT solutions that address evolving security challenges and business demands with professionalism and care. We invite businesses interested in strengthening their IT resilience and open-source adoption to engage with us for tailored consultation and support<br /> <br /> You can also review the presentation [https://matomo.mintarc.com/mautic/asset/6:cs2partnerpresentationpdf '''Presention'''] <br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Our_CS2_partnership Our CS2 Partnership]&lt;/span&gt;<br /> <br /> == Our Open Source Commitment with PeppermintOS ==<br /> '''A Testament to Our Passion for Open Source'''<br /> [[File:PepperMintOS_screenshot.png|frameless|right|upright=1.5|alt=Peppermint OS Screenshot| PeppermintOS Screenshot]]<br /> <br /> We support the development of PeppermintOS, a lightweight Linux distribution designed for speed and simplicity. Built on open-source principles, PeppermintOS demonstrates our commitment to helping users with accessible technology.<br /> <br /> PeppermintOS has:<br /> *Lightweight design optimized for performance.<br /> *Integration with web apps and cloud services.<br /> *Customizable interface tailored to user preferences.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://peppermintos.com/ &amp;nbsp;&amp;nbsp;&amp;nbsp;Learn more about PeppermintOS]&lt;/span&gt;<br /> <br /> == Transparent, Flexible Pricing for FOSS Deployments in Japan&quot; ==<br /> === Save on licensing fees, reduce ownership costs, and gain freedom with tailored open-source solutions. ===<br /> We specialize in helping businesses gain the potential of FOSS. Our pricing reflects the flexibility, transparency, and long-term value that FOSS brings to organizations.<br /> <br /> * '''No Licensing Fees:''' Eliminate costly SaaS software licenses.<br /> * '''Cost Efficiency:''' Reduce total cost of ownership while scaling your operations.<br /> * '''Freedom &amp; Customization:''' Avoid vendor lock-in and tailor solutions to your unique needs.<br /> * '''Localized Support:''' Overcome language barriers with our Japanese-language support.<br /> <br /> FOSS offers SMBs an opportunity to improve competitiveness while streamlining operations. Whether you're looking to reduce costs or drive flexibility, we’re here to guide you every step of the way.<br /> <br /> ''Explore our flexible pricing tiers designed for businesses of all sizes. Learn how FOSS can save you money.''<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Pring_Page &amp;nbsp;&amp;nbsp;&amp;nbsp;Read More About Pricing]&lt;/span&gt;<br /> <br /> == Migrating to FOSS: A Simple Guide for Small Businesses ==<br /> Many small and medium-sized enterprises (SMEs) are increasingly considering a transition to open-source solutions as a means to reduce costs, gain greater control over their operations, and enhance security. This shift is driven by the growing need for digital transformation in a competitive and resource-constrained environment. However, the journey to adopting FOSS is multifaceted, offering both opportunities and challenges.<br /> <br /> FOSS solutions provide SMEs with significant cost advantages by eliminating licensing fees associated with proprietary software. This allows businesses to allocate resources to other critical areas of operation. For example, tools like Joomla for website management, Asterisk for telecommunication, and SuiteCRM for customer relationship management enable SMEs to streamline operations without incurring high costs. FOSS offers flexibility and customization, allowing businesses to tailor software to their unique needs. This adaptability is particularly valuable for SMEs with specialized requirements or limited budgets.<br /> <br /> Despite these advantages, transitioning to open-source solutions is not without challenges. One major hurdle is the complexity of implementation and maintenance. While FOSS reduces upfront costs, it may require technical expertise for customization, integration, and ongoing support. Many SMEs address this by partnering with third-party providers who specialize in managing open-source technologies. These providers can help minimize downtime, ensure scalability, and handle updates efficiently.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Migration_Guide &amp;nbsp;&amp;nbsp;&amp;nbsp;Continue to the Guide]&lt;/span&gt;<br /> <br /> == FrequentlyAsked Questions (FAQ) ==<br /> The questions in the FAQ for small to medium enterprise (SMEs) looking to migrate to OSS/FOSS/FLOSS are designed to address the most common concerns and considerations during the decision-making and implementation process. <br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=FAQ &amp;nbsp;&amp;nbsp;&amp;nbsp;Continue to the FAQ]&lt;/span&gt;<br /> <br /> == Case Studies ==<br /> === mintarc: A Case Study in FOSS-Driven Success ===<br /> A technology company in Japan completely dedicated to championing Free and Open Source Software (FOSS), has built its entire operational infrastructure on these principles. This case study explores mintarc's process, strategies, challenges, and successes achieved through its dedication to FOSS.<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_Case &amp;nbsp;&amp;nbsp;&amp;nbsp;Continue to mintarc case]&lt;/span&gt;<br /> <br /> ==White Papers==<br /> <br /> *[https://mintarc.com/minthome/images/2/2a/TheSovereignSME.pdf '''The Sovereign Small and medium enterprises (SME)''']<br /> <br /> <br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us'''] | TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_17_2026&diff=4197 2026-07-17T02:00:02Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Proxmox Backup Server <br /> |description= Explore how Proxmox Backup Server utilizes client-side deduplication, block-level integrity, and tight hypervisor integration to minimize data loss and accelerate recovery times in virtualized environments.<br /> |keywords= Proxmox Backup Server, PBS, Near-Zero RPO, RTO, Virtualization Backup, Data Deduplication, Disaster Recovery, Data Integrity, AES-256 Encryption, Proxmox VE<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_17_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Promox Backup Server=<br /> This is an enterprise-grade, open-source backup and restoration solution designed specifically to address the challenges of protecting virtualized environments. It functions as an optimized, dedicated server application that provides a centralized repository for the secure and efficient storage of data from Proxmox Virtual Environment and other Linux-based systems. This is different from traditional, legacy backup software that relies on bulky file-level or block-level copying methods that are bandwidth-intensive and slow, PBS uses client-side deduplication technology. This means that before any data is even sent over the network, the Proxmox Backup client analyzes the data stream, breaks it into smaller, manageable chunks, and identifies redundant segments. Only transmitting and storing the data blocks that have changed since the last backup a process known as incremental-forever backup—it achieves massive space savings and significantly reduced backup window durations.<br /> <br /> The architecture of Proxmox Backup Server is built to prioritize performance and data integrity above all else. It is designed to work in harmony with the Proxmox virtualization platform, using an API-driven integration that allows for the backup of virtual machines and containers while they are running, without interrupting service. Because it operates at the block level rather than the file level, it can handle large virtual disk images with efficiency. This efficiency is bolstered by the server’s ability to perform garbage collection, a background process that systematically reclaims space by identifying and removing chunks that are no longer referenced by any backup snapshots. This ensures that the storage repository remains lean and performant over time, avoiding the pitfalls of storage bloat that plague many enterprise backup environments.<br /> <br /> ==The Datastore==<br /> The fundamental unit of organization within Proxmox Backup Server is the datastore. A datastore acts as a logical container that resides on the server’s underlying storage which can be anything from local SSDs and HDDs to network-attached storage or ZFS-based pools. Because the system is agnostic regarding the underlying storage hardware, administrators can design a storage tier that fits their specific performance and capacity requirements. When a backup job is triggered, the client—typically a Proxmox VE node communicates with the PBS instance, calculates the hash of every data chunk, and verifies whether that specific chunk already exists in the destination datastore. If it does, the redundant transmission is skipped entirely. This deduplication process is essentially the engine that drives the system’s ability to manage petabytes of data, even when the actual amount of unique information is significantly smaller.<br /> <br /> ==Security and Integrity==<br /> Proxmox Backup Server also distinguishes itself through an approach to security and data verification. Every single chunk of data is indexed and validated using SHA-256 checksums, which protects the repository against the silent threats of data corruption and bit rot. Beyond detection, the system provides integrated, client-side encryption, which is a good feature for data privacy standards. Employing AES-256 in Galois/Counter Mode, PBS ensures that the data is encrypted before it leaves the source machine and remains encrypted while at rest on the backup server. This means that even if a backup repository were physically compromised or stolen, the actual contents would remain inaccessible to unauthorized parties. The combination of these features deduplication, restoration capabilities, and encryption positions Proxmox Backup Server as an great tool for administrators tasked with maintaining high availability and verifiable data protection in a virtualized ecosystem.<br /> <br /> ==Optimizing Recovery Point Objectives==<br /> The Recovery Point Objective is primarily a function of backup frequency. In traditional environments, high-frequency backups are often avoided due to the performance impact they exert on production storage and the resulting blowup in storage costs. Proxmox Backup Server mitigates these concerns through its efficient deduplication engine. Using dynamic chunking with a rolling hash algorithm, PBS ensures that even across multiple virtual machines sharing similar operating systems or data structures, only a single instance of a repeated data block is saved. This space-efficient architecture helps IT teams to schedule backups much more aggressively. When backups are lightweight and fast, scheduling them every few minutes or hourly becomes a realistic strategy rather than a performance-prohibitive burden. This frequency directly minimizes the data loss window, effectively driving the RPO toward zero.<br /> <br /> ==Accelerating Recovery Time Objectives==<br /> RPO focuses on the freshness of the backup, the Recovery Time Objective centers on the speed of restoration. PBS facilitates rapid recovery through its integration with the Proxmox Virtual Environment. In a disaster scenario, every minute spent moving data or waiting for large volumes to rehydrate is a direct hit to business productivity. Proxmox Backup Server allows for near-instantaneous restoration by enabling administrators to mount backups directly as FUSE-based storage or perform live restores. This means that a virtual machine can be started before the entire image has been fully moved back to the production storage. Prioritizing the most critical data sectors, the system ensures that services return to an operational state while the background restoration process completes. This handoff between the backup repository and the hypervisor is what enables organizations to meet aggressive RTO requirements, even when dealing with large datasets.<br /> <br /> ==Integrity and Security==<br /> A backup is only as valuable as its ability to be restored, and in the current cyber threat climate, security is inseparable from availability. Proxmox Backup Server places a heavy emphasis on data integrity through the use of built-in, mandatory SHA-256 checksumming. Every data chunk, manifest, and index file is validated to ensure that bit rot or silent data corruption does not compromise the recovery process. This integrity verification is performed continuously, giving administrators the confidence that when a disaster does occur, the recovery path is clear and reliable. The system employs strong, client-side AES-256 encryption. Making sure that data is encrypted before it ever leaves the production host, PBS guarantees that even if a backup repository is accessed by an unauthorized entity, the data remains useless. This security-first approach is essential for meeting compliance frameworks, such as GDPR or NIS2, which require rigorous evidence of both data protection and recoverability.<br /> <br /> ==Scaling for Long-Term==<br /> As an enterprise-grade solution, Proxmox Backup Server is built to scale alongside the infrastructure it protects. Through its RESTful API, IT teams can automate the synchronization of datastores to remote, offsite locations, creating a defense against localized hardware failures or catastrophic data center outages. These remote sync jobs are equally efficient, transferring only the changes since the last synchronization, which ensures that offsite replicas remain current without saturating inter-site links. Combining local, restore capabilities with immutable or offsite secondary copies, organizations can build a layered defense that satisfies the most stringent audit requirements. Whether it is protecting a small cluster or a sprawling enterprise environment, the architecture of PBS provides the predictability and stability that many system administrators need. The transition to such a system is not just about adopting a new piece of software, but about embracing a strategy of proactive, verifiable, and lightning-fast recovery that keeps the organization resilient.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_17_2026&diff=4196 2026-07-17T01:59:14Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title= Using Virtual Networks: Linux Bridges, Bonds, and VLANs in Proxmox<br /> |description= A deep dive into Proxmox VE networking, exploring how Linux bridges, network bonds, and VLANs work together to create resilient, segmented, and high-performance virtualized environments.<br /> |keywords= Proxmox Networking, Linux Bridge, Network Bonding, VLANs, Proxmox VE, Virtualization Networking, LACP, 802.1Q, Network Segmentation, High Availability<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_16_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Promox Backup Server=<br /> This is an enterprise-grade, open-source backup and restoration solution designed specifically to address the challenges of protecting virtualized environments. It functions as an optimized, dedicated server application that provides a centralized repository for the secure and efficient storage of data from Proxmox Virtual Environment and other Linux-based systems. This is different from traditional, legacy backup software that relies on bulky file-level or block-level copying methods that are bandwidth-intensive and slow, PBS uses client-side deduplication technology. This means that before any data is even sent over the network, the Proxmox Backup client analyzes the data stream, breaks it into smaller, manageable chunks, and identifies redundant segments. Only transmitting and storing the data blocks that have changed since the last backup a process known as incremental-forever backup—it achieves massive space savings and significantly reduced backup window durations.<br /> <br /> The architecture of Proxmox Backup Server is built to prioritize performance and data integrity above all else. It is designed to work in harmony with the Proxmox virtualization platform, using an API-driven integration that allows for the backup of virtual machines and containers while they are running, without interrupting service. Because it operates at the block level rather than the file level, it can handle large virtual disk images with efficiency. This efficiency is bolstered by the server’s ability to perform garbage collection, a background process that systematically reclaims space by identifying and removing chunks that are no longer referenced by any backup snapshots. This ensures that the storage repository remains lean and performant over time, avoiding the pitfalls of storage bloat that plague many enterprise backup environments.<br /> <br /> ==The Datastore==<br /> The fundamental unit of organization within Proxmox Backup Server is the datastore. A datastore acts as a logical container that resides on the server’s underlying storage which can be anything from local SSDs and HDDs to network-attached storage or ZFS-based pools. Because the system is agnostic regarding the underlying storage hardware, administrators can design a storage tier that fits their specific performance and capacity requirements. When a backup job is triggered, the client—typically a Proxmox VE node communicates with the PBS instance, calculates the hash of every data chunk, and verifies whether that specific chunk already exists in the destination datastore. If it does, the redundant transmission is skipped entirely. This deduplication process is essentially the engine that drives the system’s ability to manage petabytes of data, even when the actual amount of unique information is significantly smaller.<br /> <br /> ==Security and Integrity==<br /> Proxmox Backup Server also distinguishes itself through an approach to security and data verification. Every single chunk of data is indexed and validated using SHA-256 checksums, which protects the repository against the silent threats of data corruption and bit rot. Beyond detection, the system provides integrated, client-side encryption, which is a good feature for data privacy standards. Employing AES-256 in Galois/Counter Mode, PBS ensures that the data is encrypted before it leaves the source machine and remains encrypted while at rest on the backup server. This means that even if a backup repository were physically compromised or stolen, the actual contents would remain inaccessible to unauthorized parties. The combination of these features deduplication, restoration capabilities, and encryption positions Proxmox Backup Server as an great tool for administrators tasked with maintaining high availability and verifiable data protection in a virtualized ecosystem.<br /> <br /> ==Optimizing Recovery Point Objectives==<br /> The Recovery Point Objective is primarily a function of backup frequency. In traditional environments, high-frequency backups are often avoided due to the performance impact they exert on production storage and the resulting blowup in storage costs. Proxmox Backup Server mitigates these concerns through its efficient deduplication engine. Using dynamic chunking with a rolling hash algorithm, PBS ensures that even across multiple virtual machines sharing similar operating systems or data structures, only a single instance of a repeated data block is saved. This space-efficient architecture helps IT teams to schedule backups much more aggressively. When backups are lightweight and fast, scheduling them every few minutes or hourly becomes a realistic strategy rather than a performance-prohibitive burden. This frequency directly minimizes the data loss window, effectively driving the RPO toward zero.<br /> <br /> ==Accelerating Recovery Time Objectives==<br /> RPO focuses on the freshness of the backup, the Recovery Time Objective centers on the speed of restoration. PBS facilitates rapid recovery through its integration with the Proxmox Virtual Environment. In a disaster scenario, every minute spent moving data or waiting for large volumes to rehydrate is a direct hit to business productivity. Proxmox Backup Server allows for near-instantaneous restoration by enabling administrators to mount backups directly as FUSE-based storage or perform live restores. This means that a virtual machine can be started before the entire image has been fully moved back to the production storage. Prioritizing the most critical data sectors, the system ensures that services return to an operational state while the background restoration process completes. This handoff between the backup repository and the hypervisor is what enables organizations to meet aggressive RTO requirements, even when dealing with large datasets.<br /> <br /> ==Integrity and Security==<br /> A backup is only as valuable as its ability to be restored, and in the current cyber threat climate, security is inseparable from availability. Proxmox Backup Server places a heavy emphasis on data integrity through the use of built-in, mandatory SHA-256 checksumming. Every data chunk, manifest, and index file is validated to ensure that bit rot or silent data corruption does not compromise the recovery process. This integrity verification is performed continuously, giving administrators the confidence that when a disaster does occur, the recovery path is clear and reliable. The system employs strong, client-side AES-256 encryption. Making sure that data is encrypted before it ever leaves the production host, PBS guarantees that even if a backup repository is accessed by an unauthorized entity, the data remains useless. This security-first approach is essential for meeting compliance frameworks, such as GDPR or NIS2, which require rigorous evidence of both data protection and recoverability.<br /> <br /> ==Scaling for Long-Term==<br /> As an enterprise-grade solution, Proxmox Backup Server is built to scale alongside the infrastructure it protects. Through its RESTful API, IT teams can automate the synchronization of datastores to remote, offsite locations, creating a defense against localized hardware failures or catastrophic data center outages. These remote sync jobs are equally efficient, transferring only the changes since the last synchronization, which ensures that offsite replicas remain current without saturating inter-site links. Combining local, restore capabilities with immutable or offsite secondary copies, organizations can build a layered defense that satisfies the most stringent audit requirements. Whether it is protecting a small cluster or a sprawling enterprise environment, the architecture of PBS provides the predictability and stability that many system administrators need. The transition to such a system is not just about adopting a new piece of software, but about embracing a strategy of proactive, verifiable, and lightning-fast recovery that keeps the organization resilient.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_17_2026&diff=4195 2026-07-17T01:58:44Z

<p>Tommy: Created page with &quot;=Promox Backup Server= This is an enterprise-grade, open-source backup and restoration solution designed specifically to address the challenges of protecting virtualized environments. It functions as an optimized, dedicated server application that provides a centralized repository for the secure and efficient storage of data from Proxmox Virtual Environment and other Linux-based systems. This is different from traditional, legacy backup software that relies on bulky fil...&quot;</p> <hr /> <div>=Promox Backup Server=<br /> This is an enterprise-grade, open-source backup and restoration solution designed specifically to address the challenges of protecting virtualized environments. It functions as an optimized, dedicated server application that provides a centralized repository for the secure and efficient storage of data from Proxmox Virtual Environment and other Linux-based systems. This is different from traditional, legacy backup software that relies on bulky file-level or block-level copying methods that are bandwidth-intensive and slow, PBS uses client-side deduplication technology. This means that before any data is even sent over the network, the Proxmox Backup client analyzes the data stream, breaks it into smaller, manageable chunks, and identifies redundant segments. Only transmitting and storing the data blocks that have changed since the last backup a process known as incremental-forever backup—it achieves massive space savings and significantly reduced backup window durations.<br /> <br /> The architecture of Proxmox Backup Server is built to prioritize performance and data integrity above all else. It is designed to work in harmony with the Proxmox virtualization platform, using an API-driven integration that allows for the backup of virtual machines and containers while they are running, without interrupting service. Because it operates at the block level rather than the file level, it can handle large virtual disk images with efficiency. This efficiency is bolstered by the server’s ability to perform garbage collection, a background process that systematically reclaims space by identifying and removing chunks that are no longer referenced by any backup snapshots. This ensures that the storage repository remains lean and performant over time, avoiding the pitfalls of storage bloat that plague many enterprise backup environments.<br /> <br /> ==The Datastore==<br /> The fundamental unit of organization within Proxmox Backup Server is the datastore. A datastore acts as a logical container that resides on the server’s underlying storage which can be anything from local SSDs and HDDs to network-attached storage or ZFS-based pools. Because the system is agnostic regarding the underlying storage hardware, administrators can design a storage tier that fits their specific performance and capacity requirements. When a backup job is triggered, the client—typically a Proxmox VE node communicates with the PBS instance, calculates the hash of every data chunk, and verifies whether that specific chunk already exists in the destination datastore. If it does, the redundant transmission is skipped entirely. This deduplication process is essentially the engine that drives the system’s ability to manage petabytes of data, even when the actual amount of unique information is significantly smaller.<br /> <br /> ==Security and Integrity==<br /> Proxmox Backup Server also distinguishes itself through an approach to security and data verification. Every single chunk of data is indexed and validated using SHA-256 checksums, which protects the repository against the silent threats of data corruption and bit rot. Beyond detection, the system provides integrated, client-side encryption, which is a good feature for data privacy standards. Employing AES-256 in Galois/Counter Mode, PBS ensures that the data is encrypted before it leaves the source machine and remains encrypted while at rest on the backup server. This means that even if a backup repository were physically compromised or stolen, the actual contents would remain inaccessible to unauthorized parties. The combination of these features deduplication, restoration capabilities, and encryption positions Proxmox Backup Server as an great tool for administrators tasked with maintaining high availability and verifiable data protection in a virtualized ecosystem.<br /> <br /> ==Optimizing Recovery Point Objectives==<br /> The Recovery Point Objective is primarily a function of backup frequency. In traditional environments, high-frequency backups are often avoided due to the performance impact they exert on production storage and the resulting blowup in storage costs. Proxmox Backup Server mitigates these concerns through its efficient deduplication engine. Using dynamic chunking with a rolling hash algorithm, PBS ensures that even across multiple virtual machines sharing similar operating systems or data structures, only a single instance of a repeated data block is saved. This space-efficient architecture helps IT teams to schedule backups much more aggressively. When backups are lightweight and fast, scheduling them every few minutes or hourly becomes a realistic strategy rather than a performance-prohibitive burden. This frequency directly minimizes the data loss window, effectively driving the RPO toward zero.<br /> <br /> ==Accelerating Recovery Time Objectives==<br /> RPO focuses on the freshness of the backup, the Recovery Time Objective centers on the speed of restoration. PBS facilitates rapid recovery through its integration with the Proxmox Virtual Environment. In a disaster scenario, every minute spent moving data or waiting for large volumes to rehydrate is a direct hit to business productivity. Proxmox Backup Server allows for near-instantaneous restoration by enabling administrators to mount backups directly as FUSE-based storage or perform live restores. This means that a virtual machine can be started before the entire image has been fully moved back to the production storage. Prioritizing the most critical data sectors, the system ensures that services return to an operational state while the background restoration process completes. This handoff between the backup repository and the hypervisor is what enables organizations to meet aggressive RTO requirements, even when dealing with large datasets.<br /> <br /> ==Integrity and Security==<br /> A backup is only as valuable as its ability to be restored, and in the current cyber threat climate, security is inseparable from availability. Proxmox Backup Server places a heavy emphasis on data integrity through the use of built-in, mandatory SHA-256 checksumming. Every data chunk, manifest, and index file is validated to ensure that bit rot or silent data corruption does not compromise the recovery process. This integrity verification is performed continuously, giving administrators the confidence that when a disaster does occur, the recovery path is clear and reliable. The system employs strong, client-side AES-256 encryption. Making sure that data is encrypted before it ever leaves the production host, PBS guarantees that even if a backup repository is accessed by an unauthorized entity, the data remains useless. This security-first approach is essential for meeting compliance frameworks, such as GDPR or NIS2, which require rigorous evidence of both data protection and recoverability.<br /> <br /> ==Scaling for Long-Term==<br /> As an enterprise-grade solution, Proxmox Backup Server is built to scale alongside the infrastructure it protects. Through its RESTful API, IT teams can automate the synchronization of datastores to remote, offsite locations, creating a defense against localized hardware failures or catastrophic data center outages. These remote sync jobs are equally efficient, transferring only the changes since the last synchronization, which ensures that offsite replicas remain current without saturating inter-site links. Combining local, restore capabilities with immutable or offsite secondary copies, organizations can build a layered defense that satisfies the most stringent audit requirements. Whether it is protecting a small cluster or a sprawling enterprise environment, the architecture of PBS provides the predictability and stability that many system administrators need. The transition to such a system is not just about adopting a new piece of software, but about embracing a strategy of proactive, verifiable, and lightning-fast recovery that keeps the organization resilient.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4194 2026-07-17T01:41:38Z

<p>Tommy: /* July 2026 */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> *[[Daily_Post_July_17_2026|Daily Post July 17 2026 - Promox Backup Server]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Main_Page&diff=4193 2026-07-16T06:59:02Z

<p>Tommy: </p> <hr /> <div>{{#seo:<br /> |title=FOSS導入支援のmintarc | 日本企業のデータ主権とIT自由化を支援<br /> |description=日本の中小企業に「デジタルの自由」を。Linuxサーバー、Matrix、Nextcloud、Mautic等のFOSS導入支援からITコスト削減まで。ベンダーに依存しない持続可能なIT戦略を提案する独立系コンサルティング会社です。<br /> |keywords=FOSS, OSS, オープンソース, デジタル主権, データ主権, ITコスト削減, ベンダーロックイン排除, Linux, Kubernetes, Matrix, Mautic, Listmonk, 自社運用, 日本企業, mintarc, ソブリンSME<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |type=website<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> <br /> <br /> <br /> <br /> <br /> =FOSS導入支援・ITコスト最適化ソリューショ=<br /> TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ'''] <br /> | [https://mintarc.com/minthome/index.php?title=Mintarc_partner '''概要''']<br /> <br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left; width: 100%;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 650px; border: 1px solid #ddd; padding: 20px; border-radius: 8px; background-color: #f9f9f9;&quot;&gt;<br /> <br /> === 最新スケジュールと資料公開 ===<br /> <br /> '''IT専門家に直接チャットで相談できる1時間です'''<br /> <br /> * '''次回：''' 8月10日 19:30～20:30<br /> <br /> [https://meet.jit.si/moderated/... '''Jitsiで参加する（時間になったらこちらをクリック）''']<br /> <br /> &lt;span style=&quot;font-size: 75%;&quot;&gt;※匿名での参加、お悩み相談のみも大歓迎です。&lt;/span&gt;<br /> <br /> ----<br /> <br /> '''ホワイトペーパー'''<br /> * [https://mintarc.com/minthome/images/f/f3/%E4%B8%AD%E5%B0%8F%E4%BC%81%E6%A5%AD%28SME%29%E3%81%AB%E3%81%8A%E3%81%91%E3%82%8B%E3%83%87%E3%83%BC%E3%82%BF%E4%B8%BB%E6%A8%A9.pdf '''中小企業(SME)におけるデータ主権''']<br /> <br /> ----<br /> <br /> '''導入事例'''<br /> * [[Opentextfilr導入事例|'''OpenText 社の Filrについての導入事例''']]<br /> * [https://mintarc.com/minthome/index.php?title=%E3%82%B3%E3%83%A9%E3%83%9C%E3%83%A9%E5%B0%8E%E5%85%A5%E4%BA%8B%E4%BE%8BNorthern_Irish_Health_and_Social_Care_Makes_Huge_Savings_with_Collabora_Office#Collabora_%E3%81%AE%E3%82%BD%E3%83%AA%E3%83%A5%E3%83%BC%E3%82%B7%E3%83%A7%E3%83%B3# '''北アイルランドの大手医療機関の導入事例''']<br /> * [[Tarawa_university_collabira事例|'''リール大学の導入事例''']]<br /> <br /> ----<br /> <br /> '''FAQ''' - [https://mintarc.com/minthome/index.php?title=%E3%82%88%E3%81%8F%E3%81%82%E3%82%8B%E8%B3%AA%E5%95%8F%EF%BC%88FAQ%EF%BC%89# '''よくある質問（FAQ）''']<br /> <br /> &lt;span style=&quot;font-size: 100%;&quot;&gt;※このFAQは、中小企業（SME）がOSS/FOSS/FLOSSへの移行を検討・実施する際に、最も一般的な懸念や考慮事項に対応するために作成されました。&lt;/span&gt;<br /> <br /> === FOSSに関する質問はありますか？ ===<br /> <br /> ----<br /> <br /> {{#widget:JP_Main_QA}}<br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 650px; border: 1px solid #ddd; padding: 20px; border-radius: 8px; background-color: #f9f9f9;&quot;&gt;<br /> === ソリューション・パッケージ ===<br /> [[File:FossPenguin.png|frameless|right|upright=.3|alt=Penguy|link=...]]<br /> mintarcでは、日本の中小企業の課題を解決するために、厳選されたオープンソース・ソフトウェア（FOSS）を組み合わせた「ソリューション・パッケージ」を提供しています。<br /> 高額なサブスクリプション料金に悩まされることなく、自社専用の安全なIT基盤を構築することが可能です。<br /> <br /> [https://matomo.mintarc.com/mautic/contact--jp パッケージの導入相談はこちら] <br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_パッケージ#パッケージの詳細 パッケージの詳細]&lt;/span&gt;<br /> <br /> ----<br /> <br /> === ITコストの「見える化」診断しませんか？ ===<br /> <br /> [[File:Survey.png|frameless|right|upright=.5|alt=IT Tool| link=https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)&amp;mtm_campaign=IT%20Tool%20Survey%20Lime&amp;mtm_source=Lime%20Survey#:?title=Main_Page_JA#:?title=%E3%83%A1%E3%82%A4%E3%83%B3%E3%83%9A%E3%83%BC%E3%82%B8]]<br /> <br /> 「ITコストは高いけど、どこを削ればいいかわからない」「IT部門から上がってくる請求書の内容が専門的すぎて理解できない」<br /> <br /> そんなお悩みはありませんか？<br /> <br /> 私たちは、ITコストを専門的な視点から診断し、コスト削減のヒントとIT投資の最適化をサポートします。 <br /> 詳細はこちら[https://mintarc.com/minthome/index.php?title=ITコスト診断#ITコスト診断のメリット ITコスト診断の詳細]<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ ITコスト診断]&lt;/span&gt;<br /> <br /> 「強引な営業は一切いたしません。秘密保持を遵守します。」<br /> <br /> ===FOSS導入における料金===<br /> ----<br /> *[https://mintarc.com/minthome/index.php?title=%E6%96%99%E9%87%91%E3%81%AE%E8%A9%B3%E7%B4%B0 '''mintarc クラウドホスティング料金''']<br /> *[https://mintarc.com/minthome/index.php?title=Collabora%E6%96%99%E9%87%91'''Collabora Online サービス提供内容''']<br /> &lt;/div&gt;<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;<br /> <br /> ==FOSS/OSSコンサルのmintarcとは？==<br /> mintarc合同会社は、フリー・オープン・ソース・ソフトウェア（FOSS）の導入支援と活用支援を専門とするコンサルティング会社です。 私たちは、企業がFOSSを効果的に利用し、データ管理とセキュリティを向上させ、特定のベンダーに縛られることなく自由にシステムを選べるよう支援しています。<br /> <br /> <br /> お客様のニーズに合わせ、FOSS導入を全面的にサポートします。 まず、現在のシステムを詳しく分析し、最適なFOSSソリューションをご提案します。 そして、スムーズな導入計画を立て、実行までしっかりサポートします。<br /> <br /> 信頼性が高く柔軟性のあるITインフラを、FOSSを使って構築することも得意としています。 企業の成長に合わせてシステムを拡張でき、パフォーマンスも考慮します。 お客様はご自身のデータを完全に管理でき、ビジネスに役立つデータを有効活用できるようにサポートします。<br /> <br /> セキュリティ対策も重視しています。 FOSSの特性を活かし、お客様のデータとシステムを最新の脅威から守ります。 また、特定のベンダーに依存しない、オープンで柔軟なシステム環境を構築することで、ベンダーロックインを解消します。<br /> <br /> お客様のニーズに合わせたFOSSのカスタマイズと最適化も行います。 業務効率を改善し、企業の競争力向上に貢献します。<br /> <br /> <br /> <br /> さらに、社内のIT担当者やエンドユーザー向けに、FOSSの使い方や管理方法に関する研修も行っています。 企業全体のFOSS活用能力を高め、長期的な成功を支援します。<br /> <br /> FOSS導入後も、システムの運用やトラブルシューティング、アップデートなどの継続的なサポートを提供します。 お客様との長期的なパートナーシップを大切にし、FOSSを活用したビジネスの成長を継続的に支援します。<br /> <br /> FOSSの導入や活用でお困りの企業様、ベンダーロックインから脱却したい企業様、データの管理とセキュリティを強化したい企業様は、ぜひ一度お問い合わせください。 お客様のビジネスニーズに最適なFOSSソリューションをご提案し、導入から活用までサポートいたします。 mintarcと一緒に、FOSSを活用して、より自由で安全、そして効率的なITインフラを実現しましょう。<br /> <br /> <br /> <br /> ITのことでお困りのことがありましたらぜひ[https://matomo.mintarc.com/mautic/contact--jp お問い合わせ]<br /> ください<br /> <br /> <br /> &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt;<br /> <br /> ==FOSS/OSS導入までの流れ==<br /> [[File:導入プロセス.png|frameless|center|upright=3|alt=Process Flow for a Transition|link=https://mintarc.com/minthome/images/b/b0/ウェブサイト用.png|Flow for a Transition]]<br /> <br /> <br /> {| class=&quot;wikitable&quot; style=&quot;width: 100%; border-collapse: collapse; font-family: Arial, sans-serif; font-size: 14px; text-align: center; background-color: #f9f9f9; border: 1px solid #ddd;&quot;<br /> |-<br /> ! style=&quot;background-color: #3eb489;width: 33%; color: white; padding: 10px; border: 1px solid #ddd;&quot; | FOSSコンサルティングと戦略策定：クラウドおよびオンプレミス環境への導入、ソリューションのカスタマイズ<br /> ! style=&quot;background-color: #3eb489;width: 33%; color: white; padding: 10px; border: 1px solid #ddd;&quot; | クラウド &amp; オンプレミス導入、ソリューションのカスタマイズ<br /> ! style=&quot;background-color: #3eb489;width: 33%;color: white; padding: 10px; border: 1px solid #ddd;&quot; | トレーニングとサポートでビジネスの成長を加速<br /> |-<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | 現在の IT インフラの状況把握と分析<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | mintarc Cloud または Akamai などのクラウドプロバイダーを選択し、オープンソースソリューションを導入<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | チームを FOSS の効果的な活用と管理に必要なスキルで強化する<br /> |-<br /> | style=&quot;padding: 8px; border: 1px solid #ddd; background-color:#f2f2f2;&quot; | 導入する FOSS ソリューションの選定 <br /> | style=&quot;padding: 8px; border: 1px solid #ddd; background-color:#f2f2f2;&quot; | 最大限のコントロールを実現するために、ハイブリッドシステムまたは完全なオンプレミスシステムを設計する<br /> | style=&quot;padding: 8px; border: 1px solid #ddd; background-color:#f2f2f2;&quot; | 運用・保守・更新を継続的にサポート<br /> |-<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | 統合ロードマップを策定する<br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | <br /> | style=&quot;padding: 8px; border: 1px solid #ddd;&quot; | <br /> |}<br /> <br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=FOSS導入のステップ# &amp;nbsp;&amp;nbsp;&amp;nbsp;FOSS導入の詳細]&lt;/span&gt;<br /> <br /> ==FOSSとは？==<br /> <br /> オープンであることによって、イノベーションを解き放つ<br /> <br /> オープンなコラボレーション、透明性、そしてイノベーションを何よりも大切に考えています。お客様のビジネスを次のレベルに引き上げるために、IT インフラの合理化、クラウドソリューションの活用、そしてフリー・オープンソースソフトウェア (FOSS) の利点を最大限に活用するお手伝いをいたします。<br /> <br /> FOSSとは、<br /> <br /> ・自由な利用: 使用料や利用制限がありません。<br /> <br /> ・オープンなコラボレーション: ソースコードは公に入手可能で、検査、変更、配布が可能です。<br /> <br /> ・コミュニティ主導: 透明性とイノベーションを優先するグローバルな貢献者コミュニティによって開発されています。<br /> <br /> FOSSを利用することで、企業はコスト削減、ピアレビューされたコードによるセキュリティ向上、そしてテクノロジースタックの管理強化を実現できます。<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=FOSSについての説明# &amp;nbsp;&amp;nbsp;&amp;nbsp;FOSSについての詳細]&lt;/span&gt;<br /> <br /> ==フリー・オープンソース・ソフトウェア（FOSS/OSS/FLOSS)を選択する理由==<br /> オープンソースソフトウェア（FOSS）は、今のITインフラを支える上で欠かせない存在となっています。例えば、LinuxというオープンソースのOSは、世界中のサーバーの大部分を占めており、ウェブサービスやクラウドプラットフォームの基盤として機能しています。また、KubernetesやOpenStackといったプロジェクトも、クラウドコンピューティング分野において重要な役割を果たしています。<br /> <br /> FOSSの導入のメリット<br /> <br /> '''・コスト効率:''' 従来のソフトウェアライセンスにかかる高額な費用を削減できます。<br /> <br /> '''・柔軟性:''' 自社のビジネスニーズに合わせてソフトウェアを自由にカスタマイズできます。<br /> <br /> '''・セキュリティ:''' 多くの開発者によるレビューを受けることで、ソフトウェアの信頼性が向上します。<br /> <br /> '''・拡張性:''' ライセンス制限を気にすることなく、事業規模に合わせてシステムを拡張できます。<br /> <br /> '''・コミュニティサポート: '''世界中の開発者やユーザーからなる活発なコミュニティに参加できます。<br /> <br /> FOSSの導入は、単なるソフトウェアの導入にとどまらず、イノベーションとコラボレーションを重視する考え方を企業にもたらします。<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=FOSSのメリットについての詳細# &amp;nbsp;&amp;nbsp;&amp;nbsp;FOSSのメリットについての詳細]&lt;/span&gt;<br /> <br /> ==Collabora Online パートナーシップ==<br /> [[File:Collabora-logo.png|frameless|right|upright=0.3|alt=Collabora Online|link=https://www.collaboraonline.com/]]<br /> この度、私たちmintarcはCollabora Onlineの公式パートナーとして、お客様にその優れた機能を提供できることを大変嬉しく思います。Collabora Onlineとのパートナーシップは、文書編集とコラボレーションを革新するこのツールをお客様に自信を持って推奨し、積極的に普及させていくという、私たちの強い決意を示すものです。<br /> <br /> 柔軟なオープンソースソリューションを求めるお客様に、これまで以上の価値を提供するため、私たちはこのパートナーシップを最大限に活用してまいります。<br /> <br /> サポート、[https://mintarc.com/minthome/index.php?title=Collabora料金 料金]<br /> についてはこちらをご覧ください。また、[https://mintarc.com/minthome/index.php?title=Collabora_FAQ_JP FAQ]もご用意しておりますので、ぜひご活用ください。<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=CollaboraJP# &amp;nbsp;&amp;nbsp;&amp;nbsp;Collabora Onlineパートナーについての詳細]&lt;/span&gt;<br /> <br /> ==セキュリティ・コンサルティング(CS2)パートナシップ==<br /> [[File:Cs2-logo4.png|frameless|right|upright=0.3|alt=CS2|link=https://www.cybers2.com/]]<br /> この度、当社はCybers2との提携を締結いたしました。<br /> <br /> これにより、私たちは、高まるセキュリティリスクと多様化するビジネスニーズに対応するため、信頼と透明性を基盤とし、将来を見据えたITソリューションを日本の中小企業（SME）へお届けする決意を、改めて明確にいたします。<br /> <br /> 専門知識と丁寧なサポートをもって、貴社のIT回復力（レジリエンス）の強化やオープンソースの活用を全面的に支援いたします。カスタムメイドのコンサルティングとサポートをご希望の企業様は、どうぞお気軽にお問い合わせください。<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Cs2パートナー Cs2パートナーシップの詳細]&lt;/span&gt;<br /> <br /> ==PeppermintOSへのオープンソース貢献：私たちの情熱の証==<br /> <br /> [[File:PepperMintOS_screenshot.png|frameless|right|upright=1.5|alt=Peppermint OS Screenshot| PeppermintOS Screenshot]]<br /> 私たちは、軽量LinuxディストリビューションであるPeppermintOSの開発を支援しています。PeppermintOSは、高速性とシンプルさを追求して設計されており、オープンソースの理念に基づいて構築されています。この取り組みは、私たちがユーザーにとって使いやすいテクノロジーを提供することに尽力していることの証です。<br /> <br /> PeppermintOSの特長：<br /> <br /> *動作速度に優れた軽量設計<br /> *ウェブアプリやクラウドサービスとの連携<br /> *ユーザーの好みに合わせてカスタマイズ可能なインターフェース<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://peppermintos.com/&amp;nbsp;&amp;nbsp;&amp;nbsp;?title=PeppermintOSの詳細# &amp;nbsp;&amp;nbsp;&amp;nbsp;PeppermintOSの詳細]&lt;/span&gt;<br /> <br /> ==料金==<br /> <br /> '''ライセンス費用を削減し、総所有コストを削減し、そしてお客様のニーズに合わせたオープンソースソリューションで自由を手に入れましょう。'''<br /> <br /> 私たちは、企業が FOSS (フリー・オープンソースソフトウェア) の可能性を最大限に引き出すお手伝いを専門としています。当社の価格設定は、FOSS が組織にもたらす柔軟性、透明性、そして長期的な価値を反映しています。<br /> <br /> *ライセンス費用不要: 高額な SaaS ソフトウェアライセンスが不要になります。<br /> *コスト効率: 事業規模に合わせて総所有コストを削減できます。<br /> *自由とカスタマイズ: ベンダーロックインを回避し、お客様独自のニーズに合わせてソリューションをカスタマイズできます。<br /> *日本語サポート: 専門家による日本語サポートで、言語の壁を克服できます。<br /> <br /> FOSS は、中小企業が競争力を強化し、業務を効率化する機会を提供します。コスト削減を目指している場合でも、イノベーションを推進したい場合でも、当社がお客様をあらゆる段階でご案内します。<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=料金の詳細 &amp;nbsp;&amp;nbsp;&amp;nbsp;料金の詳細]&lt;/span&gt;<br /> <br /> ==中小企業のためのシンプルFOSS移行ガイド==<br /> <br /> 多くの中小企業（SME）は、コスト削減、事業運営の管理強化、そしてセキュリティ向上を目的として、オープンソースソリューションへの移行を検討しています。この動きは、競争が激しく、リソースが限られた環境におけるデジタルトランスフォーメーションの必要性の高まりによって加速されています。しかし、FOSSの導入には多くの側面があり、機会と課題の両方が存在します。<br /> <br /> FOSSソリューションは、プロプライエタリソフトウェアに関連するライセンス費用を不要にすることで、中小企業に大きなコスト上の優位性をもたらします。これにより、企業はリソースを他の重要な事業分野に割り当てることができます。例えば、ウェブサイト管理ツールのJoomla、通信システムのAsterisk、そして顧客関係管理システムのSuiteCRMといったツールを利用することで、中小企業は高コストをかけずに業務を効率化できます。さらに、FOSSは柔軟性とカスタマイズ性を提供し、企業はソフトウェアをそれぞれのニーズに合わせて調整することができます。この適応力は、特別な要件を持つ、または予算が限られている中小企業にとって特に価値があります。<br /> <br /> これらの利点がある一方で、オープンソースソリューションへの移行には課題も伴います。大きなハードルの一つは、実装と保守の複雑さです。FOSSは初期費用を削減できるものの、カスタマイズ、統合、そして継続的なサポートには技術的な専門知識が必要となる場合があります。多くの中小企業は、オープンソース技術の管理を専門とするサードパーティプロバイダーと提携することで、この課題に対応しています。これらのプロバイダーは、ダウンタイムを最小限に抑え、拡張性を確保し、アップデートを効率的に処理するのに役立ちます。<br /> <br /> &lt;span class=&quot;custom-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=シンプルガイドの詳細# &amp;nbsp;&amp;nbsp;&amp;nbsp;シンプルガイドの詳細]&lt;/span&gt;</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_Post_July_16_2026&diff=4192 2026-07-16T01:57:19Z

<p>Tommy: Created page with &quot;{{#seo: |title= Using Virtual Networks: Linux Bridges, Bonds, and VLANs in Proxmox |description= A deep dive into Proxmox VE networking, exploring how Linux bridges, network bonds, and VLANs work together to create resilient, segmented, and high-performance virtualized environments. |keywords= Proxmox Networking, Linux Bridge, Network Bonding, VLANs, Proxmox VE, Virtualization Networking, LACP, 802.1Q, Network Segmentation, High Availability |site_name= mintarc |locale=...&quot;</p> <hr /> <div>{{#seo:<br /> |title= Using Virtual Networks: Linux Bridges, Bonds, and VLANs in Proxmox<br /> |description= A deep dive into Proxmox VE networking, exploring how Linux bridges, network bonds, and VLANs work together to create resilient, segmented, and high-performance virtualized environments.<br /> |keywords= Proxmox Networking, Linux Bridge, Network Bonding, VLANs, Proxmox VE, Virtualization Networking, LACP, 802.1Q, Network Segmentation, High Availability<br /> |site_name= mintarc<br /> |locale= en_US<br /> |type= article<br /> |canonical= https://mintarc.com/minthome/index.php?title=Daily_Post_July_16_2026<br /> }}<br /> &lt;div class=&quot;noexcerpt&quot;&gt;<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email Us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' <br /> | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc'''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts'''Daily Posts''']<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> |-<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mediawiki/index.php?title=Main_Page &amp;nbsp;&amp;nbsp;Mintarc Forge]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact-en &amp;nbsp;&amp;nbsp;Contact Us]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/english-news-letter &amp;nbsp;&amp;nbsp;News Letter]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Blog_English &amp;nbsp;&amp;nbsp;Blog]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc:About#Business_Partnerships &amp;nbsp;&amp;nbsp;Partners]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Collaboration'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> &lt;/div&gt;<br /> =Linux Bridges, Bonds, and VLANs in Proxmox=<br /> Proxmox VE relies on a flexible, software-defined networking stack built upon the capabilities of the Linux kernel. To manage virtualization, Proxmox changes the physical network interfaces of a host machine into virtual entities. Understanding how to orchestrate these components specifically bridges, bonds, and VLANs is needed for building scalable, high-performance, and secure virtualized environments. The Proxmox network configuration exists as a bridge between the physical world of cables and switches and the virtual world of guest instances, providing an abstraction layer that allows virtual machines and containers to communicate as if they were physically connected to the network fabric.<br /> <br /> ==Linux Bridges in Proxmox==<br /> The Linux bridge is the building block of Proxmox networking. Functionally similar to a physical network switch, the bridge acts as a virtual layer-2 device that connects multiple network interfaces, whether physical or virtual, into a single segment. When a virtual machine is deployed in Proxmox, its virtual network interface card (vNIC) is typically attached to a bridge, such as the standard vmbr0. The bridge then forwards Ethernet frames between the VM and the physical uplink, or between other VMs sharing the same bridge, based on MAC address learning. This design enables Proxmox to provide VMs with direct network access, allowing them to participate in the local network with their own IP addresses, effectively making them first-class citizens in the data center infrastructure. The bridge interface itself can optionally hold an IP address for management traffic, though in high-security setups, it is often kept transparent to prevent unauthorized layer-3 access to the host management interface.<br /> <br /> ==Reliability with Network Bonding==<br /> The bridge provides connectivity, it represents a single point of failure if the underlying physical link goes down. To mitigate this, Proxmox used Linux network bonding, which allows for the aggregation of multiple physical network interfaces into a single, logical bonded interface. This process is important for achieving high availability and increased throughput. Combining several physical ports, administrators can configure various bonding modes, such as Active-Backup, which provides immediate failover if a primary cable is disconnected, or Link Aggregation (LACP/802.3ad), which provides both redundancy and load balancing by distributing traffic across all active links. When this bonded interface is then assigned as the physical port for a Linux bridge, the entire virtual network stack gains the resilience of the bond, ensuring that virtual machines remain connected to the outside world even in the event of a cable or switch port failure.<br /> <br /> ==Segmenting Traffic with VLANs==<br /> VLANs, or Virtual Local Area Networks, allow for the logical segmentation of network traffic at the data link layer, even when all devices are physically connected to the same infrastructure. In Proxmox, VLAN tagging provides a mechanism for network isolation, security, and traffic management. Applying 802.1Q tags to network frames, Proxmox can ensure that traffic from one set of virtual machines is completely isolated from another, even if they share the same physical hardware and underlying bridge. This is particularly important in multi-tenant environments where security boundaries must be strictly enforced. Proxmox simplifies this by allowing administrators to configure VLAN-aware bridges. When a bridge is set to VLAN-aware mode, it can interpret VLAN tags on incoming frames from the physical network and properly route them to the correct virtual interface assigned to that specific VLAN ID, or conversely, tag traffic exiting from a VM before it reaches the physical switch.<br /> <br /> ==Integrating Bridges, Bonds, and VLANs==<br /> Proxmox networking is realized when these three technologies are combined into a architecture. A typical enterprise-grade configuration often starts with a bond of two or more physical interfaces to ensure redundancy. This bonded interface is then utilized as the port for a VLAN-aware bridge. Within this setup, individual virtual machines can be assigned specific VLAN tags in their network configuration. This allows the physical network infrastructure to remain relatively simple while the Proxmox host handles complex logical traffic segmentation. For instance, a single host might support internal management traffic on a native untagged VLAN, and simultaneously hosting production web servers on VLAN 10 and database servers on a restricted VLAN 20. Because the bridge is VLAN-aware, the physical switch simply sees an 802.1Q trunk port, and the Proxmox host manages the distribution of this traffic to the appropriate guest virtual machines.<br /> <br /> ==Best Practices==<br /> Performance optimization in Proxmox networking requires a balance between logical complexity and hardware capabilities. When implementing these virtual structures, it is important to consider the overhead introduced by software-based switching, particularly at high throughputs. Offloading features such as checksum offloading and hardware-level VLAN filtering on network interface cards can significantly reduce CPU utilization on the Proxmox host. Administrators should ensure that the underlying physical switch ports are correctly configured to match the Proxmox settings. For instance, if using LACP, the switch must be explicitly configured for an 802.3ad port channel. If using VLANs, the switch port must be set as a trunk port to pass the tagged traffic. Failure to align the virtual configuration with the physical switch settings is a frequent cause of intermittent connectivity issues, packet loss, or total network isolation for virtual guests.<br /> <br /> ==Security Considerations==<br /> Security within a virtualized network environment requires moving past traditional perimeter defenses. Because bridges and virtual switches can facilitate inter-VM communication that never leaves the physical host, standard firewall rules at the edge of the network may not see this lateral traffic. Proxmox addresses this by integrating with the Linux kernel's ebtables and nftables frameworks, allowing for the implementation of fine-grained firewall rules at the virtual interface level. Applying these rules, administrators can prevent spoofing, restrict inter-VM communication, and enforce strict traffic policies before data ever leaves the virtual environment. Leveraging VLANs for micro-segmentation further helps this security posture, as it creates hard boundaries between different classes of services or applications, ensuring that even if one VM is compromised, the blast radius is limited to the isolated VLAN segment.<br /> <br /> ==Future-Proofing Proxmox Network Configurations==<br /> As infrastructure requirements evolve, the ability to reconfigure network topologies without physical intervention becomes increasingly valuable. The software-defined nature of Proxmox networking allows for dynamic scaling and adaptation. Administrators can migrate virtual machines across different hosts in a cluster, and because the networking configuration including bridges, bonds, and VLAN assignments is abstracted, the virtual machine maintains its connectivity profile regardless of the underlying physical host. This mobility is a nature of virtualization, enabling maintenance, load balancing, and high-availability clustering. As SDN technologies continue to mature, the integration of these features within Proxmox will likely become even more streamlined, with better automation and improved visibility into the flows of traffic.</div>

Tommy https://mintarc.com/minthome/index.php?title=Daily_posts&diff=4191 2026-07-16T01:41:17Z

<p>Tommy: /* English */</p> <hr /> <div>{{#seo:<br /> |title=mintarc Daily Posts一覧｜日々のSNS・ブログ投稿アーカイブ<br /> |description=このページはmintarcのDaily Posts（デイリーポスト）アーカイブです。Mineによる日々のSNS投稿やブログ記事をまとめて掲載。最新のIT動向、FOSS・オープンソース情報、社内ニュース、コラボレーションやパートナー情報も随時更新しています。<br /> |keywords=mintarc, FOSS導入支援, オープンソース, Digital Sovereignty, Sovereign IT, ITコスト削減, 自社運用, Self-Hosting, Nextcloud, Collabora, Matrix, インフラ構築, デイリーブログ, ITコンサルティング, 町田市 IT, 脱ベンダーロックイン<br /> |image=https://mintarc.com/minthome/images/thumb/2/2e/Logo_with_name.png/150px-Logo_with_name.png<br /> |image_alt=mintarc logo with name<br /> |type=blog<br /> |site_name=mintarc<br /> |locale=ja_JP<br /> }}<br /> [[File:Logo_with_name.png|frameless|left|upright=.5|link=https://mintarc.com/minthome/index.php?title=Main_Page|alt=Mintarc]]<br /> {| border=&quot;0&quot; style=&quot;margin: auto; text-align: center; width: 70%;&quot;<br /> | &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/lime/index.php?r=survey/index&amp;sid=321546&amp;lang=japhp?title=FOSS_and_OSS_Tools_(JA)#:?title=Main_Page_JA#:?title=メインページ &amp;nbsp;&amp;nbsp;ITコスト診断]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://matomo.mintarc.com/mautic/contact--jp &amp;nbsp;&amp;nbsp;お問い合わせ]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/Widget:Weekly_Bundle_Subscribe &amp;nbsp;&amp;nbsp;メルマガ登録]&lt;/span&gt; <br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=ブログ#: &amp;nbsp;&amp;nbsp;ブログ]&lt;/span&gt;<br /> || &lt;span class=&quot;static-button&quot;&gt;[https://mintarc.com/minthome/index.php?title=Mintarc_partner &amp;nbsp;&amp;nbsp; パートナー]&lt;/span&gt;<br /> |-<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Cost Assessment'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Questions?'<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Weekly Letter'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Monthly Blog'''<br /> | style=&quot;width: 1%; word-wrap: break-word; white-space: normal;&quot; | '''Our Partners'''<br /> |}<br /> [mailto:&amp;#113;&amp;#117;&amp;#101;&amp;#115;&amp;#116;&amp;#105;&amp;#111;&amp;#110;&amp;#115;&amp;#64;&amp;#109;&amp;#105;&amp;#110;&amp;#116;&amp;#97;&amp;#114;&amp;#99;&amp;#46;&amp;#99;&amp;#111;&amp;#109; '''Email us''']<br /> |TEL:''' &amp;#48;&amp;#53;&amp;#48;-&amp;#49;&amp;#55;&amp;#50;&amp;#48;-&amp;#48;&amp;#54;&amp;#52;&amp;#49;''' | [https://www.linkedin.com/company/mintarc/about/?viewAsMember=true|MintArc '''LinkedIn''']<br /> | [https://mintarc.com/minthome/index.php?title=Welcome_to_mintarc '''English''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts '''日々のブログ''']<br /> | [https://mintarc.com/minthome/index.php?title=Daily_posts#Answers_to_Questions '''Q &amp; A''']<br /> &lt;/div&gt;<br /> <br /> =Mine's Daily Postings=<br /> &lt;div style=&quot;display: flex; flex-wrap: wrap; justify-content: center; gap: 20px; text-align: left;&quot;&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==日本語の投稿==<br /> ===2026年7月===<br /> *[[Daily_Post_July_02_2026JP|Debianサーバーの堅牢化（ハーデニング）：継続的なセキュリティの実践 7/02/2026]]<br /> *[[Daily_Post_July_13_2026JP|Proxmox VEのインストールと初期堅牢化（ハーデニング）のベストプラクティス7/13/2026]]<br /> *[[Daily_Post_July_15_2026JP|ZFS、Ceph、ローカルストレージ：Proxmox VEのストレージアーキテクチャ最適解 7/15/2026]]<br /> ===2026年6月===<br /> *[[Daily_Post_June_01_2026JP|タイポグラフィの完全な支配権をその手に：オープンソースのフォントエディタ「FontForge」 6/01/2026]]<br /> *[[Daily_Post_June_02_2026JP|妥協なき自由と安定性の礎：究極のオープンソースOS「Debian」 6/02/2026]]<br /> *[[Daily_Post_June_04_2026JP|自由なコミュニケーション基盤を自前で構築する：FreePBXの魅力と活用法 6/04/2026]]<br /> *[[Daily_Post_June_05_2026JP|レガシーシステムからの脱却：日本の中小企業のためのFOSS移行戦略 6/05/2026]]<br /> *[[Daily_Post_June_11_2026JP|仮想化とコンテナの理想的な融合：真のオープンソースインフラ基盤「Incus」 6/11/2026]]<br /> *[[Daily_Post_June_12_2026JP|SaaSの罠に溺れる日本企業：FOSSによる真の自律と主権の回復 6/12/2026]]<br /> *[[Daily_Post_June_16_2026JP|ログ解析型セキュリティツールの最前線：SSHGuardとCrowdSecの比較と実践的活用 6/16/2026]]<br /> *[[Daily_Post_June_22_2026JP|データのコントロール権を取り戻す：Nextcloudが実現する真のデジタル主権 6/22/2026]]<br /> *[[Daily_Post_June_30_2026JP|マーケティングの自由を取り戻す：Mauticがもたらす変革 6/30/2026]]<br /> <br /> ===2026年5月===<br /> *[[Daily_Post_May_07_2026JP|顧客対応を自分たちの手に：オープンソースのヘルプデスク FreeScout の実力 5/07/2026]]<br /> *[[Daily_Post_May_08_2026JP|システムの健康状態を可視化し堅牢化を支える：セキュリティ監査ツール Lynis の全貌 5/08/2026]]<br /> *[[Daily_Post_May_27_2026JP|便利さという幻想：SaaS導入に潜む罠と、私たちが本当に選ぶべき道 5/27/2026]]<br /> <br /> ===2026年4月===<br /> *[[Daily_Post_Apr_15_2026JP|Nextcloud Talk：自分たちで「鍵」を握る、究極のプライベート・チャット 4/15/2026]]<br /> *[[Daily_Post_Apr_24_2026JP|ビジネス・セキュリティ視点：SMEの盲点「ブラウザ選び」が企業の命運を分ける理由 4/24/2026]]<br /> *[[Daily_Post_Apr_27_2026JP|自社専用の熱狂的なコミュニティを構築する：次世代プラットフォーム Forem の全貌 4/27/2026]]<br /> *[[Daily_Post_Apr_30_2026JP|ブラウザに潜む追跡者を賢くブロック：Privacy Badgerが守るオンラインのプライバシー 4/30/2026]]<br /> <br /> ===2026年1月===<br /> *[[Daily_Post_Jan_5_2026JP|スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026]]<br /> *[[Daily_Post_Jan_6_2026JP|ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026]]<br /> *[[Daily_Post_Jan_7_2026JP|失敗しないためのオープンソース・ライセンス基礎知識　1/7/2026]]<br /> <br /> ==2025==<br /> ===12月の投稿===<br /> *[[Daily_Post_dec_1_2025JP|KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025]]<br /> *[[Daily_Post_dec_2_2025JP|Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025]]<br /> *[[Daily_Post_dec_4_2025JP|KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025]]<br /> *[[Daily_Post_dec_5_2025JP|Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025]]<br /> <br /> ===11月の投稿===<br /> *[[Daily_Post_nov_4_2025JP|日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025]]<br /> *[[Daily_Post_nov_6_2025JP|日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025]]<br /> *[[Daily_Post_nov_10_2025JP|Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025]]<br /> <br /> ===10月の投稿===<br /> *[[Daily_Post_oct_2_2025JP|オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025]]<br /> *[[Daily_Post_oct_3_2025JP|プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025]]<br /> *[[Daily_Post_oct_4_2025JP|Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025]]<br /> *[[Daily_Post_oct_5_2025JP|Papra: 軽量で安全なデジタル・アーカイブ10/5/2025]]<br /> <br /> ===9月の投稿===<br /> *[[Daily_Post_Sep_1_2025JP|pyinfra: Pythonでインフラを自動化するツール 9/1/2025]]<br /> *[[Daily_Post_Sep_5_2025JP|Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025]]<br /> *[[Daily_Post_Sep_7_2025JP|Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025]]<br /> <br /> ===8月の投稿===<br /> *[[Daily_Post_Aug_1_2025JP|Gmailからの卒業：Mail-in-a-Boxで自分だけのメールサーバーを構築し　8/1/2025]]<br /> *[[Daily_Post_Aug_3_2025JP|Gophish: 企業をフィッシング詐欺から守る、無料で使える最強ツール8/3/2025]]<br /> <br /> ===7月の投稿===<br /> *[[Daily_Post_Jul_1_2025JP|YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025]]<br /> *[[Daily_Post_Jul_3_2025JP|Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025]]<br /> *[[Daily_Post_Jul_9_2025JP|Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025]]<br /> *[[Daily_Post_Jul_12_2025JP|Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025]]<br /> *[[Daily_Post_Jul_13_2025JP|OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025]]<br /> *[[Daily_Post_Jul_14_2025JP|NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025]]<br /> <br /> ===6月の投稿===<br /> *[[Daily_Post_Jun_10_2025JP|MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025]]<br /> *[[Daily_Post_Jun_11_2025JP|XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025]]<br /> *[[Daily_Post_Jun_12_2025JP|Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025]]<br /> *[[Daily_Post_Jun_13_2025JP|Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025]]<br /> *[[Daily_Post_Jun_14_2025JP|OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025]]<br /> *[[Daily_Post_Jun_15_2025JP|mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025]]<br /> *[[Daily_Post_Jun_16_2025JP|Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025]]<br /> *[[Daily_Post_Jun_17_2025JP|Wazuh：セキュリティを強くするオープンソースの力6/17/2025]]<br /> <br /> ===5月の投稿===<br /> *[[Daily_Post_May_7_2025JP|Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025]]<br /> *[[Daily_Post_May_12_2025JP|プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025]]<br /> *[[Daily_Post_May_14_2025JP|中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025]]<br /> *[[Daily_Post_May_20_2025JP|AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025]]<br /> *[[Daily_Post_May_27_2025JP|Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025]]<br /> *[[Daily_Post_May_29_2025JP|スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025]]<br /> <br /> ===4月の投稿===<br /> * [[Daily_Post_Apr_01_2025JP|日々の投稿 Post apr 01 2025]]<br /> *[[Daily_Post_Apr_02_2025JP|日々の投稿 Post apr 02 2025]]<br /> *[[Daily_Post_Apr_09_2025JP|中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025]]<br /> *[[Daily_Post_Apr_14_2025JP|日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025]]<br /> *[[Daily_Post_Apr_15_2025JP|SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025]]<br /> *[[Daily_Post_Apr_16_2025JP|Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025]]<br /> *[[Daily_Post_Apr_22_2025JP|社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025]]<br /> *[[Daily_Post_Apr_23_2025JP|顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025]]<br /> *[[Daily_Post_Apr_30_2025JP|Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025]]<br /> <br /> ===3月の投稿===<br /> * [[Daily_Post_Mar_05_2025JP|日々の投稿 Post Mar 05 2025]]<br /> * [[Daily_Post_Mar_010_2025JP|日々の投稿 Post Mar 10 2025]]<br /> * [[Daily_Post_Mar_019_2025JP|日々の投稿 Post Mar 19 2025]]<br /> <br /> ==Answers to Questions==<br /> A place for answers to questions we get about the things we post<br /> ===What is the main difference between FOSS, FLOSS, and OSS===<br /> We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom (&quot;free as in speech&quot;). FLOSS adds &quot;Libre&quot; to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.<br /> <br /> ===What are the risks of staying with &quot;Big Tech&quot; SaaS solutions?===<br /> This is always a &quot;Prove it to me&quot; questions LOL - Basically the risks include &quot;SaaS Creep&quot; (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.<br /> <br /> ===What is OWASP ZAP and why should a business use it===<br /> Its is an open-source web security tool. It acts as a &quot;manipulator-in-the-middle&quot; to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.<br /> <br /> ===What is &quot;Shadow IT&quot; and how does FOSS mitigate it?===<br /> This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.<br /> <br /> ===My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?===<br /> <br /> ====The Business Risks You Are &quot;Ignoring&quot;====<br /> Even when things are running perfectly, relying on a single proprietary provider creates &quot;silent risks&quot; that don't matter... until they suddenly do.<br /> *The &quot;Price Creep&quot; when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the &quot;cost of switching&quot; becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.<br /> <br /> *Data Sovereignty &amp; Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.<br /> <br /> *The &quot;Feature Sunset&quot;, Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.<br /> <br /> ====Is anti-Google Technical or Ideological?====<br /> *FOSS advocates see Google as a &quot;centralized authority&quot; that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are &quot;digital tenants&quot; rather than &quot;digital owners.&quot;<br /> <br /> *FOSS companies argue that Google’s code is a &quot;black box.&quot; You can’t audit it for security flaws or &quot;backdoors&quot; yourself; you have to take Google's word for it. Many of us FOSS folk believe &quot;given enough eyes, all bugs are shallow&quot; meaning open code is inherently more secure because it can be audited by anyone.<br /> <br /> ====You don't need to quit Google to benefit from Open Source. a &quot;Hybrid Approach&quot;====<br /> *Stay on Google Workspace for email and docs because the collaboration is your preference.<br /> *Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.<br /> *Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.<br /> <br /> &lt;/div&gt;<br /> &lt;div style=&quot;flex: 1; min-width: 320px; max-width: 550px; border: 1px solid #ddd; padding: 15px; border-radius: 8px;&quot;&gt;<br /> <br /> ==English==<br /> ===July 2026===<br /> *[[Daily_Post_July_06_2026|Daily Post July 06 2026 - MSP vs. FOSS Consultancy]]<br /> *[[Daily_Post_July_07_2026|Daily Post July 07 2026 - Addressing Common FOSS Hesitations]]<br /> *[[Daily_Post_July_09_2026|Daily Post July 09 2026 - Vendor Independence as a Business Strategy ]]<br /> *[[Daily_Post_July_10_2026|Daily Post July 10 2026 - Hypervisors vs. Containers Choosing the Right Tool for the Job]]<br /> *[[Daily_Post_July_13_2026|Daily Post July 13 2026 - Proxmox VE Installation &amp; Initial Hardening Best Practices]]<br /> *[[Daily_Post_July_14_2026|Daily Post July 14 2026 - ZFS, Ceph, and Local Storage]]<br /> *[[Daily_Post_July_16_2026|Daily Post July 16 2026 - Linux Bridges, Bonds, and VLANs in Proxmox]]<br /> <br /> ===June 2026 ===<br /> *[[Daily_Post_June_01_2026|Daily Post June 01 2026 - FontForge]]<br /> *[[Daily_Post_June_02_2026|Daily Post June 02 2026 - Debian]]<br /> *[[Daily_Post_June_03_2026|Daily Post June 03 2026 - Devuan]]<br /> *[[Daily_Post_June_04_2026|Daily Post June 04 2026 - Big Tech Telemetry]]<br /> *[[Daily_Post_June_05_2026|Daily Post June 05 2026 - Legacy Migrations]]<br /> *[[Daily_Post_June_08_2026|Daily Post June 08 2026 - Forgejo]]<br /> *[[Daily_Post_June_09_2026|Daily Post June 09 2026 - Incus]]<br /> *[[Daily_Post_June_10_2026|Daily Post June 10 2026 - Nginx]]<br /> *[[Daily_Post_June_11_2026|Daily Post June 11 2026 - Drowning in the SaaS Trap]]<br /> *[[Daily_Post_June_12_2026|Daily Post June 12 2026 - Building Custom Live ISOs]]<br /> *[[Daily_Post_June_15_2026|Daily Post June 15 2026 - &quot;Self-Reliant&quot; vs &quot;Autonomous&quot;Philosophy]]<br /> *[[Daily_Post_June_16_2026|Daily Post June 16 2026 - SSHGuard and CrowdSec]]<br /> *[[Daily_Post_June_17_2026|Daily Post June 17 2026 - Nextcloud for Data Control]]<br /> *[[Daily_Post_June_18_2026|Daily Post June 18 2026 - Hidden Architecture of the Free Tier]]<br /> *[[Daily_Post_June_19_2026|Daily Post June 19 2026 - OID]]<br /> *[[Daily_Post_June_22_2026|Daily Post June 22 2026 - Data Ownership in the Cloud]]<br /> *[[Daily_Post_June_23_2026|Daily Post June 23 2026 - Debian Server Hardening]]<br /> *[[Daily_Post_June_24_2026|Daily Post June 24 2026 - Mautic for Marketing Freedom]]<br /> <br /> ===May 2026 ===<br /> *[[Daily_Post_May_01_2026|Daily Post May 01 2026 - Ghost]]<br /> *[[Daily_Post_May_07_2026|Daily Post May 07 2026 - Lynis]]<br /> *[[Daily_Post_May_08_2026|Daily Post May 08 2026 - FreePBX]]<br /> *[[Daily_Post_May_25_2026|Daily Post May 25 2026 - How the SES System and FOSS Ignorance Stifle Japanese Innovation]]<br /> *[[Daily_Post_May_26_2026|Daily Post May 26 2026 - The Illusion of Convenience, Us Care When Choosing SaaS]]<br /> *[[Daily_Post_May_27_2026|Daily Post May 27 2026 - SuiteCRM]]<br /> *[[Daily_Post_May_28_2026|Daily Post May 28 2026 - Security Onion]]<br /> *[[Daily_Post_May_29_2026|Daily Post May 29 2026 - GNU Health]]<br /> <br /> ===April 2026 ===<br /> *[[Daily_Post_April_01_2026|Daily Post April 01 2026 - Nextcloud Forms]]<br /> *[[Daily_Post_April_02_2026|Daily Post April 02 2026 - Nextcloud Talk]]<br /> *[[Daily_Post_April_03_2026|Daily Post April 03 2026 - Nextcloud Calendar]]<br /> *[[Daily_Post_April_07_2026|Daily Post April 06 2026 - NoScript]]<br /> *[[Daily_Post_April_08_2026|Daily Post April 08 2026 - Web Browsers]]<br /> *[[Daily_Post_April_09_2026|Daily Post April 09 2026 - Privacy Badger]]<br /> *[[Daily_Post_April_10_2026|Daily Post April 10 2026 - SSHGuard]]<br /> *[[Daily_Post_April_13_2026|Daily Post April 13 2026 - It's ok to try it yourself]]<br /> *[[Daily_Post_April_14_2026|Daily Post April 14 2026 - Mautic Points]]<br /> *[[Daily_Post_April_15_2026|Daily Post April 15 2026 - Mautic Stages]]<br /> *[[Daily_Post_April_16_2026|Daily Post April 16 2026 - Mautic Projects]]<br /> *[[Daily_Post_April_17_2026|Daily Post April 17 2026 - Mautic Campaigns]]<br /> *[[Daily_Post_April_20_2026|Daily Post April 20 2026 - Mautic Components]]<br /> *[[Daily_Post_April_21_2026|Daily Post April 21 2026 - Mautic Segments]]<br /> *[[Daily_Post_April_22_2026|Daily Post April 22 2026 - Mautic APIs, Marketpace, Plugins, Webhooks]]<br /> *[[Daily_Post_April_24_2026|Daily Post April 24 2026 - LocalAI]]<br /> *[[Daily_Post_April_27_2026|Daily Post April 27 2026 - Zulip]]<br /> *[[Daily_Post_April_29_2026|Daily Post April 29 2026 - FreeScout]]<br /> *[[Daily_Post_April_30_2026|Daily Post April 30 2026 - OpenTelemetry]]<br /> <br /> ===March 2026 ===<br /> *[[Daily_Post_March_02_2026|Daily Post March 02 2026 - MailCow]]<br /> *[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]]<br /> *[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]]<br /> *[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]]<br /> *[[Daily_Post_March_09_2026|Daily Post March 09 2026 - Forem]]<br /> *[[Daily_Post_March_11_2026|Daily Post March 11 2026 - OPNsense (Firewall/Security)]]<br /> *[[Daily_Post_March_12_2026|Daily Post March 12 2026 - osquery]]<br /> *[[Daily_Post_March_13_2026|Daily Post March 13 2026 - ONLYOFFICE]]<br /> *[[Daily_Post_March_16_2026|Daily Post March 16 2026 - Metasploit Framework]]<br /> *[[Daily_Post_March_17_2026|Daily Post March 17 2026 - fsroot]]<br /> *[[Daily_Post_March_19_2026|Daily Post March 19 2026 - Immich]]<br /> *[[Daily_Post_March_23_2026|Daily Post March 23 2026 - eXo Platform]]<br /> *[[Daily_Post_March_24_2026|Daily Post March 24 2026 - Nextcloud Email Client]]<br /> *[[Daily_Post_March_25_2026|Daily Post March 25 2026 - Nextcloud Passwords]]<br /> *[[Daily_Post_March_26_2026|Daily Post March 26 2026 - Nextcloud Deck]]<br /> *[[Daily_Post_March_27_2026|Daily Post March 27 2026 - Nextcloud Flow]]<br /> *[[Daily_Post_March_30_2026|Daily Post March 30 2026 - Nextcloud Notes]]<br /> <br /> ===February 2026 ===<br /> *[[Daily_Post_February_02_2026|Daily Post February 02 2026 - OpenStreetMap]]<br /> *[[Daily_Post_February_04_2026|Daily Post February 04 2026 - WeKan]]<br /> *[[Daily_Post_February_05_2026|Daily Post February 05 2026 - WireShark]]<br /> *[[Daily_Post_February_06_2026|Daily Post February 06 2026 - Make the shift toward FOSS]]<br /> *[[Daily_Post_February_10_2026|Daily Post February 10 2026 - Self-Hosting LLMs]]<br /> *[[Daily_Post_February_11_2026|Daily Post February 11 2026 - CryptPad]]<br /> *[[Daily_Post_February_12_2026|Daily Post February 12 2026 - Woodpecker CI]]<br /> *[[Daily_Post_February_13_2026|Daily Post February 13 2026 - PrivateBin]]<br /> *[[Daily_Post_February_16_2026|Daily Post February 16 2026 - Paperless-ngx]]<br /> *[[Daily_Post_February_18_2026|Daily Post February 18 2026 - Krita]]<br /> *[[Daily_Post_February_19_2026|Daily Post February 19 2026 - Podman]]<br /> *[[Daily_Post_February_20_2026|Daily Post February 20 2026 - Aegis]]<br /> *[[Daily_Post_February_24_2026|Daily Post February 24 2026 - Ownership vs. Outsourcing]]<br /> *[[Daily_Post_February_25_2026|Daily Post February 25 2026 - Pivot Toward Autonomy]]<br /> *[[Daily_Post_February_26_2026|Daily Post February 26 2026 - Intention to Implementation]]<br /> *[[Daily_Post_February_27_2026|Daily Post February 27 2026 - Maturity of Openness]]<br /> <br /> ===January 2026 ===<br /> *[[Daily_Post_January_06_2026|Daily Post January 06 2026 - Baserow]]<br /> *[[Daily_Post_January_07_2026|Daily Post January 07 2026 - The Hesitant Japanese SME]]<br /> *[[Daily_Post_January_08_2026|Daily Post January 08 2026 - Licenses]]<br /> *[[Daily_Post_January_09_2026|Daily Post January 09 2026 - PDFArranger]]<br /> *[[Daily_Post_January_12_2026|Daily Post January 12 2026 - Sphinx]]<br /> *[[Daily_Post_January_13_2026|Daily Post January 13 2026 - LibreWolf]]<br /> *[[Daily_Post_January_14_2026|Daily Post January 14 2026 - Privacy Badger]]<br /> *[[Daily_Post_January_15_2026|Daily Post January 15 2026 - Linkewarden]]<br /> *[[Daily_Post_January_16_2026|Daily Post January 16 2026 - Risks of Free Big Tech]]<br /> *[[Daily_Post_January_19_2026|Daily Post January 19 2026 - Weblate]]<br /> *[[Daily_Post_January_20_2026|Daily Post January 20 2026 - Offen]]<br /> *[[Daily_Post_January_21_2026|Daily Post January 21 2026 - LibreSpeed]]<br /> *[[Daily_Post_January_22_2026|Daily Post January 22 2026 - Mautic 7.0]]<br /> *[[Daily_Post_January_26_2026|Daily Post January 26 2026 - Aureus ERP]]<br /> *[[Daily_Post_January_27_2026|Daily Post January 27 2026 - VeraCrypt]]<br /> *[[Daily_Post_January_29_2026|Daily Post January 29 2026 - OpenNMS]]<br /> *[[Daily_Post_January_30_2026|Daily Post January 30 2026 - Lufi]]<br /> <br /> ==2025==<br /> ===December 2025===<br /> *[[Daily_Post_December_01_2025|Daily Post December 01 2025 - Knime]]<br /> *[[Daily_Post_December_02_2025|Daily Post December 02 2025 - Collabora Online Desktop]]<br /> *[[Daily_Post_December_04_2025|Daily Post December 04 2025 - KumoMTA]]<br /> *[[Daily_Post_December_05_2025|Daily Post December 05 2025 - Taiga]]<br /> *[[Daily_Post_December_09_2025|Daily Post December 09 2025 - SeaweedFS]]<br /> *[[Daily_Post_December_11_2025|Daily Post December 11 2025 -Technitium]]<br /> *[[Daily_Post_December_12_2025|Daily Post December 12 2025 - Japan's FOSS Reality]]<br /> *[[Daily_Post_December_15_2025|Daily Post December 15 2025 - Looking at Collabora Online]]<br /> *[[Daily_Post_December_16_2025|Daily Post December 16 2025 - matrix]]<br /> *[[Daily_Post_December_17_2025|Daily Post December 17 2025 - LiteFarm]]<br /> *[[Daily_Post_December_18_2025|Daily Post December 18 2025 - Wagtail]]<br /> *[[Daily_Post_December_19_2025|Daily Post December 19 2025 - KeePassXC]]<br /> *[[Daily_Post_December_22_2025|Daily Post December 22 2025 - Keycloak]]<br /> *[[Daily_Post_December_24_2025|Daily Post December 24 2025 - OpenCloud]]<br /> *[[Daily_Post_December_25_2025|Daily Post December 25 2025 - OSSEC]]<br /> *[[Daily_Post_December_26_2025|Daily Post December 26 2025 - Ghost]]<br /> <br /> ===November 2025===<br /> *[[Daily_Post_November_4_2025|Daily Post November 4 2025 - FOSS Reality in Japan]]<br /> *[[Daily_Post_November_5_2025|Daily Post November 6 2025 - Let’s Encrypt ]]<br /> *[[Daily_Post_November_7_2025|Daily Post November 7 2025 - SaaS ]]<br /> *[[Daily_Post_November_10_2025|Daily Post November 10 2025 - Kasm Workspaces ]]<br /> *[[Daily_Post_November_11_2025|Daily Post November 11 2025 - Calibre]]<br /> *[[Daily_Post_November_12_2025|Daily Post November 12 2025 - Drupal]]<br /> *[[Daily_Post_November_13_2025|Daily Post November 13 2025 - Open Project ]]<br /> *[[Daily_Post_November_14_2025|Daily Post November 14 2025 - Outsourcing]]<br /> *[[Daily_Post_November_18_2025|Daily Post November 18 2025 - Element]]<br /> *[[Daily_Post_November_19_2025|Daily Post November 19 2025 - Znuny]]<br /> *[[Daily_Post_November_20_2025|Daily Post November 20 2025 - Trilium]]<br /> *[[Daily_Post_November_21_2025|Daily Post November 21 2025 - TYPO3]]<br /> *[[Daily_Post_November_25_2025|Daily Post November 25 2025 - MintHCM]]<br /> *[[Daily_Post_November_26_2025|Daily Post November 26 2025 - Pleasanter]]<br /> *[[Daily_Post_November_28_2025|Daily Post November 28 2025 - Syncthing]]<br /> <br /> ===October 2025===<br /> *[[Daily_Post_October_2_2025|Daily Post October 2 2025 - OpenVAS]]<br /> *[[Daily_Post_October_3_2025|Daily Post October 3 2025 - Logseq]]<br /> *[[Daily_Post_October_6_2025|Daily Post October 6 2025 - Rocket.Chat]]<br /> *[[Daily_Post_October_7_2025|Daily Post October 7 2025 - MantisBT]]<br /> *[[Daily_Post_October_9_2025|Daily Post October 9 2025 - Papra]]<br /> *[[Daily_Post_October_10_2025|Daily Post October 10 2025 - Gatus]]<br /> *[[Daily_Post_October_14_2025|Daily Post October 14 2025 - New Peppermint OS]]<br /> *[[Daily_Post_October_15_2025|Daily Post October 15 2025 - Nextcloud AIO]]<br /> *[[Daily_Post_October_16_2025|Daily Post October 16 2025 - Deploy Collabora Online(native)]]<br /> *[[Daily_Post_October_17_2025|Daily Post October 17 2025 - Deploy Collabora Online(docker)]]<br /> *[[Daily_Post_October_20_2025|Daily Post October 20 2025 - Self-Hosting Matters for Small Businesses in Japan]]<br /> *[[Daily_Post_October_21_2025|Daily Post October 21 2025 - Cloud Sprawl]]<br /> *[[Daily_Post_October_23_2025|Daily Post October 23 2025 - Email Options]]<br /> *[[Daily_Post_October_24_2025|Daily Post October 24 2025 - ERPNext]]<br /> *[[Daily_Post_October_25_2025|Daily Post October 27 2025 - Scribus]]<br /> *[[Daily_Post_October_28_2025|Daily Post October 28 2025 - Seafile]]<br /> *[[Daily_Post_October_29_2025|Daily Post October 29 2025 - Redash]]<br /> *[[Daily_Post_October_30_2025|Daily Post October 30 2025 - GIMP]]<br /> *[[Daily_Post_October_31_2025|Daily Post October 31 2025 - Thunderbird]]<br /> <br /> ===September 2025===<br /> *[[Daily_Post_September_1_2025|Daily Post September 1 2025 - BookStack]]<br /> *[[Daily_Post_September_3_2025|Daily Post September 3 2025 - LibreTranslate]]<br /> *[[Daily_Post_September_4_2025|Daily Post September 4 2025 - Pyinfra]]<br /> *[[Daily_Post_September_5_2025|Daily Post September 5 2025 - Blocky]]<br /> *[[Daily_Post_September_8_2025|Daily Post September 8 2025 - Roundcube]]<br /> *[[Daily_Post_September_9_2025|Daily Post September 9 2025 - OpenCTI]]<br /> *[[Daily_Post_September_11_2025|Daily Post September 11 2025 - Papermark]]<br /> *[[Daily_Post_September_12_2025|Daily Post September 12 2025 - BigBlueButton]]<br /> *[[Daily_Post_September_15_2025|Daily Post September 15 2025 - opsi]]<br /> *[[Daily_Post_September_16_2025|Daily Post September 16 2025 - Nextcloud Talk]]<br /> *[[Daily_Post_September_17_2025|Daily Post September 17 2025 - Mautic Spam]]<br /> *[[Daily_Post_September_18_2025|Daily Post September 18 2025 - Selfhosted Email]]<br /> *[[Daily_Post_September_19_2025|Daily Post September 19 2025 - Dolibarr]]<br /> *[[Daily_Post_September_22_2025|Daily Post September 22 2025 - NIAP]]<br /> *[[Daily_Post_September_23_2025|Daily Post September 23 2025 - MinIO]]<br /> *[[Daily_Post_September_24_2025|Daily Post September 24 2025 - FOSS Advocacy in Japan]]<br /> *[[Daily_Post_September_25_2025|Daily Post September 25 2025 - Grist-Core]]<br /> *[[Daily_Post_September_26_2025|Daily Post September 26 2025 - XCP-ng]]<br /> *[[Daily_Post_September_29_2025|Daily Post September 29 2025 - ZITADEL]]<br /> *[[Daily_Post_September_30_2025|Daily Post September 30 2025 - CodeBerg]]<br /> <br /> ===August 2025===<br /> *[[Daily_Post_August_1_2025|Daily Post August 1 2025 - Mail-in-a-Box]]<br /> *[[Daily_Post_August_4_2025|Daily Post August 4 2025 - FusionPBX]]<br /> *[[Daily_Post_August_6_2025|Daily Post August 6 2025 - Galene]]<br /> *[[Daily_Post_August_7_2025|Daily Post August 7 2025 - MintHCM]]<br /> *[[Daily_Post_August_8_2025|Daily Post August 8 2025 - Incus]]<br /> *[[Daily_Post_August_11_2025|Daily Post August 11 2025 - OpenSearch]]<br /> *[[Daily_Post_August_13_2025|Daily Post August 13 2025 - Authentik]]<br /> *[[Daily_Post_August_14_2025|Daily Post August 14 2025 - Seafile]]<br /> *[[Daily_Post_August_15_2025|Daily Post August 15 2025 - Clonezilla]]<br /> *[[Daily_Post_August_18_2025|Daily Post August 18 2025 - SuiteCRM]]<br /> *[[Daily_Post_August_19_2025|Daily Post August 19 2025 - Duplicated Chat Services]]<br /> *[[Daily_Post_August_20_2025|Daily Post August 20 2025 - Snipe-IT]]<br /> *[[Daily_Post_August_21_2025|Daily Post August 21 2025 - webmin]]<br /> *[[Daily_Post_August_22_2025|Daily Post August 22 2025 - Gophish]]<br /> *[[Daily_Post_August_24_2025|Daily Post August 25 2025 - GLPI]]<br /> *[[Daily_Post_August_27_2025|Daily Post August 27 2025 - OpenCast]]<br /> *[[Daily_Post_August_28_2025|Daily Post August 28 2025 - FleetDM]]<br /> *[[Daily_Post_August_29_2025|Daily Post August 29 2025 - Joplin]]<br /> <br /> ===July 2025===<br /> *[[Daily_Post_July_1_2025|Daily Post July 1 2025 - YARA]]<br /> *[[Daily_Post_July_2_2025|Daily Post July 2 2025 - Desktop Environments (Linux) ]]<br /> *[[Daily_Post_July_3_2025|Daily Post July 3 2025 - Windows manager (Linux) ]]<br /> *[[Daily_Post_July_4_2025|Daily Post July 4 2025 - Collabora Office / Online]]<br /> *[[Daily_Post_July_7_2025|Daily Post July 7 2025 - pangolin]]<br /> *[[Daily_Post_July_8_2025|Daily Post July 8 2025 - Thinking Tech Strategy]]<br /> *[[Daily_Post_July_9_2025|Daily Post July 9 2025 - OpenNebula]]<br /> *[[Daily_Post_July_10_2025|Daily Post July 10 2025 - SaltCorn]]<br /> *[[Daily_Post_July_11_2025|Daily Post July 11 2025 - CrowdSec]]<br /> *[[Daily_Post_July_14_2025|Daily Post July 14 2025 - Odoo]]<br /> *[[Daily_Post_July_15_2025|Daily Post July 15 2025 - Digital Transformation, let's talk about it ]]<br /> *[[Daily_Post_July_16_2025|Daily Post July 16 2025 - Docuseal]]<br /> *[[Daily_Post_July_18_2025|Daily Post July 18 2025 - NetBird]]<br /> *[[Daily_Post_July_21_2025|Daily Post July 21 2025 - Flarum]]<br /> *[[Daily_Post_July_22_2025|Daily Post July 22 2025 - matrix]]<br /> *[[Daily_Post_July_23_2025|Daily Post July 23 2025 - OpenObserve]]<br /> *[[Daily_Post_July_24_2025|Daily Post July 24 2025 - Wallabag]]<br /> *[[Daily_Post_July_25_2025|Daily Post July 25 2025 - OpenMediaVault]]<br /> *[[Daily_Post_July_28_2025|Daily Post July 28 2025 - AFFiNE]]<br /> *[[Daily_Post_July_30_2025|Daily Post July 30 2025 - Incus]]<br /> *[[Daily_Post_July_31_2025|Daily Post July 31 2025 - Stirling-PDF]]<br /> <br /> ===June 2025===<br /> *[[Daily_Post_June_2_2025|Daily Post June 2 2025 - Mediawiki]]<br /> *[[Daily_Post_June_4_2025|Daily Post June 4 2025 - XWiki]]<br /> *[[Daily_Post_June_5_2025|Daily Post June 5 2025 - Clonezilla]]<br /> *[[Daily_Post_June_6_2025|Daily Post June 6 2025 - Understanding FOSS Japan POV]]<br /> *[[Daily_Post_June_9_2025|Daily Post June 9 2025 - Apache ECharts]]<br /> *[[Daily_Post_June_10_2025|Daily Post June 10 2025 - OpenBoard]]<br /> *[[Daily_Post_June_11_2025|Daily Post June 11 2025 - mintarc]]<br /> *[[Daily_Post_June_12_2025|Daily Post June 12 2025 - Solr]]<br /> *[[Daily_Post_June_13_2025|Daily Post June 13 2025 - Wazuh]]<br /> *[[Daily_Post_June_16_2025|Daily Post June 16 2025 - GnuCash]]<br /> *[[Daily_Post_June_17_2025|Daily Post June 17 2025 - Cal.com]]<br /> *[[Daily_Post_June_18_2025|Daily Post June 18 2025 - Authelia]]<br /> *[[Daily_Post_June_19_2025|Daily Post June 19 2025 - Uptime Kuma]]<br /> *[[Daily_Post_June_20_2025|Daily Post June 20 2025 - SBOM]]<br /> *[[Daily_Post_June_23_2025|Daily Post June 23 2025 - Vendor Lock In]]<br /> *[[Daily_Post_June_25_2025|Daily Post June 25 2025 - Mautic]]<br /> *[[Daily_Post_June_26_2025|Daily Post June 26 2025 - OpenBao]]<br /> *[[Daily_Post_June_27_2025|Daily Post June 27 2025 - WireGuard]]<br /> *[[Daily_Post_June_30_2025|Daily Post June 30 2025 - Redmine]]<br /> <br /> ===May 2025===<br /> *[[Daily_Post_May_1_2025|Daily Post May 1 2025 - Web Browsers]]<br /> *[[Daily_Post_May_2_2025|Daily Post May 2 2025 - LUFI]]<br /> *[[Daily_Post_May_5_2025|Daily Post May 5 2025 - Jellyfin]]<br /> *[[Daily_Post_May_6_2025|Daily Post May 6 2025 - Nextcloud]]<br /> *[[Daily_Post_May_7_2025|Daily Post May 7 2025 - Apache Answer]]<br /> *[[Daily_Post_May_8_2025|Daily Post May 8 2025 - ThingsBoard]]<br /> *[[Daily_Post_May_9_2025|Daily Post May 9 2025 - Privacy And Data Ownership ]]<br /> *[[Daily_Post_May_13_2025|Daily Post May 13 2025 - Pi-hole ]]<br /> *[[Daily_Post_May_14_2025|Daily Post May 14 2025 - Taiga ]]<br /> *[[Daily_Post_May_15_2025|Daily Post May 15 2025 - BuildBot ]]<br /> *[[Daily_Post_May_16_2025|Daily Post May 16 2025 - AI and FOSS, Thinking Business Responsibility ]]<br /> *[[Daily_Post_May_19_2025|Daily Post May 19 2025 - Calyx Meet ]]<br /> *[[Daily_Post_May_20_2025|Daily Post May 20 2025 - LeanTime ]]<br /> *[[Daily_Post_May_21_2025|Daily Post May 21 2025 - FarmOS ]]<br /> *[[Daily_Post_May_22_2025|Daily Post May 22 2025 - Business Owner's FOSS Perspective ]]<br /> *[[Daily_Post_May_23_2025|Daily Post May 23 2025 - CiviCRM ]]<br /> *[[Daily_Post_May_26_2025|Daily Post May 26 2025 - Joomla ]]<br /> *[[Daily_Post_May_27_2025|Daily Post May 27 2025 - OMV ]]<br /> *[[Daily_Post_May_28_2025|Daily Post May 28 2025 - Serious Business Decisions]]<br /> *[[Daily_Post_May_29_2025|Daily Post May 29 2025 - Apache Superset]]<br /> *[[Daily_Post_May_30_2025|Daily Post May 30 2025 - Fediverse]]<br /> <br /> ===April 2025===<br /> *[[Daily_Post_Apr_1_2025|Daily Post Apr 1 2025 - OWA]]<br /> *[[Daily_Post_Apr_2_2025|Daily Post Apr 2 2025 - SSPL]]<br /> *[[Daily_Post_Apr_3_2025|Daily Post Apr 3 2025 - Guacamole ]]<br /> *[[Daily_Post_Apr_4_2025|Daily Post Apr 4 2025 - Grav]]<br /> *[[Daily_Post_Apr_7_2025|Daily Post Apr 7 2025 - Mautic 6.0]]<br /> *[[Daily_Post_Apr_8_2025|Daily Post Apr 8 2025 - Discourse]]<br /> *[[Daily_Post_Apr_9_2025|Daily Post Apr 9 2025 - LimeSurvey]]<br /> *[[Daily_Post_Apr_10_2025|Daily Post Apr 10 2025 - Japan FOSS Illusion]]<br /> *[[Daily_Post_Apr_11_2025|Daily Post Apr 11 2025 - Anytype]]<br /> *[[Daily_Post_Apr_14_2025|Daily Post Apr 14 2025 - iRedMail]]<br /> *[[Daily_Post_Apr_15_2025|Daily Post Apr 15 2025 - Chatwoot]]<br /> *[[Daily_Post_Apr_16_2025|Daily Post Apr 16 2025 - Wireguard]]<br /> *[[Daily_Post_Apr_17_2025|Daily Post Apr 17 2025 - Forgejo]]<br /> *[[Daily_Post_Apr_18_2025|Daily Post Apr 18 2025 - Data Privacy and Ownership]]<br /> *[https://matomo.mintarc.com/mediawiki/index.php?title=Mmdebstrap Daily Post Apr 21 2025 - mmdebstrap]<br /> *[[Daily_Post_Apr_22_2025|Daily Post Apr 22 2025 - FormBricks]]<br /> *[[Daily_Post_Apr_23_2025|Daily Post Apr 23 2025 - SaaS Creep]]<br /> *[[Daily_Post_Apr_24_2025|Daily Post Apr 24 2025 - OpenMeetings]]<br /> *[[Daily_Post_Apr_25_2025|Daily Post Apr 25 2025 - Seafile]]<br /> *[[Daily_Post_Apr_28_2025|Daily Post Apr 28 2025 - The Choice for Small Businesses]]<br /> *[[Daily_Post_Apr_29_2025|Daily Post Apr 29 2025 - OpenSourceBilling]]<br /> *[[Daily_Post_Apr_30_2025|Daily Post Apr 30 2025 - Open Core and Washing]]<br /> <br /> ===March 2025===<br /> *[[Daily_Post_Mar_04_2025|Daily Post Mar 04 2025 - FOSS Contributions]]<br /> *[[Daily_Post_Mar_05_2025|Daily Post Mar 05 2025 - Deb822]]<br /> *[[Daily_Post_Mar_06_2025|Daily Post Mar 06 2025 - CycloneDX]]<br /> *[[Daily_Post_Mar_07_2025|Daily Post Mar 07 2025 - MiroTalk]]<br /> *[[Daily_Post_Mar_10_2025|Daily Post Mar 10 2025 - Collabora Online ]]<br /> *[[Daily_Post_Mar_12_2025|Daily Post Mar 12 2025 - SaaS]] <br /> *[[Daily_Post_Mar_13_2025|Daily Post Mar 13 2025 - Owncast]]<br /> *[[Daily_Post_Mar_14_2025|Daily Post Mar 14 2025 - ModSecurity]]<br /> *[[Daily_Post_Mar_17_2025|Daily Post Mar 17 2025 - A tech story]]<br /> *[[Daily_Post_Mar_18_2025|Daily Post Mar 18 2025 - Buildbase]]<br /> *[[Daily_Post_Mar_19_2025|Daily Post Mar 19 2025 - Listmonk]]<br /> *[[Daily_Post_Mar_21_2025|Daily Post Mar 21 2025 - MintHCM]]<br /> *[[Daily_Post_Mar_24_2025|Daily Post Mar 24 2025 - RustDesk]]<br /> *[[Daily_Post_Mar_25_2025|Daily Post Mar 25 2025 - OWASP]]<br /> *[[Daily_Post_Mar_26_2025|Daily Post Mar 26 2025 - Japan FOSS Reality]]<br /> *[[Daily_Post_Mar_28_2025|Daily Post Mar 28 2025 - Vaultwarden]]<br /> *[[Daily_Post_Mar_31_2025|Daily Post Mar 31 2025 - FOSS Licenses]]<br /> <br /> ===February 2025===<br /> *[[Daily_Post_Feb_24_2025|Daily Post Feb 24 2025 - Debunking]]<br /> *[[Daily_Post_Feb_25_2025|Daily Post Feb 25 2025 - FOSS Solutions]] <br /> *[[Our_collabora_online_partnership|Daily Post Feb 26 2025 - mintarc-Collabora]]<br /> <br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div style=&quot;clear: both;&quot;&gt;&lt;/div&gt;</div>

Tommy