-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CP Update Module #71
Comments
This would be a cool feature for future use anyways! Many web based services use this method now so I see no reason why we can't have something like that. :) |
I think this would be an awesome addition. From my previous experience, uploading / upgrading certain tables always threw some sort of error when you go through the install / update process. This would make things a little bit more seamless. |
This feature would be a welcome addition. Even if it just would show the updates available that would be sufficient, but making it a one-click-update system would appeal the masses more. Were you also meaning to add the rA update feature? If that was also the idea, I think it would also be a welcome addition. |
I'd definitely include this module so that FluxCP admins can update their copies when they're able to. Honestly, this is pretty much a must these days. |
Just a quick update; I've begun to work on this. It could take a few days, it could take a few months. There are currently 3 Pull Requests that will either be merged or dismissed as the last set of changes to our version of FluxCP before the Update module is introduced. All future code pushed to github will be obtainable via the Update module with a single button click. Nice and easy. There will be several things that server owners need to keep in-mind before beginning to use this process:
There are many users who seem to think they can just go changing code willy-nilly because they know a little php, but in most cases this has introduced bad coding standards, vulnerabilities and headaches for people who actually get hired to clear up someone elses mess. The module will essentially keep the entire CP in a single state, where customisations to the core code are removed. You will need to keep your customisations in the appropriate place, as this is how FluxCP is designed. More details and instructions on how to migrate your existing installations will be made available closer to the time. |
Originally, the FluxAdmin module showed the latest FluxCP commits and PRs, along with information about the latest commits to rA too. On my version that I never managed to publish, was a backup and update feature.
Backup was pretty simple; the CP would create a .zip of itself containing all files and SQL data. It was meant to help users who needed to move their website from one host to another.
Update feature literally updated FluxCP to the latest version available on Github. This had two methods, one button ran similar to exec('git stash && git pull && git stash pop'); while the other would download a tag and unpack. The install screen would be shown if new sql data needed creating.
Essentially this was designed to save users time and effort updating. It became abit useless since no real updates were being produced at the time but i still used it to check on commits on FluxCP and rA (mine had rA git update code as site was on same vps as server, which is the other main reason it was never released).
Thoughts?
The text was updated successfully, but these errors were encountered: