Cachet 3.x Announcement #4342
Replies: 51 comments 76 replies
-
I would be interested in this. |
Beta Was this translation helpful? Give feedback.
-
This is awesome news and never too late, I constantly come back to this project as I work in the enterprise and we have the need for self-hosted status pages (re: Atlassian is f***ing expensive). |
Beta Was this translation helpful? Give feedback.
-
That's nice 😀🥳 |
Beta Was this translation helpful? Give feedback.
-
Welcome back <3 |
Beta Was this translation helpful? Give feedback.
-
This is great news, but sounds like that it will take a while (considering the long wait and silence I guess this doesn't matter). Unfortunately other forks weren't successful either and I hope that 3.x will be a great comeback. Would love to help but me being an Angular guy and also time is always an issue. But I wish you all the best with your "baby" and hope you can continue where you left and bring it back to live soon. <3 |
Beta Was this translation helpful? Give feedback.
-
I can test Cachet in future for you |
Beta Was this translation helpful? Give feedback.
-
Very nice to see a good open source project like this being back to live again. |
Beta Was this translation helpful? Give feedback.
-
Great to hear the project is back alive! |
Beta Was this translation helpful? Give feedback.
-
This is awesome, all the best for the project. If you need any help maintaining the project please keep creating Github issues about your plans. Once we have a good base code, all of us can contribute. |
Beta Was this translation helpful? Give feedback.
-
Happy to test and proof-read documentation. Moved to another open source status page system because this one wasn't being maintained, then when that stopped being maintained went onto Atlassian (which is quite restrictive on it's customisation unless you go for the $399 per month plan). Would be great to be able to go back to the first choice again. Are there plans to do a docker/container release of the new version 3.x? P.S. The blog link is dead on the Cachet HQ website (cachethq.io) |
Beta Was this translation helpful? Give feedback.
-
Wonderful news!!! I would suggest definitely leaving the door open for translations. I suspect there is a large amount of interest globally. I’m happy to help test! |
Beta Was this translation helpful? Give feedback.
-
Welcome back!! Happy to help pitch in wherever I can. |
Beta Was this translation helpful? Give feedback.
-
Welcome back! To start of good with enough cups of coffee, I sponsored the project through your personal page with a $100 funding. |
Beta Was this translation helpful? Give feedback.
-
So happy to see you back, we all missed you so much. Congratulations on having a kid! I'll throw a lot of money at you to keep this going as soon as we're able! |
Beta Was this translation helpful? Give feedback.
-
It's been a long time since I've been in the Laravel community but I've been itching to get back in it in some capacity. I still have need for this even to this day and would love to see some of it come to life. I'm willing to join in on the development process in any capacity. Do you all have a Discord community you are coordinating in? If not, I'll be happy to help set it up since I run Discord communities on the side. |
Beta Was this translation helpful? Give feedback.
-
I am a bit late to the party here, really glad to hear that this project is catching some fresh wind again! :) I would be more than happy to offer my assistance and time to lend a helping hand to get this baby on its feet again. While the backend stuff isn't quite my cup of tea, I would be more than happy to help with documentation (in English), and translations to Norwegian - as I do really hope that translations will be kept in the new revamped version. Another area I can contribute to is testing, Docker-related stuff and ways to interface the new Cachet with PowerShell for those using Windows. Personally, I would also love a role for Ansible to automate the deployment, which I can help with. |
Beta Was this translation helpful? Give feedback.
-
There's a lot going on here, but I have some plans to my future and contribute to this project seems to fit it. I can help to document and translating to Brazilian Portuguese, if no one has offered before. Or I can do anything that I'll be asked and could do o/ |
Beta Was this translation helpful? Give feedback.
-
What is the planned release date/target for the beta? |
Beta Was this translation helpful? Give feedback.
-
Happy to help with testing! Love the vision and drive here. Starting to dive real deep into self-hosted microservices, and would love to contribute to maintaining and testing Cachet @jbrooksuk. |
Beta Was this translation helpful? Give feedback.
-
Is there a roadmap for when and how something will go online? |
Beta Was this translation helpful? Give feedback.
-
Hi, just wondering if there is any updates on how this project is progressing? :) |
Beta Was this translation helpful? Give feedback.
-
I would like to contribute to the project, if you still need volunteers. |
Beta Was this translation helpful? Give feedback.
-
@jbrooksuk After updating to 2.4, when we create an incident the page generates error 500. |
Beta Was this translation helpful? Give feedback.
-
Does 3.x plan to support webhook? As we want to notify our online users when publish an maintenance on Cachet, it seems 2.x still not support webhook right now. |
Beta Was this translation helpful? Give feedback.
-
I've an issue regarding mail, i can't change the mail from address, every time i refresh it, the default address is shown. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone? Isn't 3.x available to install yet? Any ETA? Thanks |
Beta Was this translation helpful? Give feedback.
-
sooo any update on the progress of 3? is it going to support php 8.3 and laravel 11? |
Beta Was this translation helpful? Give feedback.
-
Hello, I read your conversation with another poster above about having a webhooks feature for 3.x. I was curious, is it 100% in the works, can we expect to see it sometime soon? Love the work you and the contributors have done so far, keep it up! |
Beta Was this translation helpful? Give feedback.
-
Hey, I think it would be neat to see some sort of SSO SAML / LDAP / IP allowlisting, or any other additional form of authentication. Thanks again |
Beta Was this translation helpful? Give feedback.
-
It has been now over a year and I had to ditch php7.4 support once and for all. I'm a "nobody user" with a very basic cachet setup, I could migrate to 3.x now with a few issues which I could resolve: I couldn't find any migration guide and docs are not fully helpful yet, so I took all the pieces I found and put them together. # cd into cachet
# checkout to
git checkout .
# I removed vendor and the cache manually (whole env was broken due to only php8.1 - php8.3)
# rm -R vendor/
# rm -R bootstrap/cache
# checkout to current state
git checkout .
# switch to 3.x
git switch 3.x
# NOTE if you come from an older system, you might have to install latest composer and or use a different php version
# run composer
composer install --no-dev -o
# or force a given php version `/usr/bin/php8.2 /usr/local/bin/composer install --no-dev -o`
# Migrate to new .env
# I simply took the .env.example and filled in my old values from the .env
# any obsolete keys were removed
# I chose:
APP_ENV=production
APP_KEY=<oldkey>
APP_DEBUG=false
# also I had mysql and wasn't sure which key was the right one:
DB_CONNECTION=mysql
DB_DRIVER=mysql
# email keys have slightly changed
# clear everything to be sure
php artisan config:clear
php artisan cache:clear
# then run php artisan
php artisan vendor:publish --tag=cachet
# now migration...
# In my case, I had to change the collation of all tables to `utf8mb4_unicode_ci` (it was somethig with utf8mb3 before)
# I renamed the user table, because in my case the migration wants to create a new one
# The settings table migration failed, I had to empty the table
# then run migration (say yes for production)
php artisan migrate
# it should pass
# I then migrated my two users back :)
# And some settings (through DB and frontend)
# If the frontend is not working (lots of errors in console), then try to install / upgrade the filament stuff:
php artisan filament:install
php artisan filament:upgrade Haven't fully tested it yet. But works for my usecase: |
Beta Was this translation helpful? Give feedback.
-
Hey everyone,
It’s been a while 👋🏻
I want to start by saying that I owe so much to Cachet. My career at Laravel being just one of the many things I'm grateful for.
9 years ago, I released Cachet while working on another SaaS application. Cachet became my primary focus and it reached many heights. Fortune 50 companies were using it, it reached #1 on Hacker News, topped Product Hunt and casually sat in GitHub's trending projects for weeks like it was no big deal.
5 years ago, I sold Cachet. The buyers and I had big plans for the project. Unfortunately, those plans never came to life. I personally hold myself responsible for that. Within just a few weeks, my brother passed away and my first daughter was born. After that, I never felt right working on Cachet.
Fast forward 5 years and things have changed dramatically. I'm now in a much better place personally, I love my job at Laravel, I've launched a new product, Checkmango and I have a deep, burning desire to get my baby back.
A few months ago I mentioned in an issue that I was speaking with the owners to see if I could get Cachet back. It's taken us some time but we're now at a point where I have something to announce.
Cachet, is once again, mine 🎉
Immediately I have thoughts… Maybe I'm too late now? Maybe too much time has passed? Cachet may've blazed the way for open-source status page systems, but who's even using it anymore?
Honestly, I don’t think that’s a problem. I still get several emails a week about Cachet and the website + repository receive thousands of visitors a month. I firmly believe that we're in a good position to get Cachet going again.
So what's the plan, James?
Looking through the codebase is quite painful... I'm going to rebuild Cachet with Vue.js, Inertia, Laravel 10.x and Tailwind.
The current 2.4 branch of Cachet is old. It's easier to rebuild than it is to upgrade at this point. As much as I want 3.x to be 100% compatible, there are some things we need to keep in mind:
This isn't going to be an overnight job. It's going to take me a while and you'll be able to follow along too. Shortly, I'm going to be cleaning up the repository:
I’ve put real money into making this happen. This is happening.
Let’s make this super collaborative. Can you help? I’d really appreciate it if you could help me re-build Cachet. Here's what I'm looking for:
cachethq/docs
repository with VitePress installed and ready for the old docs to be migrated.I guess that's everything for now. Let me know what you think and importantly, whether you can help.
Thanks ❤️
Beta Was this translation helpful? Give feedback.
All reactions