Upcoming: v15.02 - VestaCP, Cyberpanel, Automatic Updates

[Aetherinox]

v15.02 Update

Just wanted to throw out a quick update, as to not confuse anyone. Originally, there were plans for the next major release to be v15.10, however, that has been shifted to v15.02. The reason for this is to keep up with the original versioning pattern that CSF had before. A simple increment for each release.

---

Cyberpanel

It appears that the developers over at Cyberpanel removed ConfigServer Firewall as their firewall solution. Which of course is expected since the developers for Cyberpanel figured that was the end of CSF. Plus, a new developer starts working on it, and I imagine there's trust concerns. It happens.

However, I will continue to support it. So if you'd like to opt and use CSF as your firewall instead of the new option, you have that choice.

Integration Fixed

I went over the code from the last few days and made sure that v15.02 fixes the issues with Cyberpanel integration, and it is currently operational again.

Installation is the same as before, much like everything else, and the same goes for updates. I tried to keep as much backwards compatibility as possible so that it's available for as many as possible.

---

VestaCP

VestaCP switched over to React in their v1.0.x release. This broke CSF's integration. You could still access the /list/csf page if you manually entered the URL, however, you would not see the VestaCP header.

This has since been fixed, but with a some notes to address

New Structure / Menu Button

VestaCP on React means that the templates are built and output as minified .js and .css files, instead of their original structure which consisted of simple PHP and HTML static files. This makes it significantly more difficult to modify the header to re-add CSF to the navigation menu. Along with a hash being assigned to each generated file, and not wanting to violate the purpose of that.

Unless we re-build the template ourselves, which seems like a drastic measure, the only other option is that I wrote up instructions on how to do it yourself which can be found at: https://docs.configserver.dev/install/install/#add-csf-to-vestacp-menu

This could easily be solved if the developers simply add a conditional menu item to their header template and build it, but VestaCP has been without updates for quite some time, and that leads me into the next point ...

Lack of Updates

CSF is about security, and not about making your attack surface larger. With this said, VestaCP has over 20 known vulnerabilities / exploits, and as much as I don't want to speak against software, I would highly recommend people re-consider if they want to use VestaCP at this moment in time. If VestaCP is updated in the future to address these issues, great. However, my logic is coming from a security stand-point, and ensuring that users don't open themselves up.

I'll continue to keep it operational, but I do not want to consume a lot of time on a product that doesn't seem to be getting support.

Header Integration

I have re-integrated the header menu into CSF for VestaCP, so you can now jump to other pages from the /list/csf page.

---

Dark Theme Users

The dark theme will be back. However, core functionality is a higher priority, and with several of the integrations not functioning properly, I chose to put the energy into that first. Bringing the dark theme back however, is definitely on the list.

I have re-implemented the footer that the original dark theme had, and re-added the Light / Dark theme switcher. I just haven't added the CSS classes yet. It requires a lot of careful work and testing to ensure I don't break the appearance of one integration, over a cosmetic feature that is a "nice to have", and not a necessity. I want to do things slow and right, and not throw out a lot at once and people start getting an unstable product.

This also includes the login interface that was originally part of this repository. It will definitely be returning.

---

Updates

As most already know, the update servers are back online. Everything is as it was with the original developer's website. I have added a help page to the download service:

• https://download.configserver.dev/help

I have also spoken to a few companies who reached out to me to offer services such as reputation identity which CSF originally had integration for. I have been working on that along with everything else. But the priority is using these services, and not having to jeopardize security or privacy. No data collection, no additional ports, etc.

---

Pre/Post Script Support

We have added Pre/post integration support. If you have existing scripts that you load with CSF, they will continue to work. No changes needed. It's just a built-in feature now. I have written documentation on how it works at:

• https://docs.configserver.dev/usage/prepost/

---

Additional Notes

This is already long enough, and there are a lot more things that were done in preparation for v15.02, but I have covered the main points. A change-log will list the rest once v15.02 releases.

However, CSF has long been an established and stable application, and I don't want to grind my foot on the gas and start changing that trajectory. If it's not broke, don't fix it. There are routes to making it even better, but the core functionality should not suffer. I still use this app every single day, and I wouldn't want it messed with in a dramatic way.

Contributing

A final thing to ensure the invitation is out there. I decided to do this on Github for

1. Transparency
2. Collaboration potential

There has been talk within the CSF community that others have been interested in throwing out ideas, and this repository is more than open to it. Code contributions are also welcome as long as it doesn't jeopardize the end-user by either opening them up or breaching privacy, and the code is logical, tested, and either solves a problem or adds benefit for the end-user. New features with a toggle / bool should be opt-in only, and not force the user into the feature without their knowledge.

[opsintel]

How does one get rid of that flashing heart at the bottom? Its a huge distraction and really makes this repo look sketchy.

[Aetherinox]

See response below.

[eric418hk]

I am a sponsor but I agree that the flashing heart is a distraction. I ended up hiding it with adblocker. I don't mind it there if it is a static heart but flashing is actually affecting my attention.

[Aetherinox]

I'll switch it out today. The beating part isn't had to kill. Just CSS anim and I'll add a few settings

• Remove animation
• Remove if already sponsor with key added
• Ability to hide in csf.conf

I don't even notice it when I'm in CSF. But then again I have an oddly shaped monitor. Or maybe my eyes are just losing peripheral vision lol

Made an issue:

• 💡 Feature: Make changes to sponsor icon #72

[eric418hk]

Yes, it is logical to just hide it if sponsor key is already defined. Thanks!

I think most people would be completely fine with a static icon, just the same as most of the other open source projects. But no animation.

[Aetherinox]

Alright, made the changes.

• Sponsor icon will not show if you have provided a key
• No more beating heart
• Can hide the icon in the settings with SPONSOR_HIDE_ICON = "1"

[Aetherinox]

The sponsor icon? I'll have to add a setting today so that it can be toggled off. Once I drink my coffee and wake up, I'll look into it.

That icon is there as most other open-source apps do in some form, for anyone who wants to contribute financially to the project to help with server costs required to maintain it. We use multiple services to keep the process going.

And I've always told people, it is 110% optional. It doesn't change the fact that the app will continue to remain free.

If memory serves me correct, the original CSF had a section of the interface dedicated to contributions, which was removed, and a simple icon was put in place.

[theking81]

☕ Coffee rules!!!

[Aetherinox]

I just looked up the Breville Barista Express.

That is one pretty machine. I bet the coffee is great.

[opsintel]

15 cups a day, so I totally get it. As for the Breville, it was a starter machine for me long ago. They've made many improvements over time, but my chief issue is with the grinder. You can play with it, and at times, depending on the beans, you can get a good grind which will work. But if you use beans from various sources (I buy beans every two weeks from various roasters) then you will endure problems with the grinder in being able to "Dial It In" so to speak. This dialing in process is tough because you can waste half a bag of coffee just getting it right. The other part is the pre-infusion process. I found that holding the brew button in until you see the pressure dial ramp up to 1/3 the way up and then releasing it would give you a decent amount of crema in the allotted 25-30 second time. The other issue is time. Its 18 grams of grind in, and 36 grams out in 25-30 seconds. The Breville doesn't work well in that area. If you don't pre-infuse using the button, then it will end up not giving you the correct timings and grams out (too runny (comes out too fast) (or too tight hardly comes out at all). That all being said, if you place your zeroed out scale with your cup on it, and then pre-infuse, and then release after the pressure goes 1/3 the way up (You want your brew pressure to go to the 12 o'clock position after you release the button) for the right brew, then you're pretty much good to go once you hit 25-30 seconds. The scale should show anywhere from 36 grams to 40grams out or in the cup. Its a crap shoot depending on beans, grind, and tamping into the portafilter. Things they don't tell you lol.

[josh-jday]

I just looked up the Breville Barista Express.

That is one pretty machine. I bet the coffee is great.

Yup once you've got the settings dialed in it's pretty great, easy to maintain and consistent great cups of joe every time. But I digress, at risk of sounding like a salesman. Great work continuing the CSF legacy. I enjoy following the continued development. have you set up a donations link yet?

[opsintel]

The problem with it is chasing it. After awhile you start thinking hey, maybe I need a bigger more shiny buggy. And that's where the addiction to the entire process leads you. From great expensive portafilters, to expensive shower screens, to diffusers, to tampers, to everything one can get, including a new machine. And then of course after awhile you see a better one come out, one that has a big screen on it with thousands of different profiles that can be had (The Decent). Then there are single handle pump style machines, commercial machines, machines that are plumbed in, more and more and more. Then beans come next. Gee, what would those expensive cat shit beans be like? How about those beans from this country or that country or even the most expensive beans in the world. It just goes on and on and on.

As for CSF, yes thank you for sure on the maintainer. I just happened to need it 12 hours ago and ended up here. The flashing heart was doing something to my eyes or something, I don't know. After awhile I was going to use the 14.x version I saved just to get rid of it. I then started doing an inspect to find it, did a few things, looked into the CSS files, I see heartbeat, but not the ax-heartbeat image, its not located in csf image folder. Then suddenly I decided to just block the element and it was gone lol. I don't mind the supporting of the people behind it, but I've always found that having something like that flashing at you with no way to remove it makes it somehow not a great thing. I understand people need to get support for work, and approve of that, but I've always felt that those who are going to support will do so without flashing things that they need to remove because its a distraction. Just my 1 cent opinion, of course YMMV.

[Aetherinox]

@josh-jday Yes. They are in the lower middle right of the github page.

But as I tell everyone, don't feel obligated. The app will continue to remain free: https://buymeacoffee.com/aetherinox

It just helps with the server costs and the Cloudflare limits for workers.

But you all are more than welcome. I use CSF just as much as many others, so it's vital to my daily setup.

@opsintel I can definitely tell you I chase coffee sometimes. It has become a hard habit to break. Sometimes it does nothing, so I have to up it. I love the stuff. I don't even really drink it for the caffeine, it's the taste. A great dark roast coffee, sometimes black. Or when I feel "freaky", I put a creamer in it.

The beating heart will be gone in the next update. Just finishing up a few things first. Changelog is here:

• https://docs.configserver.dev/about/changelog/

I didn't even add the beating heart because I wanted people to see it more, I thought the beating with the icon just looked good.

It was actually inspired by the developers of mkdocs material theme.