Good news. Upstream has merged my pull request that places the snapcraft.yaml in the root of the project.
I now have a question on how I can provide them with an account that will allow them to upload as ntopng. Currently ntopng is a reserved name. I would like to setup some travis CI that will auto upload tip of dev into the edge channel of "ntopng". On Fri, Aug 5, 2016 at 2:53 PM, Blake Rouse <blake.ro...@canonical.com> wrote: > Already have pull request into the project. > > https://github.com/ntop/ntopng/pull/676 > > ntopng is a reserved name in the snappy store, so I don't know the process > of getting an account that can have access to that name. Allowing them to > publish under the correct name. > > On Fri, Aug 5, 2016 at 1:55 AM, Didier Roche <didro...@ubuntu.com> wrote: > >> Le 04/08/2016 à 17:40, Blake Rouse a écrit : >> > I have created a ntopng snap for the dev branch of ntopng. The snap >> > works in strict mode once you connect it to the network-control >> > interface. I currently registered the snap as ntopng-blake as ntopng >> > is a reserved name. Let me know what you think. >> > >> > sudo snap install ntopng-blake >> > sudo snap connect ntopng-blake:network-control >> ubuntu-core:network-control >> > sudo systemctl restart snap.ntopng-blake.ntopng.service >> > >> > Login - http://localhost:3000 >> > User - admin >> > Pass - admin >> > >> > A couple things that would improve this snap are: >> > >> > 1. I need the ntopng service to start after the redis service. >> > Currently in the ntopng service it loops until it can connect to redis >> > and then spawns the ntopng process. It would be nice to say in >> > snapcraft start this service after this other service has started. >> > >> > 2. Since network-control interface is a reserved interface you have to >> > manually restart the service once the connection is made. It would be >> > nice to say in snapcraft that this service should be restarted once >> > the connection is made. Even better would be don't start this service >> > until this connection is made. >> > >> > Overall this is an awesome way of getting ntopng running on your >> > system, directly from tip of dev. >> > >> > ntopng - https://github.com/ntop/ntopng >> > ntopng-snap - https://github.com/blakerouse/ntopng-snap >> >> Excellent work Blake! >> >> Do you think there is any chance that you propose it to upstream for >> merging your snapcraft.yaml to their upstream tree? >> Cheers, >> Didier >> >> -- >> Snapcraft mailing list >> Snapcraft@lists.snapcraft.io >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/snapcraft >> > >
-- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
