Seeing sync + proxy running together at the same time for the first time in Indie Web Server… getting closer :)
Seeing sync + proxy running together at the same time for the first time in Indie Web Server… getting closer :)
Indie Web Server v9.1.0 release
This is a minor release that brings better error handling.
https://ar.al/2019/04/30/indie-web-server-9.1.0-better-error-handling/
Indie Web Server version 9.1.0 is a minor release that handles the following two, related (and common), errors more gracefully: Trying to enable a web server daemon when one is already enabled Previously, this would succeed even though the earlier server would continue to be served. Now, it gives an error and instructs you to disable the existing server. Trying to enable a web server daemon when some other service was using port 443
Indie Web Server v9.0.0 release
* Mostly housekeeping
* Breaking change: proxy syntax
* Drops Windows support (use Windows Subsystem for Linux)
https://ar.al/2019/04/29/indie-web-server-9.0.0-housekeeping/
I just released Indie Web Server version 9.0.0. This is mostly a housekeeping release and nearly all the changes are under the hood. Maintainability I refactored the command-line application quite extensively to pull out all the commands into their own modules and remove any redundancy in the command-line argument parsing. The whole thing is far more robust now and ready for the two new features I’ve been itching to add.
Indie Web Server 8.2.0: Cascading archives for an evergreen web
https://ar.al/2019/04/20/indie-web-server-8.2.0-cascading-archives-for-an-evergreen-web/
I just released version 8.2.0 of Indie Web Server. This version brings with it a cascading archives feature to make it easier than ever for you to support an evergreen web and not break existing links as you evolve your sites.
Cascading archives for an evergreen web. I just released version 8.2.0 of Indie Web Server. This version brings with it a cascading archives feature to make it easier than ever for you to support an evergreen web and not break existing links as you evolve your sites. Easier than the 404 to 302 technique for static archives Indie Web Server already had native support for the 404 → 302 technique where you convert 404s into 302 redirects to earlier versions of your site, thereby preserving those links.
This site now runs on Indie Web Server
https://ar.al/2019/04/17/this-site-now-runs-on-indie-web-server/
🐹🥜
In the interests of eating my own hamster food1, I just switched this site from nginx to Indie Web Server. The only complication in the process was that I had to update the hostname of the server to match the domain name. Otherwise, the whole process was basically as follows: # Disable nginx. sudo systemctl disable nginx # Copy the web directory into a more human-sounding place # (not necessary but I like it better, so there!
Just switched my personal web site https://ar.al from nginx to Indie Web Server.
Took a few seconds.
What’s Indie Web Server? Check out a two-minute introductory video here: https://ar.al/2019/04/16/set-up-a-live-static-personal-web-site-in-seconds-with-indie-web-server-8.0.0/
If only everything was as simple as setting up your own web server…
Coming soon ;)
Just released v6.2.0 of Indie Web Server
https://ar.al/2019/03/10/indie-web-server/
All telemetry and the artificially introduced and privacy-eroding email address requirement for Let’s Encrypt in Greenlock.js removed via my ACME TLS fork (including in submodules).
Why yes, it was just like cleaning a sewer now that you mention it.
Indie Web Server serving my blog over a TLS tunnel via ngrok. Indie Web Server1 is a secure and seamless Small Tech personal web server. Use it to seamlessly serve your personal static web site in development and production or build your own dynamic web app on top of it using JavaScript and Node.js. Indie Web Server is as easy as it gets. Features Zero-configuration – It Just Works 🤞™.