Sure don’t worry, I try just to keep the discussions clean 
1 Like
Question @Ctek concernant ajax does it used to get an upload widget/plugin in nethgui ?
@davidep i miss it
Hi Stephane,
I’m not sure what are you asking…
If you ask about a upload function, then yes I’ve added a upload function to the backup Config module.
(check the pictures from the posts above, in the top left corner of the image you can see the upload field)
For now there is no danger using the upload function, just that I always want to do a little more to be sure that it is ok.
Yes bogdan it is what I was asking for, an official upload widget
1 Like
now the only thing is to test it and see if it works.
On my test server works ok.
I will try it ASAP. I have had the worse bad week at work since really a long time 
Sorry to hear it… I have the same struggle for 2 months 
Its because of Q1 when all things breaks loose, everybody tries to do all the things at once
Let me know if you have issues with the BCM.
looking to your MR I can see the amount of work 
1 Like
I miss it too 
We’ll need one at least to upload the server certificate…
I think I’ll start with the basic PHP/HTML features, as Bogdan did: $_FILES and <input type="file"...
I don’t know how much code it’s going to require. At least we could set up CSS under a Nethgui widget…
1 Like
I’d like to revive this topic, how can we close it? I don’t like to throw away all this effort
1 Like
If possible, I’d split @ctek’s pull request into two parts:
- changes required to the nethserver-backup-config package,
- user interface, to be packaged in a separate RPM for NethForge
2 Likes
Davide, what is the rationale behind the split ?
I mean, the UI needs some things from the way the BCM works
Basically you are splitting the package and removing all the functionality from the UI.
I guess that doing this you will only keep the multi archive creation and check.
And, If the UI will be in a different package, what will the reason be ? If you want to install the BCM you will need both of them .
I’m not sure that i follow the process why to be separated. Maybe you can give more details ?
1 Like
I still can’t merge the UI part in nethserver-backup-config mainly because the style and behavior (i.e. dialog boxes, table styles) are very different from other core modules.
I see two good reasons to merge the PR on two separate packages:
- we consolidate and make available an API for “multi-archive creation” without introducing big changes in the core UI
- we’d allow everyone to choose from the “Software center” what is the best UI for his purpose
If you agree with me, I can make an attempt of building the two RPMs!
Hi Davide,
I understand now what you wanted to say with splitting the package.
I have no problem with building two packages.
The only issue i can see is if you use the “default” UI of the BCM you will lose some functionality.
But let’s see how this goes.
PS have you tested the BCM on your system ?
1 Like
Thank you for supporting me, Bogdan!
The Enterprise version has already a similar feature that uploads the config backups to the private Nethesis cloud.
Therefore my goal is supporting both UIs (and whatever future one) with a common API.
Yeah of course I did it to give an attempt at the merge!
1 Like
The PKI module in nethserver-base has now an upload field for custom certificates. Have a glance at the module and view code!
It required a fix to the ajax library in Nethgui to work.
1 Like
Hi Davide.
Just let me know when you have the packages ready, to give them a test from the Software Center.
4 Likes
nice feature
2 Likes
Hi Bogdan,
I’ve just pushed an experimental package to nethforge-testing, please have a look at it
Probably there are some things to fix; at least I managed to re-pack your code without requiring changes to the core package. Now we can see how to enhance it!
3 Likes
@Davide, I’ll give it a try this on a fresh NS instance and let you know.
Thanks for you work on this package!
4 Likes