[Systems] Hosting with SL

[Matthew Ciao]

Hi Prasoon/Sam,

the SSH solution is useful only if you need a quick and 'dirty' :) way to
start working/testing.

I am pretty sure that you guys work on a *nix system so you should have
OpenSSH. It's just a matter of SSHing into the server and spending 15
seconds to configure Firefox (or Chrom /e/ium), that way you can
test/configure/break your application without exposing any resource the the
Net.

However I don't have enough details about the development status of your
project so you might as well be ready to jump to production right away - in
that case you could go directly to the webserver configuration!

Up to you folks!

Matthew


On 20 August 2014 22:38, Prasoon Shukla <prasoon92.iitr at gmail.com> wrote:

> Hey all. Just got back from classes.
>
> @Matthew, @Sam: I have no idea how ssh tunneling works and I've never done
> it before,  so I guess if you guys think it's alright then it's fine by me,
> too.
> ᐧ
>
>
> On Wed, Aug 20, 2014 at 3:49 PM, Sam P. <sam.parkinson3 at gmail.com> wrote:
>
>> I like Matthew's the idea of ssh proxying it, but wouldn't a nginx/apache
>> proxy be more appropriate?  That seems to be how all the other SL stuff
>> goes.
>>
>> Did you dockerify the redirector thing?  Just wondering :)
>>
>>
>> On Wed, Aug 20, 2014 at 8:44 AM, Matthew Ciao <matthew at laptop.org.au>
>> wrote:
>>
>>> On Wednesday, 20 August 2014, Bernie Innocenti <bernie at sugarlabs.org>
>>> wrote:
>>>
>>>> Status update: Freedom is now running Ubuntu 14.04 and still holding
>>>> well.
>>>>
>>>> I installed docker.io and tried setting up a simple container to ensure
>>>> everything works. It did.
>>>
>>>
>>> Nice one!
>>>
>>>
>>>>
>>>> Now we'd be ready to deploy your image and experiment with it. Sam &
>>>> Matthew: what should I do next? I guess you need a public ip and a dns
>>>> entry for it?
>>>
>>>
>>> For testing purpose I'd SSH tunnel into the system and use dynamic port
>>> forwarding to the application listening on localhost.
>>>
>>> That way you don't need to bind Docker to a WAN facing interface.
>>>
>>> It's a good security measure that avoids exposing the testing instance
>>> until is fully ready and secured.
>>>
>>> If security is not a concern in this case, then public IP and a DNS
>>> CNAME record should do the trick!
>>>
>>> Sam/Prasoon what do you think?
>>>
>>> Cheers
>>>
>>>
>>>>
>>>> For fast turnaround, please chat me on #sugar, as I don't check my
>>>> personal email very often during work days.
>>>>
>>>> On 08/18/2014 10:20 PM, Matthew Ciao wrote:
>>>> > Sure, I'm always on IRC #olpc-au (@freenode) but if you let me know
>>>> > where you folks hang out I'll be there..
>>>> >
>>>> >
>>>> > On 19 August 2014 12:16, Bernie Innocenti <bernie at sugarlabs.org
>>>> > <mailto:bernie at sugarlabs.org>> wrote:
>>>> >
>>>> >     Dogi and I are meeting at my place in 20 minutes to start
>>>> upgrading
>>>> >     freedom to Ubuntu 14.04.
>>>> >
>>>> >     Then we'll install Docker. If you'll be around in about 1h, any
>>>> help is
>>>> >     welcome.
>>>> >
>>>> >
>>>> >     On 08/18/2014 10:14 PM, Matthew Ciao wrote:
>>>> >     > Hi folks,
>>>> >     >
>>>> >     > I have some experience with Docker on virtualized systems (KVM)
>>>> -
>>>> >     we use
>>>> >     > it to run our build/cross-compile environments for low level
>>>> driver
>>>> >     > development here at OLPCAU.
>>>> >     >
>>>> >     > Glad to lend a hand if needed however Bernie was first so I am
>>>> >     second in
>>>> >     > the queue of available people for this project :)
>>>> >     >
>>>> >     >
>>>> >     > On 19 August 2014 07:06, Sam P. <sam.parkinson3 at gmail.com
>>>> >     <mailto:sam.parkinson3 at gmail.com>
>>>> >     > <mailto:sam.parkinson3 at gmail.com
>>>> >     <mailto:sam.parkinson3 at gmail.com>>> wrote:
>>>> >     >
>>>> >     >     Hey,
>>>> >     >
>>>> >     >     > What access level do you need in order to setup and
>>>> >     configure your
>>>> >     >     > container(s)? I'd rather not give out root access to our
>>>> >     production
>>>> >     >     > hosts, but several SL sysadmins can help you.
>>>> >     >
>>>> >     >     Normally you need root but you can set up a docker group:
>>>> >     >
>>>> >
>>>> https://docs.docker.com/installation/binaries/#giving-non-root-access
>>>> >     >
>>>> >     >     Sam
>>>> >     >
>>>> >     >
>>>> >
>>>> >
>>>> >     --
>>>> >     Bernie Innocenti
>>>> >     Sugar Labs Infrastructure Team
>>>> >     http://wiki.sugarlabs.org/go/Infrastructure_Team
>>>> >
>>>> >
>>>>
>>>>
>>>> --
>>>> Bernie Innocenti
>>>> Sugar Labs Infrastructure Team
>>>> http://wiki.sugarlabs.org/go/Infrastructure_Team
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/private/systems/attachments/20140820/94d10402/attachment.html>