3 ms·
On this note, I'm setting up an OSS side project (finally going public after a year+ of internal revisions) for many of the reasons cited in this project. It's
by asdkhadsj 7y ago
On this note, I'm setting up an OSS side project (finally going public after a year+ of internal revisions) for many of the reasons cited in this project. It's something I care about.
With that said, part of my plan is to have a hosted version of the application - at least until the moderation of content makes me regret it, hah. However, I am concerned about the overhead of both writing and maintaining a complex FOSS project, but also handling [dev]ops of the project.
I know enough ops to be dangerous, but not much beyond that. I also know enough to know how little I know. Due to budget constraints, I will likely be hosting this on a very low cost server and exploiting CDN caching/etc very, very heavily - but I do imagine I'll need a cheap VPS. Ie, I don't think I can exploit a fully managed Function as a Service architecture; I think I'll be managing a VPS.
So for a low budget project with minimal ops experience, how can I ensure security and safety? What path to growth can I walk, without consuming my time trying to become an expert in [dev]ops?