Cool!!

I had a look but could not find my network profile, there were just a few.

And I could not find where to log in. I mean in order to edit your own profile.

I also see the connection was not encrypted, so I went to https://jefe.tk/ but my browser did not trust the certificate, I told it to trust it and took me to a different page!

Thank you!

A very nice improvement would be to detect which routers are 4MB and which ones are >4MB (this can be probably extracted from the imagebuilder or sdk files). Then allow only the flavors which are available for such flash space.

On 10/11/17 2:21 PM, pau wrote: Nice idea, however currently there is no generic way to find the maximal image size. I see two solutions: * parse https://lede-project.org/toh/start * add profile row 'max_imagesize' where the image-server logs the minimal size of a faild build request.

The information will be returned on profile request. However, building a too large image, jefe.tk will inform the user to retry with less packages. This could already be a hint to choose a smaller flavor.

That would be consistent in terms of how the IB does things and would allow the update-/build-server to extract the flash size in the same way it also gets the information about the available profiles.

Hi all, Paul it's really great that you are working on this. I just want to note before it's too late! that Jefe in spanish means Boss. A more appropriate translation would be "Cocinero", but I'd like to propose that if this tool will replace our existing firmware chef, whe just call this chef, and explain it's a complete rewrite of the previous project. Or chef2 ? We talk about the firmware in many places old and current, so if this will be the natural replacement, it seems best to inherit the name also. Please other devs state your opinion on this. Cheers! Nico On 10/10/2017 10:40 AM, Paul Spooren wrote: _______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

I agree that an imagebuilder.libremesh.org (that then migrates to imagebuilder.openwrt.org ) would be great. Regards, On Fri, 2017-10-20 at 00:06 +0200, Paul Spooren wrote: > Hey Nico, > > yea gosh I totally messed up that name. I personally hate adding a 2 > at > the end, if it works for you please add chef.libremesh.org to the IP > of > jefe.tk. > > As this service may become more "official", maybe > imagebuilder.libremesh.org would be the international solution. > > Best, > Paul > > On 10/19/17 11:59 PM, Nicolás Echániz wrote: >> Hi all, >> >> Paul it's really great that you are working on this. >> >> I just want to note before it's too late! that Jefe in spanish >> means >> Boss. A more appropriate translation would be "Cocinero", but I'd >> like >> to propose that if this tool will replace our existing firmware >> chef, >> whe just call this chef, and explain it's a complete rewrite of the >> previous project. Or chef2 ? >> >> We talk about the firmware in many places old and current, so if >> this >> will be the natural replacement, it seems best to inherit the name >> also. >> >> Please other devs state your opinion on this. >> >> >> Cheers! >> Nico >> >> >> >> On 10/10/2017 10:40 AM, Paul Spooren wrote: >>> Hi all, >>> >>> as chef.altermundi.net is somewhat outdated I created a >>> simplified >>> version called "Jefe" (Spanish for chef). >>> >>> Currently it jefe.tk has the following features: >>> >>> - Build latest stable 17.06 (dev tree could be added as well) >>> - Easy to find device, just type in the name >>> - Choose network profile >>> - Choose flavor >>> - Edit packages (if desired) >>> >>> More features can be added, let me know what you need. This is a >>> very >>> early version, let me know what you think! >>> >>> Best, >>> >>> Paul >>> >>> _______________________________________________ >>> lime-dev mailing list >>> lime-dev(a)lists.libremesh.org >>> https://lists.libremesh.org/mailman/listinfo/lime-dev >>> >> >> _______________________________________________ >> lime-dev mailing list >> lime-dev(a)lists.libremesh.org >> https://lists.libremesh.org/mailman/listinfo/lime-dev > > _______________________________________________ > lime-dev mailing list > lime-dev(a)lists.libremesh.org > https://lists.libremesh.org/mailman/listinfo/lime-dev > > > _______________________________________________ > lime-dev mailing list > lime-dev(a)lists.libremesh.org > https://lists.libremesh.org/mailman/listinfo/lime-dev

I agree with Ufo that imagebuilder is already used in the OpenWRT/LEDE world and it would be confusing to use that name. Chef (as in the french word for the "guy who specializes in cooking") was a good term I think, although there's also conflict with the well known tool: https://www.chef.io/chef/ https://www.chef.io/chef/ I personally like the "cooking" reference, so something like: kitchen.libremesh.org might be good. And the package might be called: lime-kitchen

Cheers, Nico On 10/24/2017 11:40 AM, Ufo wrote:

_______________________________________________ lime-dev mailing list lime-dev(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-dev

On Wed, Oct 25, 2017 at 03:46:09PM -0300, Nicolás Echániz wrote: I do like the 'kitchen' term for the imagebuilder-instance, I used that name for the buildroot container of gentoo-based LXC clusters :) or maybe it's more like a fast-food restaurant or even pizza-delivery? > > Cheers, > Nico > > > > > On 10/24/2017 11:40 AM, Ufo wrote: >> i dont agree with the name "imagebuilder" for this new jefe-project. >> As you might know, that name is already existing for Openwrt/LEDE. Using >> the same name will be confusing. >> >> https://wiki.openwrt.org/doc/howto/obtain.firmware.generate >> >> also, its not the first and only web-interface for the >> openwrt/lede-imagebuilder, see f.i. meshkit. >> >> so it would be nice to find a new (maybe shorter) name for jefe.tk! >> >> ufo >> >> p.s. >> also think about people who are not involved into mesh-networks since >> years: most of these will not know why a firmware has to be "build", and >> the name "image" is more associated with png or jpg-files for them. >> >> >> >> On 20.10.2017 16:10, Nicolas Pace wrote: >>> I agree that an imagebuilder.libremesh.org (that then migrates to >>> imagebuilder.openwrt.org ) would be great. >>> >>> Regards, >>> >>> On Fri, 2017-10-20 at 00:06 +0200, Paul Spooren wrote: >>>> Hey Nico, >>>> >>>> yea gosh I totally messed up that name. I personally hate adding a 2 >>>> at >>>> the end, if it works for you please add chef.libremesh.org to the IP >>>> of >>>> jefe.tk. >>>> >>>> As this service may become more "official", maybe >>>> imagebuilder.libremesh.org would be the international solution. >>>> >>>> Best, >>>> Paul >>>> >>>> On 10/19/17 11:59 PM, Nicolás Echániz wrote: >>>>> Hi all, >>>>> >>>>> Paul it's really great that you are working on this. >>>>> >>>>> I just want to note before it's too late! that Jefe in spanish >>>>> means >>>>> Boss. A more appropriate translation would be "Cocinero", but I'd >>>>> like >>>>> to propose that if this tool will replace our existing firmware >>>>> chef, >>>>> whe just call this chef, and explain it's a complete rewrite of the >>>>> previous project. Or chef2 ? >>>>> >>>>> We talk about the firmware in many places old and current, so if >>>>> this >>>>> will be the natural replacement, it seems best to inherit the name >>>>> also. >>>>> >>>>> Please other devs state your opinion on this.

I can see that this tools is relevant beyond the scope of libremesh, sooner or later it may become imagebuilder.openwrt.org or something like that...