4 ms·

nginx does restart, but without taking the site down which is the most important aspect and the most important feature. Brining us to another point, I have depl

by amix 16y ago

nginx does restart, but without taking the site down which is the most important aspect and the most important feature. Brining us to another point, I have deployed a lot of servers that use textual configurations and I can't really see what problem you are solving and I can't see how storing the configuration in a relational database will solve any problems.

zedshaw 16y ago
I'm solving the problem of migrations, automation, tooling, and simplicity. Yes, you can do the many of the same things in both, and if you're an old school "I-ssh-into-100-boxes-all-day" sysadmin then they're the same thing. If you're a modern system administrator who automates, automates, automates, then this is better. For example, my challenge still stands, load an nginx config and tell me what version of nginx it is for. If you can't even do that then how can you automate it better than a sqlite3 file (remember, sqlite3 file, NOT RDBMS).
- amix 16y ago
  I use Fabric (fabfile.org) to automate deployments. It works pretty good and I don't see how it is going to work better with a relational database. Regarding your question: I don't really know or care what version a nginx config is written for (I could specify this in a comment if this was an issue and I can always test the config by running "nginx -t"). For the record, I have used nginx for years and this has never been an issue. Anyway, I am generally impressed by your other ideas in Mongrel2 and happy hacking :)
  - zedshaw 16y ago
    Using a SQLite database doesn't mean you can't use fabric, so it's not going to work better or worse. You see the difference? So far nothing you've said invalidates sqlite files or sql as a configuration interface. The version challenge points directly at what's wrong with config files: they aren't accessible to automation. If you can't even do this very simple thing from one programming language, then it means you can't do other things easily.
    - amix 16y ago
      If it isn't broken, don't fix it and I don't think textual configurations are broken, i.e. you are solving a problem that really isn't a problem. Based on my experience with Flipper (a MySQL master-master tool), SQL configurations are very hard to maintain and understand.

by amix 16y ago

zedshaw 16y ago

I'm solving the problem of migrations, automation, tooling, and simplicity. Yes, you can do the many of the same things in both, and if you're an old school "I-ssh-into-100-boxes-all-day" sysadmin then they're the same thing. If you're a modern system administrator who automates, automates, automates, then this is better. For example, my challenge still stands, load an nginx config and tell me what version of nginx it is for. If you can't even do that then how can you automate it better than a sqlite3 file (remember, sqlite3 file, NOT RDBMS).

amix 16y ago
I use Fabric (fabfile.org) to automate deployments. It works pretty good and I don't see how it is going to work better with a relational database. Regarding your question: I don't really know or care what version a nginx config is written for (I could specify this in a comment if this was an issue and I can always test the config by running "nginx -t"). For the record, I have used nginx for years and this has never been an issue. Anyway, I am generally impressed by your other ideas in Mongrel2 and happy hacking :)
- zedshaw 16y ago
  Using a SQLite database doesn't mean you can't use fabric, so it's not going to work better or worse. You see the difference? So far nothing you've said invalidates sqlite files or sql as a configuration interface. The version challenge points directly at what's wrong with config files: they aren't accessible to automation. If you can't even do this very simple thing from one programming language, then it means you can't do other things easily.
  - amix 16y ago
    If it isn't broken, don't fix it and I don't think textual configurations are broken, i.e. you are solving a problem that really isn't a problem. Based on my experience with Flipper (a MySQL master-master tool), SQL configurations are very hard to maintain and understand.