More of a Linux sysadmin question: how do I run my go http server in AWS forever (even when I ssh out)

<p>I have an <code>http</code> binary file from <code>go build</code>. How do I run this binary file forever in my AWS server? I tried <code>./http &amp;</code> but it stops running once I log out of <code>ssh</code>. How do I make sure that my binary keeps running forever? An additional feature (but not important), have it automatically run again when it crashes.</p> <p>Kind of like Node.js&#39;s pm2 library.</p> <hr/>**评论：**<br/><br/>Ainar-G: <pre><p>Isn&#39;t that what <a href="https://en.wikipedia.org/wiki/Init" rel="nofollow">init</a> and alike usually do?</p></pre>StabbyCutyou: <pre><p>You should use a daemonizing tool like init /upstart / systemd to handle this for you. Leaving it running in a tmux or screen session &#34;works&#34;, but is not the correct way to handle what you want to do here.</p></pre>sjalfurstaralfur: <pre><p>yeah it&#39;s next on my todo list of things to learn</p></pre>oh-thatguy: <pre><p>SupervisorD is great for this, I also use it with node</p> <p><a href="http://supervisord.org/" rel="nofollow">http://supervisord.org/</a></p></pre>journalctl: <pre><p>You should use <code>systemd</code> or <code>Upstart</code> if you&#39;re on an older version of Ubuntu.</p> <p>They both have the ability to start your Go binary on boot and restart it on crash. They also log anything your program writes to Stdout or Stderr.</p></pre>din100: <pre><p>is this any good <a href="http://stackoverflow.com/questions/12486691/how-do-i-get-my-golang-web-server-to-run-in-the-background" rel="nofollow">http://stackoverflow.com/questions/12486691/how-do-i-get-my-golang-web-server-to-run-in-the-background</a> ?</p></pre>sjalfurstaralfur: <pre><p>This is perfect, thanks. I was able to get a quick bandaid solution with <code>nohup ./http &amp;</code></p></pre>WellAdjustedOutlaw: <pre><p>Just make a service file.</p></pre>jahayhurst: <pre><p>You can nohup, or run it in a screen - both are valid solutions.</p> <p>TBH tho, I typically like to instead write up a service script for it, and run it that way. It&#39;s not that hard to do.</p> <p>If you&#39;re running systemd, here&#39;s an example - maybe not a good example, but an example. I may hate systemd, but at least this is simple.</p> <pre><code>[Unit] Description=gnosis After=firewalld.service Requires=firewalld.service After=rsyslog.service Requires=rsyslog.service After=network.target Requires=network.target [Service] User=wiki ExecStart=/var/live/wiki-backend/webserver --config=/var/live/wiki-backend/config.json Restart=on-failure [Install] WantedBy=multi-user.target </code></pre> <p>If you have docker, go that way, it&#39;s wonderful.</p> <p>If you have good old sysvinit, you can get that working too. That&#39;s really not that bad either.</p></pre>cemclaug: <pre><p>screen session or a tmux session. These are really good for quick hacky solutions, just pipe the output to a log file and you&#39;re good to go.</p> <pre><code>screen -dmS &lt;screen_name&gt; ./http &gt; out.log </code></pre></pre>mnbbrown: <pre><p>I&#39;d suggest not using screen for running a server. Screen (and nohup) were created to maintain sessions between connections - not as an init system that can maintain dependencies, and handle restarts.</p></pre>alevinval: <pre><p>This. Screens.</p></pre>icub3d: <pre><p>I use docker for most of my go services and it works great.. There is a golang image that makes creating your own container easy. With that made, you can get docker to start it, keep it running, etc.</p></pre>