Question thread #77

[pauamma]

It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.

Comments

[pauamma]

To elaborate on what Denise said, you should expect a time investment of up to... I want to say 5-10 hours per week (assuming nothing goes wrong - if something does, all bets are off) monitoring your system and keeping it running smoothly (including the email part which you didn't discuss in your initial request and can be significant when a Big Player(TM) decides you are spamming them, or perhaps just doesn't trust you because you're a newcomer) unless you can invest a lot of up-front time automating that monitoring, which the Dreamwidth documentation doesn't cover at all. If you're still interested, let us know, and we'll point you to the documentation that does exist.

[denise]

I don't really think they'd have to worry too much about monitoring for a two-person install where they don't need 100% uptime or reliability, "notice that it's busted when we go to use it and fix it then" wouldn't be too awful for that use case. But yeah, ugh, the email thing.

[pauamma]

Fair enough.

[devilbear]

The time investment would be less than ideal for sure, but more importantly you (and denise's addition) have shed light on an important concern my friend and I had completely overlooked re: email. Given we'd want to avoid the headache of gmail deciding we're spam and don't have the time to dedicate to upkeep, this probably isn't the best option for us.

I appreciate the honesty of your advice! And your willingness to point me in the right direction, had I decided it'd still be a worthwhile undertaking for our project.