Set up a minimal web presence under subscribe.adblockplus.org

[trev]

Background

See #2208, we need to establish a minimal web presence under subscribe.adblockplus.org as a first step.

What to change

• Set up a subscribe.adblockplus.org repository, analogous to web.eyeo.com. Initialize it with some minimal content required for our CMS.
• Include the subscribe.* sub-domain with our DNS records
• Get an SSL certificate for the subscribe.adblockplus.org subdomain.
• Set up a new web server for the subscribe.adblockplus.org using the new SSL certificate and displaying the contents of the subscribe.adblockplus.org repository.

Overview

Ticket	Status	Resolution	Summary	Component	Owner
#3292	closed	fixed	Obtain SSL certificate for subscribe.adblockplus.org	Office-IT	fred
#3293	closed	fixed	Introduce subscribe.adblockplus.org repository	Infrastructure	matze
#3295	closed	fixed	Setup server back-end for subscribe.adblockplus.org	Infrastructure	matze
#3881	closed	fixed	Provide sitescripts.ini even if no settings are required	Infrastructure	matze

[matze]

There are a few questions I'd like to have answered upfront:

• How many users do you expect in general, e.g. per hour or per day?
• Though the content is obviously static for now, are the plans to introduce some sort of application logic in the near or mid-distant future?
• If so, who can describe those plans?
• How often do you expect the content to change in general?
• Does anybody (e.g. @kirill) need access to the server, other than HTTPS and beside the usual suspects?
• Is there an explicit time frame due to dependencies of other tickets or upcoming tasks?

I am aware that we may not have precise information for every point, though any additional info will help calculating resource requirements etc.

[trev]

How many users do you expect in general, e.g. per hour or per day?

Not too many. Apart from search bots, the only visitors will be people clicking on a "subscribe" link somewhere without having Adblock Plus installed. It will likely have less traffic than eyeo.com for the foreseeable future.

Though the content is obviously static for now, are the plans to introduce some sort of application logic in the near or mid-distant future?

No. The purpose of that website should be purely informative, it will merely direct people to the available resources.

How often do you expect the content to change in general?

Not very often, after the initial stage only every few months. However, right now all our CMS servers update the entire content every 10 minutes.

Does anybody (e.g. @kirill) need access to the server, other than HTTPS and beside the usual suspects?

Yes, we will have to process the logs of that server, like for any other web server.

Is there an explicit time frame due to dependencies of other tickets or upcoming tasks?

Not yet, but that task will likely make it to the Q2 roadmap.

will help calculating resource requirements

Well, a while ago we chose to use identical hardware for most tasks, given that pretty much all our applications are traffic-bound and not CPU-bound.

[matze]

OK then, that should be enough for now, thank you.

[sebastian]

There is no user called snoack here. ;)

[matze]

The majority of steps have been done, most resources are available already:

• The ​subscribe.adblockplus.org repository has been created
• A minimal ​initial commit has been pushed by @saroyanm, for testing purpose
• All necessary ​updates to the infrastructure repository have been performed
• The server backend is up and running

The official introduction of the subscribe.adblockplus.org domain, namely the creation of the required DNS records (see #3295), has been delayed until the SSL certificate has been aquired and imported into the production setup (see #3292).