I’ve made the decision to shut down PyHost.
It’s not been an easy choice by any means, but I’ve been toying with it for a while and felt I should explain myself.
When I first started PyHost I was wrapped up in dev. Completely consumed by it. I spent my time trawling through dev twitter and brainstorming project ideas to make money off it and start my own business. At the time, that was what I wanted to do with my creative energy, and so I burnt the candle at both ends, while not knowing what I was doing, to get PyHost built. I worked on it tirelessly. This was misguided for one main reason: I had no idea about Django or deployment. I’m willing to admit that.
As the years have passed I’ve learnt a lot but still feel like it’s an area where I fall down. What PyHost became because of this was a brittle and confusing system to work on and use.
The combination of not being happy with the project and not having the time to dedicate to fixing it has begun to weigh on me. I have other interests now and no passion for the project anymore, hence my decision.
The servers will be up for another couple of weeks and be turned off on Friday 11th Nov.
With PyHost closing down, you’ll likely be wondering if your servers will be removed. They won’t be brought down. Just as has always been the goal of PyHost you own the servers. If you are hosting a site which uses a custom domain name, then your site will remain live. If you are using a PyHost subdomain (e.g. something.pyhost.io) then it will be brought down since the domain routing happens on PyHost’s servers. You can update the server’s Apache config to use a domain you own.
I still love the creativity that dev allows and will build things, I’m pretty sure, until my hands can’t type anymore. This is by no means the end of dev for me, just the ending of a chapter which I’m ready to leave behind.
Thank you if you’ve stopped by PyHost or even given it a try. What I’ve learnt along the way has been invaluable, and PyHost as a project will always hold fond memories for me.