Opened 8 years ago

Closed 8 years ago

#4313 closed task (implemented)

Please create cloud.torproject.org

Reported by: runa Owned by: phobos
Priority: Medium Milestone:
Component: Webpages/Website Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

As part of #4057, I'd like to have access to put content on cloud.torproject.org.

Child Tickets

Change History (10)

comment:1 Changed 8 years ago by phobos

How are we putting content up here? Is this hosted by us or expresstech? Is it a static html site? I'd prefer to just redirect cloud.tpo to the current domain.

comment:2 in reply to:  1 Changed 8 years ago by runa

Replying to phobos:

How are we putting content up here? Is this hosted by us or expresstech? Is it a static html site? I'd prefer to just redirect cloud.tpo to the current domain.

(1) Jeremy put together the design and emailed me everything. I just need rw access to a directory so that I can put it online.

(2) This will be hosted by us. The Tor Project will host the website and maintain the images. Expression Technologies will run bridges.

(3) The page is some static HTML, some javascript and some images.

Can we please move this forward now?

comment:3 Changed 8 years ago by Sebastian

istr that we talked about it on irc at some point, and reached the conclusion tpo/cloud would be fine too? That'd be easy to achieve

comment:4 Changed 8 years ago by phobos

How about we put this in projects, since it is a project of ours. https://www.torproject.org/projects/cloud is a fine url as any.

comment:5 Changed 8 years ago by runa

Wait what? I started to create torproject.org/projects/cloud last month, only to be told that we should make it completely separate (i.e. cloud.torproject.org with a design different than what we have on www.torproject.org).

comment:6 Changed 8 years ago by phobos

Status: newaccepted

I have no idea where these discussions happened. I created cloud.torproject.org. My original thought was that someone else creates 'tor cloud servers' like 'tor servers' and runs their own thing, not us. However, it seems no one else is doing it but us, so we'll just host some images and be a lead generation tool for amazon aws.

cloud.torproject.org is awaiting html. where do I find the tarball?

comment:7 in reply to:  6 ; Changed 8 years ago by runa

Replying to phobos:

I have no idea where these discussions happened. I created cloud.torproject.org. My original thought was that someone else creates 'tor cloud servers' like 'tor servers' and runs their own thing, not us. However, it seems no one else is doing it but us, so we'll just host some images and be a lead generation tool for amazon aws.

What do you mean by "runs their own thing"? Anyone can run bridges, but someone will have to maintain the images and and publish them somewhere.

cloud.torproject.org is awaiting html. where do I find the tarball?

You've got mail. Can I have access to edit the html once it's up? I want to update the cloud images and the documentation that we have.

comment:8 in reply to:  7 ; Changed 8 years ago by phobos

Replying to runa:

What do you mean by "runs their own thing"? Anyone can run bridges, but someone will have to maintain the images and and publish them somewhere.

I mean that someone else runs tor cloud servers on their own, we were going to have nothing to do with it. It seems we've created images so anyone with an AWS account can run their own bridges/relays. Maybe torservers.net can use our images and cause more bridges/relays to appear.

You've got mail. Can I have access to edit the html once it's up? I want to update the cloud images and the documentation that we have.

And you have git patches. Right now, only root as access to the non-www.tpo sites, like cloud.tpo until we figure out a better model for permissions.

comment:9 in reply to:  8 ; Changed 8 years ago by runa

Replying to phobos:

Replying to runa:

What do you mean by "runs their own thing"? Anyone can run bridges, but someone will have to maintain the images and and publish them somewhere.

I mean that someone else runs tor cloud servers on their own, we were going to have nothing to do with it. It seems we've created images so anyone with an AWS account can run their own bridges/relays. Maybe torservers.net can use our images and cause more bridges/relays to appear.

Oh, so you didn't want us to maintain the images either? I thought that was the plan all along.

You've got mail. Can I have access to edit the html once it's up? I want to update the cloud images and the documentation that we have.

And you have git patches. Right now, only root as access to the non-www.tpo sites, like cloud.tpo until we figure out a better model for permissions.

Thanks, I'll add them to tor-cloud.git later today. In the future, should I just ask you to pull changes from my git repo and push things live?

comment:10 in reply to:  9 Changed 8 years ago by phobos

Resolution: implemented
Status: acceptedclosed

Replying to runa:

Oh, so you didn't want us to maintain the images either? I thought that was the plan all along.

The original plan was 'they who create and run the images, do it all'. This was because TPI cannot run parts of the Tor network, lest we accept far more liability than we can afford, nevermind trust issues, legal ISP issues, etc.

This plan is just providing AWS images, like packages, that we will not take funding to run. Someone with their own AWS account can spin up our images and join the tor network. These AWS images are no different than downloading the bridge-by-default or relay-by-default package and running it on your own computer.

Thanks, I'll add them to tor-cloud.git later today. In the future, should I just ask you to pull changes from my git repo and push things live?

For now, yes.

Note: See TracTickets for help on using tickets.