3 ms·

I do it KISS. Deployment for me is always a git hook, usually with a private gitea server. So I have versioning and rollbacks available with a cute UI if necess

by herbst 5y ago

I do it KISS. Deployment for me is always a git hook, usually with a private gitea server. So I have versioning and rollbacks available with a cute UI if necessary. DBs run side by side and are simply backed up regularly with whatever backup solution the VPS offers. That's it. Out of school I put way more effort in building my infrastructure but in reality a good VPS, something like Cloudflare and some app based caching can run millions of daily views over 20+ different apps without issues. Edit:// it's mostly rails apps I host btw. For my wordpress installs i use dedicated VPSes because those scale horrible.

playpause 5y ago
I like this answer, but could you expand a bit on why gitea? Never used it myself, but it looks like self-hosted OSS clone of GitHub? If so, my instinct (in terms of KISS) would be to just use GitHub, so I don’t have to set up and maintain my own thing. What made you decide to go with gitea, out of interest?
- herbst 5y ago
  GitHub would be the opposite of kiss in my opinion. External dependencies and pushing to remote servers are just pain points. > git init --bare On your remote server is all you need to spawn a repo to push to, usually hook examples already included. The hook can then directly checkout to my live directory, run migrations and restart the server without weird remote automations after every (or specified) push. Gitea is just a little extra (setup once, touch never thingy) for quick edits and checks (it's a wonderful lightweight piece of software too)
iKevinShah 5y ago
> Out of school I put way more effort in building my infrastructure but in reality a good VPS, something like Cloudflare and some app based caching can run millions of daily views over 20+ different apps without issues. I read such messages (and also agree to it mostly) and then I encounter my peers wanting active-active clusters with K8s on top or something and I feel I like a dinosaur. Refreshing to see KISS still being used. Also gitea. What an awesome piece of open source software.
- Sanguinaire 5y ago
  Don't fall victim to resume-driven development; keep on KISSing.

by herbst 5y ago

playpause 5y ago

I like this answer, but could you expand a bit on why gitea? Never used it myself, but it looks like self-hosted OSS clone of GitHub? If so, my instinct (in terms of KISS) would be to just use GitHub, so I don’t have to set up and maintain my own thing. What made you decide to go with gitea, out of interest?

herbst 5y ago
GitHub would be the opposite of kiss in my opinion. External dependencies and pushing to remote servers are just pain points. > git init --bare On your remote server is all you need to spawn a repo to push to, usually hook examples already included. The hook can then directly checkout to my live directory, run migrations and restart the server without weird remote automations after every (or specified) push. Gitea is just a little extra (setup once, touch never thingy) for quick edits and checks (it's a wonderful lightweight piece of software too)

iKevinShah 5y ago

> Out of school I put way more effort in building my infrastructure but in reality a good VPS, something like Cloudflare and some app based caching can run millions of daily views over 20+ different apps without issues. I read such messages (and also agree to it mostly) and then I encounter my peers wanting active-active clusters with K8s on top or something and I feel I like a dinosaur. Refreshing to see KISS still being used. Also gitea. What an awesome piece of open source software.

Sanguinaire 5y ago
Don't fall victim to resume-driven development; keep on KISSing.