[UGMM] [admin-plug.org.au 6797] Re: Updating UGMM

Timothy White tim at whiteitsolutions.com.au
Wed Feb 17 13:03:36 UTC 2016


So....

I poke my head in about once a year still and see how things are going.

Building packages is really very easy, as mentioned by Andrew. See
https://github.com/plugorgau/ugmm/releases/tag/0.5.2 for the first
"official GitHub" release.

I've added to the 'issues' a little bit this evening. Frankly, I'd love to
see UGMM rewritten on a framework like Symfony, with a simple DB as the
backend. It was a great idea to have SSO with LDAP, however it's more
trouble than it's worth. And with "Social Signin" being so easy, lets not
make people remember another password. And if we can't find your preferred
login method in (https://github.com/hwi/HWIOAuthBundle), then maybe you
need to come out from under a rock. The data in UGMM is better structured
to a database (that isn't LDAP), other than the user account part. Payments
in LDAP, what was I thinking!?!?

Also, regarding servers and AWS credits expiring. Other than our website,
and the video streaming we do, what are we using the servers for anymore?

   - Main website - Planning to move to Github
   - IRC? - Moved to Uniirc
   - Mailing lists
   - Mail
   - UGMM
   - Video Streaming (Icecast?)
   - DNS

Other than Video streaming, the rest would fit on a Digital Ocean droplet
for 5USD/month. Maybe Video Streaming should be a droplet we fireup when we
actually want to be streaming?

Happy to be part of the discussion and put some time in to moving things
forward. Really glad to see some new blood coming in and making changes,
moving things forward. It's a good thing for change, I welcome it!

And for anyone who doesn't know who I am. I'm Tim, long time PLUGer who
moved to QLD. I generally pay for the domain name when it comes up for
renewal as paying for a membership doesn't really get me anything anymore.
I still care about PLUG, just hard to be involved from QLD and with a young
family.

Regards

Tim

On Sun, Jan 24, 2016 at 1:34 PM, Andrew Cooks <acooks at gmail.com> wrote:

>
>
> On Sun, Jan 24, 2016 at 9:05 AM, Michael Van Delft <michael at hybr.id.au>
> wrote:
>
>> Hey Andrew,
>>
>> That sounds good, I did actually do a manual change just after Luke's
>> email but I think it's still worth deploying from the deb so that it's up
>> to date and also to check if anything else has changed that hasn't been
>> added to the git repo.
>>
>
> I've done the manual comparison between the files on power and the git
> repo and found small inconsistencies in classtest.php and
> members_group_status.php.
>
> Besides those differences, it doesn't look like deploying a .deb package
> built from the current repo would break anything. That being said, I'm
> quite novice at Debian packaging and don't feel comfortable with breaking
> this on my own at this stage.
>
> The good news is it looks like things could be cleaned up in an hour or
> less.
>
>
>>
>> Unfortunately I've had a few things come up and I don't think I'm going
>> to be able to make it to plug in the pub tomorrow but maybe we can run
>> through it at the next plug event.
>>
>
> I'll see if there is any other interest to do this tomorrow, otherwise it
> will just become another one of the things "we should do some day".
>
> a.
>
>
>> --
>> Michael
>>
>> On 22 January 2016 at 14:07, Andrew Cooks <acooks at gmail.com> wrote:
>>
>>> Hi Michael
>>>
>>> On Wed, Jan 20, 2016 at 3:45 PM, Michael Van Delft <michael at hybr.id.au>
>>> wrote:
>>>
>>>> Hey All,
>>>>
>>>> I've got a couple of questions about ugmm, first is becoming an admin.
>>>> I assume I need to ask one of the other admins to mark my account as an
>>>> admin so I can then go in and update users (e.g. mark them as having paid).
>>>>
>>>
>>> I think you need to be added to the committee group, possibly in ldap,
>>> but I don't see a way to do this in the web interface.
>>>
>>>
>>>>
>>>> The second question is how do we go about pushing updates to the
>>>> server? I've made a small pull request to the git repo (just to fix the
>>>> mixed content SSL warnings we were getting) and I've been resisting the
>>>> urge to just go and edit the files on the server by hand but I'm not sure
>>>> what the correct process is. I assume we build a .deb and install it with
>>>> dpkg?
>>>>
>>>
>>> I've had a quick look at your pull request and it looks good to me.
>>>
>>> There was a similar discussion on the admin list in Feb 2015:
>>> http://lists.plug.org.au/mailman/private/admin/2015-February/006432.html
>>>
>>> Building a package seems to be as easy as:
>>>
>>> $ git clone https://github.com/plugorgau/ugmm.git
>>> $ cd ugmm
>>> $ debuild -i -us -uc -b
>>>
>>> Let's try to do this with a .deb package and a manual diff to confirm
>>> that our previously deployed code matches the new package minus your latest
>>> patch.
>>>
>>> We (or I) can do this on Monday evening unless someone objects before
>>> then.
>>>
>>>
>>> a.
>>>
>>
>>
>> _______________________________________________
>> You are receiving this email as your are listed as an Admin for Perth
>> Linux User Group servers
>> Admin mailing list
>> Admin at plug.org.au
>> http://lists.plug.org.au/mailman/listinfo/admin
>>
>>
>
> _______________________________________________
> You are receiving this email as your are listed as an Admin for Perth
> Linux User Group servers
> Admin mailing list
> Admin at plug.org.au
> http://lists.plug.org.au/mailman/listinfo/admin
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plug.org.au/pipermail/ugmm/attachments/20160217/91f8b7ab/attachment.html>


More information about the Ugmm mailing list