<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deploy on Cesar Gimenes</title><link>https://crg.eti.br/en/tags/deploy/</link><description>Recent content in Deploy on Cesar Gimenes</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>crg@crg.eti.br (Cesar Gimenes)</managingEditor><webMaster>crg@crg.eti.br (Cesar Gimenes)</webMaster><lastBuildDate>Sat, 09 Mar 2024 11:45:51 -0300</lastBuildDate><atom:link href="https://crg.eti.br/en/tags/deploy/index.xml" rel="self" type="application/rss+xml"/><item><title>Deploying Applications Using curl</title><link>https://crg.eti.br/en/post/deploy_de_aplicacoes_usando_curl/</link><pubDate>Sat, 09 Mar 2024 11:45:51 -0300</pubDate><author>crg@crg.eti.br (Cesar Gimenes)</author><guid>https://crg.eti.br/en/post/deploy_de_aplicacoes_usando_curl/</guid><description>&lt;p>Small teams face several challenges when distributing binaries these days. If you simply put an application up for download on a website, search tools will immediately flag your site as suspicious content. Browsers show the user a scary warning, and there is no way to remove it, even with a signed binary. The warning only goes away once enough users have downloaded your binary without reporting problems.&lt;/p>
&lt;p>Letting the user download the binary from some already well-known site, even GitHub, isn&amp;rsquo;t ideal, especially for closed-source applications.&lt;/p></description></item></channel></rss>