Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
The next version of the application addresses the many requests I received last week. Of particular interest to the community is the possibility to manage multiple Nginx instances via NginxUI, as well as the ability to reload an nginx instance after it has received a new configuration. The challenge will be to distinguish between a bare-metal and a docker runtime environment. There is a need for user management. Maybe it is time to connect a database which allows a more complex setup for the application. I am still undecided about the choice of the database. My default would be a NoSQL database like MongoDB. But I am currently experimenting with embedded document stores. I still have to decide which technology I will use with the knowledge in mind that this will define the future development of the application. The community has also already set up great PR like an ACE editor that enhances the configuration of the files.