From sebastien at aperghis.net Thu Apr 7 01:45:01 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Thu, 7 Apr 2016 01:45:01 +0200 (CEST) Subject: [Act] Act services moving on a new server In-Reply-To: <430342655.204767191.1456104743351.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <2093236587.175361074.1459986301050.JavaMail.root@spooler3-g27.priv.proxad.net> S?bastien Aperghis-Tramoni wrote: > S?bastien Aperghis-Tramoni wrote: > > > Indeed. I'll try to compile some older Perl as well and see if > > it's easier with these instead of a too recent one. > > This went much better. If you can access this URL: > ? http://act.perlworkshop.eu/phantom/ > > it will confirm that Act is working on the new server. I quickly > imported part of the production database, but I'll have to do > that again when we actually switch from spectre to phantom. A last thing that wasn't working was the wiki. Now fixed: ? http://act.perlworkshop.eu/phantom/wiki?node=HomePage So we can consider migrating to phantom (the new server) really soon now. This will obviously disrupt the services during the migration, for a duration that will depend on DNS propagation. Steps: - shutdown all services on spectre - dump all PostgreSQL databases - rsync everything a last time from spectre to phantom - reimport all PostgreSQL databases - startup all services on phantom Executing these steps should roughly take an hour, given that data have been rsync'd every 2 hours since weeks. But as said, DNS propagation will make the disruption longer for people still trying to reach spectre. This can be mitigated to some degree by reducing the TTL of the records. Unless I oversaw something, migrating over the next days should be an appropriate time. Opinions? > To dump a few notes here: > > - compile everything with -std=gnu89 > > - Perl 5.12 is apparently the last Perl we can compile an > unmodified modperl 1.x against; 5.14 already presents the > conflicts Alex and myself encountered > > - latest Apache::AuthCookie depends on Apache::Test 1.39, > which isn't correctly indexed, or at least is unknown to > cpanminus (I haven't looked into that) - Wiki::Toolkit 0.75 is the last version compatible with the current schema used by Act. It should be possible to upgrade the schema to newer version, but this will be tried after migrating to the new server. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From sjn at pvv.org Thu Apr 7 02:47:53 2016 From: sjn at pvv.org (Salve J Nilsen) Date: Thu, 7 Apr 2016 02:47:53 +0200 (CEST) Subject: [Act] Act services moving on a new server In-Reply-To: <2093236587.175361074.1459986301050.JavaMail.root@spooler3-g27.priv.proxad.net> References: <2093236587.175361074.1459986301050.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: S?bastien Aperghis-Tramoni said: > > Steps: > - shutdown all services on spectre > - dump all PostgreSQL databases > - rsync everything a last time from spectre to phantom > - reimport all PostgreSQL databases > - startup all services on phantom > > Executing these steps should roughly take an hour, given that > data have been rsync'd every 2 hours since weeks. But as said, > DNS propagation will make the disruption longer for people still > trying to reach spectre. This can be mitigated to some degree > by reducing the TTL of the records. > > Unless I oversaw something, migrating over the next days should > be an appropriate time. > > Opinions? 0) Make a cronological task list, with ALL necessary steps written down. Even the minor ones! 1) Do the $NEW_TTL change right now, so people with $CURRENT_TTL can have time to update their DNS cache. Then wait with any migration until $CURRENT_TTL time has passed. :) 2) Make a "this site is under maintainance" static webpage, that one can put up during the migration. Doesn't have to be more than a catch-all mod_rewrite rule pointing to a static webpage containing a few words of apology, a smiley and an ETA for when the sites are expected to be up again. 3) IMHO, at least admins of currently active sites should get a separate notice mail telling about the impending doom, ETA, duration, etc. :) This is also so they can give notice to their users/staff as they deem necessary. 4) Pick a downtime a few days *after* a conference, and as long as possible before the next conference, so signup disruption is minimized. 5) Thanks for the effort! :D - Salve -- #!/usr/bin/env perl sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print# Salve Joshua Nilsen getc DATA}$"="'};&{'";@_=unpack("C*",unpack("u*",':50,$'.# '3!=0"59,6!`%%P\0!1)46%!F.Q`%01,`'."\n"));eval "&{'@_'}"; __END__ is near! :) From toddr at cpanel.net Thu Apr 7 06:44:11 2016 From: toddr at cpanel.net (Todd E Rinaldo) Date: Wed, 6 Apr 2016 23:44:11 -0500 Subject: [Act] Act services moving on a new server In-Reply-To: References: <2093236587.175361074.1459986301050.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: Yeah I'll be honest the timing on this really sucks for yapcna if there's really going to be an outage. The other thing that you should have written down is what your back out plan is if something goes wrong > On Apr 6, 2016, at 7:47 PM, Salve J Nilsen wrote: > > S?bastien Aperghis-Tramoni said: >> >> Steps: >> - shutdown all services on spectre >> - dump all PostgreSQL databases >> - rsync everything a last time from spectre to phantom >> - reimport all PostgreSQL databases >> - startup all services on phantom >> >> Executing these steps should roughly take an hour, given that >> data have been rsync'd every 2 hours since weeks. But as said, >> DNS propagation will make the disruption longer for people still >> trying to reach spectre. This can be mitigated to some degree >> by reducing the TTL of the records. >> >> Unless I oversaw something, migrating over the next days should >> be an appropriate time. >> >> Opinions? > > 0) Make a cronological task list, with ALL necessary steps written down. Even the minor ones! > > 1) Do the $NEW_TTL change right now, so people with $CURRENT_TTL can have time to update their DNS cache. Then wait with any migration until $CURRENT_TTL time has passed. :) > > 2) Make a "this site is under maintainance" static webpage, that one can put up during the migration. Doesn't have to be more than a catch-all mod_rewrite rule pointing to a static webpage containing a few words of apology, a smiley and an ETA for when the sites are expected to be up again. > > 3) IMHO, at least admins of currently active sites should get a separate notice mail telling about the impending doom, ETA, duration, etc. :) This is also so they can give notice to their users/staff as they deem necessary. > > 4) Pick a downtime a few days *after* a conference, and as long as possible before the next conference, so signup disruption is minimized. > > 5) Thanks for the effort! :D > > > - Salve > > -- > #!/usr/bin/env perl > sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print# Salve Joshua Nilsen > getc DATA}$"="'};&{'";@_=unpack("C*",unpack("u*",':50,$'.# > '3!=0"59,6!`%%P\0!1)46%!F.Q`%01,`'."\n"));eval "&{'@_'}"; __END__ is near! :) > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4649 bytes Desc: not available URL: From philippe.bruhat at free.fr Thu Apr 7 10:23:41 2016 From: philippe.bruhat at free.fr (Philippe Bruhat (BooK)) Date: Thu, 7 Apr 2016 10:23:41 +0200 Subject: [Act] Act services moving on a new server In-Reply-To: References: <2093236587.175361074.1459986301050.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <20160407082341.GC2749@zok> On Thu, Apr 07, 2016 at 02:47:53AM +0200, Salve J Nilsen wrote: > S?bastien Aperghis-Tramoni said: > > > >Steps: > >- shutdown all services on spectre > >- dump all PostgreSQL databases > >- rsync everything a last time from spectre to phantom > >- reimport all PostgreSQL databases > >- startup all services on phantom > > > >Executing these steps should roughly take an hour, given that > >data have been rsync'd every 2 hours since weeks. But as said, > >DNS propagation will make the disruption longer for people still > >trying to reach spectre. This can be mitigated to some degree > >by reducing the TTL of the records. > > > >Unless I oversaw something, migrating over the next days should > >be an appropriate time. > > > >Opinions? > > 0) Make a cronological task list, with ALL necessary steps written down. > Even the minor ones! > > 1) Do the $NEW_TTL change right now, so people with $CURRENT_TTL can have > time to update their DNS cache. Then wait with any migration until > $CURRENT_TTL time has passed. :) This only works for the domains we control. I know of a few that point to the address of spectre, and still will after the move until we can reach the owners and let them know the new address. If we don't know the affected domains, then I think the only solution is to put up a static page with some contact info asking specifically for the URL used to reach the now-broken site. Then we can use whois to try and contact the domain owner, so that they point to the real site. We can find some of those domains by looking in the Act config for the "main" url of each conference, and get a list of all the vanity domains that we don't control. One such domain is www.aconferencetoolkit.com, which is apparently owned by Robert Blackwell from Pittsburgh. To mitigate the downtime caused by DNS propagation, what about: - setup the Act database on phantom - dump and shutdown the Act database on spectre - restore that last copy of the spectre db on phantom - point the spectre Act config to the db on phantom (this might add some latency, but that's only for people connected to spectre) - at this stage, we have two Act servers on different boxes pointing to the same database instance - reconfigure the DNS to point to phantom - wait for at least $CURRENT_TTL, until every domain points to phantom - shut down spectre This way, both the old and new IP point to a working Act instance. > 2) Make a "this site is under maintainance" static webpage, that one can put > up during the migration. Doesn't have to be more than a catch-all > mod_rewrite rule pointing to a static webpage containing a few words of > apology, a smiley and an ETA for when the sites are expected to be up again. As explained below, this should probably contain some contact info and instructions asking "through which URL did you reach this page?". This should remain on spectre as long as it's still connected to the network. -- Philippe Bruhat (BooK) Only a fool follows orders without knowing why. (Moral from Groo The Wanderer #86 (Epic)) From nine at detonation.org Thu Apr 7 10:29:30 2016 From: nine at detonation.org (Stefan Seifert) Date: Thu, 07 Apr 2016 10:29:30 +0200 Subject: [Act] Act services moving on a new server In-Reply-To: <20160407082341.GC2749@zok> References: <2093236587.175361074.1459986301050.JavaMail.root@spooler3-g27.priv.proxad.net> <20160407082341.GC2749@zok> Message-ID: <1505421.4YYsyNmYUb@sphinx> On Donnerstag, 7. April 2016 10:23:41 CEST Philippe Bruhat (BooK) wrote: > To mitigate the downtime caused by DNS propagation, what about: > - setup the Act database on phantom > - dump and shutdown the Act database on spectre > - restore that last copy of the spectre db on phantom > - point the spectre Act config to the db on phantom (this might add some > latency, but that's only for people connected to spectre) As an alternative you could set up a forwarding proxy on spectre so updates on Act's code or static files will be covered, too. Instead of a proxy, one could even forward port 80 to phantom using iptables and destination NAT. I've successfully used both strategies for server migrations in the past. Stefan From sebastien at aperghis.net Fri Apr 8 01:10:22 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Fri, 8 Apr 2016 01:10:22 +0200 (CEST) Subject: [Act] Act services moving on a new server In-Reply-To: Message-ID: <338651822.189137805.1460070622014.JavaMail.root@spooler3-g27.priv.proxad.net> Salve J Nilsen wrote: > S?bastien Aperghis-Tramoni said: > > > > Steps: > > - shutdown all services on spectre > > - dump all PostgreSQL databases > > - rsync everything a last time from spectre to phantom > > - reimport all PostgreSQL databases > > - startup all services on phantom > > > > Executing these steps should roughly take an hour, given that > > data have been rsync'd every 2 hours since weeks. But as said, > > DNS propagation will make the disruption longer for people still > > trying to reach spectre. This can be mitigated to some degree > > by reducing the TTL of the records. > > > > Unless I oversaw something, migrating over the next days should > > be an appropriate time. > > > > Opinions? > > 0) Make a cronological task list, with ALL necessary steps written > down. Even the minor ones! Agreed. > 1) Do the $NEW_TTL change right now, so people with $CURRENT_TTL can > have time to update their DNS cache. Then wait with any migration > until $CURRENT_TTL time has passed. :) Yes, I didn't mention that in my previous mail because I already had that in mind. The current TTL is currently 3h. I can reduce it to 1h. Below usually is useless, because many ISP will cache the records anyway. > 2) Make a "this site is under maintainance" static webpage, that > one can put up during the migration. Doesn't have to be more than > a catch-all mod_rewrite rule pointing to a static webpage containing > a few words of apology, a smiley and an ETA for when the sites > are expected to be up again. Agreed. > 3) IMHO, at least admins of currently active sites should get a > separate notice mail telling about the impending doom, ETA, > duration, etc. :) > This is also so they can give notice to their users/staff as > they deem necessary. Indeed, I didn't think of that. > 4) Pick a downtime a few days *after* a conference, and as long > as possible before the next conference, so signup disruption is > minimized. Yes. Given YAPC::NA is in roughly two months, I thought it was far enough to avoid being an inconvenience. But given Todd's answer, I guess it isn't. Todd E Rinaldo wrote: > Yeah I'll be honest the timing on this really sucks for yapcna > if there's really going to be an outage. > > The other thing that you should have written down is what your > back out plan is if something goes wrong Another factor on which we don't have any grasp is when we will loose the network on spectre. This is dependant on when the ISP of Logilune decides to cut the cable. So it is better to try and migrate softly while we still have spectre running, instead of having to handle that as an emergency. This makes for a kinda temporary rollback plan, but not a backup plan per se. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From sebastien at aperghis.net Fri Apr 8 01:12:24 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Fri, 8 Apr 2016 01:12:24 +0200 (CEST) Subject: [Act] Act services moving on a new server In-Reply-To: <20160407082341.GC2749@zok> Message-ID: <1176181906.189151667.1460070744227.JavaMail.root@spooler3-g27.priv.proxad.net> Philippe Bruhat wrote: > Salve J Nilsen wrote: > > > 1) Do the $NEW_TTL change right now, so people with $CURRENT_TTL > > can have time to update their DNS cache. Then wait with any > > migration until $CURRENT_TTL time has passed. :) > > This only works for the domains we control. > > I know of a few that point to the address of spectre, and still > will after the move until we can reach the owners and let them > know the new address. If we don't know the affected domains, then > I think the only solution is to put up a static page with some > contact info asking specifically for the URL used to reach the > now-broken site. Then we can use whois to try and contact the > domain owner, so that they point to the real site. > > We can find some of those domains by looking in the Act config > for the "main" url of each conference, and get a list of all > the vanity domains that we don't control. That's why we always asked people to make CNAME to the resource conferences.mongueurs.net, in order to handle server migrations. I now remember that when we moved from profane to spectre, several domains remained unchanged and therefore broken. So yes, there are certainly some domains that directly point to spectre. > To mitigate the downtime caused by DNS propagation, what about: > - setup the Act database on phantom > - dump and shutdown the Act database on spectre > - restore that last copy of the spectre db on phantom > - point the spectre Act config to the db on phantom (this might > add some latency, but that's only for people connected to spectre) > - at this stage, we have two Act servers on different boxes > pointing to the same database instance > - reconfigure the DNS to point to phantom > - wait for at least $CURRENT_TTL, until every domain points to > phantom > - shut down spectre > > This way, both the old and new IP point to a working Act instance. I'm really not keen with such a solution for the following reasons: - complex - requires to modify the configuration - PostgreSQL over the internets - the first step (setup the Act database on phantom) is useless because restoring databases requires Act to be down Stefan Seifert wrote: > As an alternative you could set up a forwarding proxy on spectre > so updates on Act's code or static files will be covered, too. > Instead of a proxy, one could even forward port 80 to phantom > using iptables and destination NAT. I've successfully used both > strategies for server migrations in the past. Both spectre and phantom are running FreeBSD, so pf instead of iptables, but as far as I know, spectre lacks pf support. French Perl monger Richard suggested a proxy-based solution as well. I quite prefer this approach, as it can also be used to prepare the maintenance pages. While reading & writing these mails, I also realised that instead of migrating everything at the same time, we can first migrate the static sites, to check that Apache works. Then migrate the Act test instance, so you can all check that it works, and it's a database we can trash with no regrets. This will also be useful to see how phantom performs when actually used, this server being clearly less powerful than spectre. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From domm at cpan.org Fri Apr 8 10:54:18 2016 From: domm at cpan.org (Thomas Klausner) Date: Fri, 8 Apr 2016 10:54:18 +0200 Subject: [Act] Act instance for Alpine Perl Workshop 2016 In-Reply-To: <20160316092733.GC13067@desther.ips.validad.net> References: <20160311113411.GA21597@localhost> <497813830.27956182.1458085664249.JavaMail.root@spooler3-g27.priv.proxad.net> <20160316092733.GC13067@desther.ips.validad.net> Message-ID: <20160408085418.GE25564@desther.ips.validad.net> Hi! On Wed, Mar 16, 2016 at 10:27:33AM +0100, Thomas Klausner wrote: > On Wed, Mar 16, 2016 at 12:47:44AM +0100, S?bastien Aperghis-Tramoni wrote: > > > The team: https://github.com/orgs/Act-Conferences/teams/alpineperl2016 > > The repo: https://github.com/Act-Conferences/alpineperl2016 > > The site: http://test.mongueurs.net/alpineperl2016/ For some strange reasons, pepl did not get his invitation (it's listed as pending in github). Maybe because he's not a member of the Act-Conferences orga? Maddingue, do you have any idea what might be wrong? Could you maybe add https://github.com/pepl to Act-Conferences and send him another invitation? Greetings, domm -- #!/usr/bin/perl http://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/} From sebastien at aperghis.net Fri Apr 8 13:42:55 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Fri, 8 Apr 2016 13:42:55 +0200 (CEST) Subject: [Act] Act instance for Alpine Perl Workshop 2016 In-Reply-To: <20160408085418.GE25564@desther.ips.validad.net> Message-ID: <1377441828.194903047.1460115775048.JavaMail.root@spooler3-g27.priv.proxad.net> Thomas Klausner wrote: > Hi! Hello Thomas, > On Wed, Mar 16, 2016 at 10:27:33AM +0100, Thomas Klausner wrote: > > > On Wed, Mar 16, 2016 at 12:47:44AM +0100, S?bastien > > Aperghis-Tramoni wrote: > > > > > The team: > > > https://github.com/orgs/Act-Conferences/teams/alpineperl2016 > > > The repo: https://github.com/Act-Conferences/alpineperl2016 > > > The site: http://test.mongueurs.net/alpineperl2016/ > > For some strange reasons, pepl did not get his invitation (it's > listed as pending in github). Maybe because he's not a member of > the Act-Conferences orga? Ah, maybe. > Maddingue, do you have any idea what might be wrong? Could you > maybe add https://github.com/pepl to Act-Conferences and send > him another invitation? Just did that. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From michael.kroell at gmail.com Fri Apr 8 14:13:32 2016 From: michael.kroell at gmail.com (=?UTF-8?Q?Michael_Kr=c3=b6ll?=) Date: Fri, 8 Apr 2016 14:13:32 +0200 Subject: [Act] Act instance for Alpine Perl Workshop 2016 In-Reply-To: <1377441828.194903047.1460115775048.JavaMail.root@spooler3-g27.priv.proxad.net> References: <1377441828.194903047.1460115775048.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <5707A06C.4090703@gmail.com> On 04/08/2016 01:42 PM, S?bastien Aperghis-Tramoni wrote: > Just did that. Worked - Cheers! ~michael From amalia at cluj.pm Fri Apr 22 19:25:08 2016 From: amalia at cluj.pm (Amalia) Date: Fri, 22 Apr 2016 20:25:08 +0300 Subject: [Act] YAPC::EU 2016 In-Reply-To: <02d101d11899$51f5a110$f5e0e330$@cluj.pm> References: <023601d117cd$fe87c420$fb974c60$@cluj.pm> <70199632.365926455.1446815372901.JavaMail.root@spooler3-g27.priv.proxad.net> <02d101d11899$51f5a110$f5e0e330$@cluj.pm> Message-ID: <002301d19cbb$eaca29f0$c05e7dd0$@cluj.pm> Hi S?bastien, Can you please add 3 more members to the ye2016 team (test site && repo)? 1. danfumarel 2. victor-dogaru 3. MihaelaMarinca Thanks a bunch, Amalia -----Original Message----- From: act-bounces at mongueurs.net [mailto:act-bounces at mongueurs.net] On Behalf Of Amalia Sent: 6 noiembrie 2015 15:45 To: 'The Act users mailing list' Subject: Re: [Act] YAPC::EU 2016 Thank you, Sebastien! -----Original Message----- From: act-bounces at mongueurs.net [mailto:act-bounces at mongueurs.net] On Behalf Of S?bastien Aperghis-Tramoni Sent: 6 noiembrie 2015 15:10 To: The Act users mailing list Subject: Re: [Act] YAPC::EU 2016 Amalia wrote: > paulmercean should work on Github, he just checked. Thanks! > > Let me know if you encounter any other issues. "paulmercean" has been invited to the ye2016 team. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. _______________________________________________ Act mailing list Act at mongueurs.net http://listes.mongueurs.net/mailman/listinfo/act _______________________________________________ Act mailing list Act at mongueurs.net http://listes.mongueurs.net/mailman/listinfo/act From sebastien at aperghis.net Sat Apr 23 16:02:19 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Sat, 23 Apr 2016 16:02:19 +0200 (CEST) Subject: [Act] YAPC::EU 2016 In-Reply-To: <002301d19cbb$eaca29f0$c05e7dd0$@cluj.pm> Message-ID: <629732098.392113353.1461420139110.JavaMail.root@spooler3-g27.priv.proxad.net> Amalia wrote: > Hi S?bastien, Hello, > Can you please add 3 more members to the ye2016 team (test site && > repo)? > > 1. danfumarel > 2. victor-dogaru > 3. MihaelaMarinca Just did, but I note that the three previous invitations are still pending: MeSeFM, deluxaran, paulmercean I can also give you owner access to the team, so that you can invite yourself other people, as needed. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From domm at cpan.org Sat Apr 23 18:34:33 2016 From: domm at cpan.org (Thomas Klausner) Date: Sat, 23 Apr 2016 18:34:33 +0200 Subject: [Act] Please publish Alpine Perl Workshop 2016 ACT instance Message-ID: <20160423163433.GF19984@localhost> Hi! We're done with a very basic ACT instance (ugly, but good enough to start). Please set up a live instance of https://github.com/Act-Conferences/alpineperl2016 I assume that changes to the repo will then also be pushed to the live site every 5 minutes (like the test setup?) If not, please tell us how to push changes to live. Greetings, domm -- #!/usr/bin/perl http://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/} From sebastien at aperghis.net Sat Apr 23 22:29:38 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Sat, 23 Apr 2016 22:29:38 +0200 (CEST) Subject: [Act] Please publish Alpine Perl Workshop 2016 ACT instance In-Reply-To: <20160423163433.GF19984@localhost> Message-ID: <1534784575.395632996.1461443378369.JavaMail.root@spooler3-g27.priv.proxad.net> Thomas Klausner wrote: > Hi! Hello, > We're done with a very basic ACT instance (ugly, but good enough to > start). > > Please set up a live instance of > https://github.com/Act-Conferences/alpineperl2016 Done: http://act.yapc.eu/alpineperl2016/ You are admin of the conference. > I assume that changes to the repo will then also be pushed to the > live site every 5 minutes (like the test setup?) > If not, please tell us how to push changes to live. The production site uses the production branch of the repository, while the test site uses the master branch. Both are updated every 5 minutes. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From domm at cpan.org Sun Apr 24 13:19:06 2016 From: domm at cpan.org (Thomas Klausner) Date: Sun, 24 Apr 2016 13:19:06 +0200 Subject: [Act] Please publish Alpine Perl Workshop 2016 ACT instance In-Reply-To: <1534784575.395632996.1461443378369.JavaMail.root@spooler3-g27.priv.proxad.net> References: <20160423163433.GF19984@localhost> <1534784575.395632996.1461443378369.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <20160424111906.GB10530@localhost> Hi! On Sat, Apr 23, 2016 at 10:29:38PM +0200, S?bastien Aperghis-Tramoni wrote: > Done: http://act.yapc.eu/alpineperl2016/ Great! But I just got a report from a user who submitted a talk: The abstract and video-URL fields were not recorded in the DB. I tried to add an abstract, and indeed the data was not stored. http://act.yapc.eu/alpineperl2016/edittalk?talk_id=6703 Any idea what's going on? Greetings, domm -- #!/usr/bin/perl http://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/} From amalia at cluj.pm Mon Apr 25 11:16:54 2016 From: amalia at cluj.pm (Amalia) Date: Mon, 25 Apr 2016 12:16:54 +0300 Subject: [Act] YAPC::EU 2016 In-Reply-To: <629732098.392113353.1461420139110.JavaMail.root@spooler3-g27.priv.proxad.net> References: <002301d19cbb$eaca29f0$c05e7dd0$@cluj.pm> <629732098.392113353.1461420139110.JavaMail.root@spooler3-g27.priv.proxad.net> Message-ID: <007501d19ed3$35dcdcd0$a1969670$@cluj.pm> Hi, Thanks heaps! Owner access would be great, my github account's amaliapomian. Have great week, Amalia -----Original Message----- From: act-bounces at mongueurs.net [mailto:act-bounces at mongueurs.net] On Behalf Of S?bastien Aperghis-Tramoni Sent: 23 aprilie 2016 17:02 To: The Act users mailing list Subject: Re: [Act] YAPC::EU 2016 Amalia wrote: > Hi S?bastien, Hello, > Can you please add 3 more members to the ye2016 team (test site && > repo)? > > 1. danfumarel > 2. victor-dogaru > 3. MihaelaMarinca Just did, but I note that the three previous invitations are still pending: MeSeFM, deluxaran, paulmercean I can also give you owner access to the team, so that you can invite yourself other people, as needed. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. _______________________________________________ Act mailing list Act at mongueurs.net http://listes.mongueurs.net/mailman/listinfo/act From sebastien at aperghis.net Mon Apr 25 16:13:32 2016 From: sebastien at aperghis.net (=?utf-8?Q?S=C3=A9bastien?= Aperghis-Tramoni) Date: Mon, 25 Apr 2016 16:13:32 +0200 (CEST) Subject: [Act] YAPC::EU 2016 In-Reply-To: <007501d19ed3$35dcdcd0$a1969670$@cluj.pm> Message-ID: <1135576562.417663055.1461593612772.JavaMail.root@spooler3-g27.priv.proxad.net> Amalia wrote: > Hi, Hello, > Thanks heaps! Owner access would be great, my github account's > amaliapomian. Done. -- S?bastien Aperghis-Tramoni Close the world, txEn eht nepO. From amalia at cluj.pm Thu Apr 28 19:07:45 2016 From: amalia at cluj.pm (Amalia) Date: Thu, 28 Apr 2016 20:07:45 +0300 Subject: [Act] YAPC::EU 2016 ready for live (basic features) Message-ID: <032801d1a170$7c25b4b0$74711e10$@cluj.pm> Hi, We're done with a basic ACT instance for YAPC::EU 2016, ready for login, registration, talk submission && also allowing potential sponsors to check out sponsorship & exhibition opportunities. Please set up a live instance of https://github.com/Act-Conferences/ye2016 Also, please let us know how to push changes to live. Thanks, Amalia -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.bruhat at free.fr Fri Apr 29 09:59:39 2016 From: philippe.bruhat at free.fr (Philippe Bruhat (BooK)) Date: Fri, 29 Apr 2016 09:59:39 +0200 Subject: [Act] YAPC::EU 2016 ready for live (basic features) In-Reply-To: <032801d1a170$7c25b4b0$74711e10$@cluj.pm> References: <032801d1a170$7c25b4b0$74711e10$@cluj.pm> Message-ID: <20160429075939.GC2479@zok> On Thu, Apr 28, 2016 at 08:07:45PM +0300, Amalia wrote: > > Also, please let us know how to push changes to live. > Quoting S?bastien: > The production site uses the production branch of the repository, > while the test site uses the master branch. Both are updated every > 5 minutes. -- Philippe Bruhat (BooK) The faster the climb, the swifter the fall. (Moral from Groo The Wanderer #87 (Epic)) From andy at shitov.ru Fri Apr 29 21:02:51 2016 From: andy at shitov.ru (Andrew Shitov) Date: Fri, 29 Apr 2016 21:02:51 +0200 Subject: [Act] YAPC::EU 2016 ready for live (basic features) In-Reply-To: <20160429075939.GC2479@zok> References: <032801d1a170$7c25b4b0$74711e10$@cluj.pm> <20160429075939.GC2479@zok> Message-ID: Hi, Could someone make an alias yapc.eu/2016 please? On Fri, Apr 29, 2016 at 9:59 AM, Philippe Bruhat (BooK) wrote: > On Thu, Apr 28, 2016 at 08:07:45PM +0300, Amalia wrote: >> >> Also, please let us know how to push changes to live. >> > > Quoting S?bastien: > >> The production site uses the production branch of the repository, >> while the test site uses the master branch. Both are updated every >> 5 minutes. > > -- > Philippe Bruhat (BooK) > > The faster the climb, the swifter the fall. > (Moral from Groo The Wanderer #87 (Epic)) > _______________________________________________ > Act mailing list > Act at mongueurs.net > http://listes.mongueurs.net/mailman/listinfo/act -- Andrew Shitov ______________________________________________________________________ andy at shitov.ru | http://shitov.ru