Dear Chevereto users:
Within the years, the use case for Chevereto has been shifted a lot and it has evolved to a point where it has a very distinctive appeal shaped by my way of interpreting the user needs around it. Chevereto turns 13 with a install base of somewhere near 20,000 public installations and I’m still just one guy in development.
My goal with Chevereto is to turn it into a distributed project around the need of self-hosting media content. I want to turn Chevereto into a large media sharing solution, on pair with the same offering of closed services.
I also want to stop being one guy behind this. To achieve that, I’ve been working for years in what I’m about to announce.
Today, I celebrate another year of Chevereto by announcing the initial development of the next major version: Chevereto V4.
The two-years project
During the last few years V3 has been pushed to maturity to allow the preparation of its replacement, a process that I started in May 2018 with the beginning of my own framework project.
I’m a self-taught developer, my learning process is by building stuff over and over until I’m happy with the outcome. There was no reasonable way to improve Chevereto without improving my own skills so the most challenging stuff that I could think was to develop a framework. I also started using Linux on the desktop as my goal also requires serious devops skills.
As I’ve learned that most of my development journey will be very lonely, I focused in creating a clean framework that will allow me to grow for decades with a minimal human footprint required, with the artifacts that will allow me to provide the tooling needed to easily extend my stuff. That way, I will stop being the only gateway to add new stuff to Chevereto, allowing it to grow at wild.
Sell me the thing!
Actually no, it is still not reasonable to consider the framework for a production project at this time. It should be useful for those wanting to pimp up their Chevereto websites with the V4 awesomeness.
👍🏾 The Chevere Framework is now in late stage and is already available for testing.
By getting used to the framework not only you will be able to create addons for Chevereto, but your own totally unrelated softwares.
Chevereto V4: "Big Picture" is now under development
Official development for Chevereto V4 has been fixed for this date. It turns out that nowadays I’m using the framework for internal systems and I feel that is about time to star working in actual application implementation. That way I can also add more examples.
V4 changes everything so I named it "big picture". The name is awesome, because I can name versioning like "biggie pic", "foto grande", "La Bomba 4", and so on, just like the cools kids.
This version will carry a huge shift in the project by introducing a new distributed application architecture, with support for third-party addons, and a headless API. It also changes to a common extensible Open Source base edition, for which I will create an store to ease the process of delivering code for Chevereto.
Just like Envato! But without eating developers a small fortune. I’m just a guy remember? 😘 I don’t need that much to be fine.
The development is live now at chevereto/chevereto where you can see the ongoing progress and contribute with it.
Based in my horrible way to measure time, I could say that "it will take a while" to have it ready for being used in real projects. I guess that the time needed only to complete the replacement of V3 to V4 could take up to 24 months. Of course, this is accounting all what V3 currently does.
The base edition, similar to the current Chevereto-Free feature set, should be available within 12 months being very optimistical and remembering that is just the basic feature set.
No surprises here, it is a 13 year old project, is quite big for one person.
Please note that I’m assuming zero collaboration in my timing measurements. It will be ready way faster if I more people can help me out!
There’s a lot of stuff in V4’s big picture that I will implement progressively during all the lifespan of V4.X.
- Infrastructure provisioning
I want to provide the server model for production. No more messy servers configurations.
- Support layers
I’ve the intention of providing more support layers and I want to certify others for this job. I don’t want to control the support around the software, I want to distribute it.
- Third-party plugin store
I want to allow others to provide addons for Chevereto. A store for services (free, paid, and subcriptions) around the software.
- Any media-type support
Support for any media type is a must.
- Log reporting
Automatically notify me that there are errors so I can be more proactive fixing bugs.
All the changes can be summarized in that Chevereto will evolve from a image sharing website to a universal media solution, that will allow to create anything from a simple image sharing website up to anything you may need like a photo portfolio, a Flickr-killer (please do) or even add media sharing to your existing application.
I also want to change the business, focusing more in supporting services, customizations and consulting. The mojo of V4 are long lasting standards allowing your application/business/hobby/profession/comunity to grow with confidence with my software in the back.
You can contribute to my work in many different ways.
- Purchasing V3 (you will get nifty gifts for V4)
- Coding (review, testing, add stuff)
- Helping others
- Telling others about it
Donating (money, servers, devices or any asset)
I appreciate everything, for real. Now in pandemia tiempos help the indie devs.
Chevereto exist because of its users. Many thanks to all those who use (or used) Chevereto, and special thanks to those who have to deal with my annoying mood everyday. I know.
Keep using my software, it encourages me to keep doing my own rockets and planing my own wacky trips. Don’t know yet how tall this can go, hope to never find out.
Thank you all, for letting me live from doing my own software 😘.