Hi guys,<p>This is very initial release of something I've been working on for the last few months.<p>Qpackt is an open source, Rust based, web server with several interesting features:<p>1. Basic analytics without tracking cookies.<p>2. Can serve multiple versions of your website. This can be used to A/B tests, track users' engagement coming from different sources or gently roll users to the new version.<p>3. Auto-fetch (and renew) SSL certificates.<p>4. GUI configuration (mostly ;) ) for the ease of use.<p>It's missing a lot of features and it's not production ready yet. At this point I'm looking for opinions.
Right now we use plausible for analytics and don't have something for A/B testing, but if we had the bandwidth to add it then it would seem like this would work well. It's great that it is written in actix as well since that is also what our primary backend uses.<p>We use Astro for our landing page so I guess that to use this we would have to write some build step for getting multiple index.html files to server within the API. That seems very possible and not too difficult though.<p>I don't know, I think a polished version of this could work. I don't see any real reason for why it wouldn't, it seems objectively useful.<p>My main concern would be that most people who aren't baby unprofitable startups like Trieve (lol) are probably using WordPress, Ghost, or some other CMS and would want their A/B testing to work by plugging into that rather than needing to create multiple index.html files. I don't even know if people with those kinds of websites could do that at all.<p>Anyways, I guess the question there is whether or not Qpackt is useful when you have a CMS instead of a packed file for your site?<p>Then secondarily, would companies/projects without a CMS pack multiple index files and use Qpackt or switch onto a CMS with A/B testing functionality?