Is this limited to Sentry 9.0.0?

[jeff-h]

Is this limited to Sentry 9.0.0, or can I use it to install the latest current version?

[mherrmann]

I don't know. I would recommend you simply try it.

[jeff-h]

I suppose I would need to update the commit referenced here?

https://github.com/mherrmann/sentry-self-hosted/blob/master/install.sh#L48

I'll do as you suggested and just give it a try :) It'll be in a month or so but I'll report back here with the results.

[jeff-h]

So I have just successfully installed Sentry 21.7.0 on a Vultr 1GB instance. I did not use your script to do it, so I'll outline what I did. Firstly however, I wanted to thank you for providing this script; I used it for quite some years and it gave me confidence that Sentry runs fine on 1GB ram. For context we are processing around 25,000 events/month on our install.

I looked carefully at the installation mechanisms provided by Sentry and decided to give the standard install a try, with one simple change. There is a minimum requirements check, which mandates some (absurdly high) VPS specs: 4 CPU cores, 8GB RAM. I simply edited this and lowered the requirements so my tiny Vultr VPS passed the checks.

With that one simple change, the standard install ran perfectly; took around 25 mins start to finish on my VPS.

For anyone wanting to attempt this, the process went something like this:

• provision new VPS
• lock down the server, configure SSH key-based access, create accounts etc as you normally would (anyone not comfortable with this step might like this script). I also install fail2ban.
• install docker and docker-compose. There are plenty of tutorials for this.
• git clone https://github.com/getsentry/onpremise.git sentry
• cd sentry then nano install/check-minimum-requirements.sh and lower the requirements.
• sudo ./install.sh
• edit docker-compose's .env to serve on port 80:

  nano .env
  # change SENTRY_BIND=9000  to SENTRY_BIND=80
  

• docker-compose up -d

At this point Sentry is up & running just fine, but only on port 80. I personally use Cloudflare, so I pointed my sentry subdomain at the new VPS, left the cloud "orange" and set their "SSL/TLS" config to "Flexible". Sentry is now available via https 🎉

[mherrmann]

Thank you for sharing your experiences!

[Aulig]

So I have just successfully installed Sentry 21.7.0 on a Vultr 1GB instance. I did not use your script to do it, so I'll outline what I did. Firstly however, I wanted to thank you for providing this script; I used it for quite some years and it gave me confidence that Sentry runs fine on 1GB ram. For context we are processing around 25,000 events/month on our install.

I looked carefully at the installation mechanisms provided by Sentry and decided to give the standard install a try, with one simple change. There is a minimum requirements check, which mandates some (absurdly high) VPS specs: 4 CPU cores, 8GB RAM. I simply edited this and lowered the requirements so my tiny Vultr VPS passed the checks.

With that one simple change, the standard install ran perfectly; took around 25 mins start to finish on my VPS.

For anyone wanting to attempt this, the process went something like this:

* provision new VPS

* lock down the server, configure SSH key-based access, create accounts etc as you normally would (anyone not comfortable with this step might like [this script](https://github.com/jasonheecs/ubuntu-server-setup)). I also install fail2ban.

* install docker and docker-compose. There are plenty of tutorials for this.

* `git clone https://github.com/getsentry/onpremise.git sentry`

* `cd sentry` then `nano install/check-minimum-requirements.sh` and lower the requirements.

* `sudo ./install.sh`

* edit docker-compose's `.env` to serve on port 80:
  ```
  nano .env
  # change SENTRY_BIND=9000  to SENTRY_BIND=80
  ```

* `docker-compose up -d`

At this point Sentry is up & running just fine, but only on port 80. I personally use Cloudflare, so I pointed my sentry subdomain at the new VPS, left the cloud "orange" and set their "SSL/TLS" config to "Flexible". Sentry is now available via https 🎉

Thanks for your guide! Unfortunately I couldn't get it to run on such a small server (install.sh always failed with random errors). Now I'm running on a 2 core 4GB VPS though, which isn't too expensive at Hetzner.