<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head></head><body><div style="font-size: 12pt; font-family: Calibri,sans-serif;"><div>Works now. Thanks!</div><div><br></div><div>Sendt fra min HTC</div><br><div id="htc_header">----- Reply message -----<br>Fra: "Sébastien Aperghis-Tramoni" <sebastien@aperghis.net><br>Til: "The Act users mailing list" <act@mongueurs.net><br>Kopi: <mojoconf@oslo.pm><br>Emne: New event: mojo2014<br>Dato: tir., jan. 21, 2014 19:19</div></div><br><pre style="word-wrap: break-word; white-space: pre-wrap;">Salve J Nilsen wrote:
> Hi Sébastien,
Hello Salve,
> Thanks for your quick reply! :D
>
>
> Sébastien Aperghis-Tramoni said:
> > Salve J Nilsen wrote:
> >>
> >> Oslo Perl Mongers will be organizing a one-day Mojolicious
> >> conference in Oslo on May 24th 2014. It'll be a one-day
> >> conference all about Mojolicious, with the goal of gathering
> >> the whole core team for the first time, with a course/training
> >> day preceeding it, and a hackathon on the day after. It'll
> >> be cool. :)
> >>
> >>
> >> 1) We'd like to use Act for managing this event; Can we please
> >> get the "mojo2014" conference code/site set up?
> >
> > The test is online: <a href="http://test.mongueurs.net/mojo2014/">http://test.mongueurs.net/mojo2014/</a>
>
> Thank you, it works wonderfully.
>
>
> >> 2) Could you also set up Act to reply to act.mojoconf.org,
> >> redirecting to the appropriate url?
> >
> > I've started configuring the vhost, but the DNS record will be
> > needed in order to finalize that part.
>
> Great, we'll set up a CNAME to conferences.mongueurs.net soon.
>
>
> >> 3) And finally create some logins with the following public SSH
> >> keys, so we can start setting up the site. :)
> >
> > Created all these accounts, with symlinks in your respective homes
> > to the conference files.
>
> Thanks!
You're welcome.
> nicomen has tried to verify that he has access, but can't log in.
> Are there any issues with directory/file permissions, or the key
> when it was copied into ~nicomen/.ssh/authorized_keys? (The file
> should contain one key per line).
I can't see any errors in the system logs, but /var was full during
the afternoon, so it may be the reason for both. Can he try again?
--
Sébastien Aperghis-Tramoni
Close the world, txEn eht nepO.
</pre></body></html>