#2066: publish new website
---------------------------+-------------------------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: Systems Admin | Keywords:
---------------------------+-------------------------------------
Setting up a ticket to schedule new website - going to recommend January
15th, giving everyone a couple weeks to double check content before it
goes live.
The website is located at http://staging.www.osgeo.org and will be
published as http://www.osgeo.org
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------------+--------------------------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------------------------
Comment (by robe):
Just outlining the steps that need to be done to make it happen
1) DNS change -- Alex or strk want to take ownership of this when it
comes time. I don't have access to DNS (wildintellect, strk) -- so A
record - 141.138.205.23 (osgeo.org, CNAME www.osgeo.org), and what we
currently have for osgeo.org/www.osgeo.org becomes old.osgeo.org (or
whatever we decided on)
2) config.php needs to be changed to reflect https://www.osgeo.org (robe)
3) LetsEncrypt SSL for www.osgeo.org (robe)
4) MySQL update fix any hard-coded staging.www.osgeo.org that may have
occurred while people were editing and make them relative links (would be
nice if we can figure out a way in wordpress to prevent hardcoded links
from happening) - (robe)
5) Any redirects from old site we need to keep (this we may have to do
piecemeal ) -- robe, strk, jive
6) Make sure robots.txt is right and old.osgeo.org has a robots.txt that
says do not crawl.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:1>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------------+--------------------------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------------------------
Comment (by wildintellect):
Odd, my comments earlier didn't seem to post.
1. Staging was intended to always remain the staging server. 3rd party
hosting was only, until no longer needed. No config changes to be made.
2. So we actually now need to begin the Production deployment. If that's
on new hardware or OSUOSL hosted virtualization we need to decide and
start down that path.
3. In the interim we could host Production and Staging on the same
machine, 3rd party just to get it live sooner.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:2>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------------+--------------------------------------
Reporter: jive | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------------------------
Comment (by robe):
I think we want to do 3 as I don't see us getting new hardware before
January 15th. Do you have proposed specs yet even and it's fairly trivial
to setup a second site on this box.
So I think the above steps still hold.
I'll add to my list todo
Create whole new site www.osgeo.org/osgeo.org on the current server and
keep staging as is, aside from changing the repointing staging to backup
db called osgeo_staging.
I think once we get new server, we should install things differently
1) We are going with PHP7 and not PHP5 that is currently installed in
staging. Not sure why GI installed PHP 5. Might be because that's what
we have on our old hardware and they wanted something we could easily
support instead of PHP 7 to begin with.
2) We are going to go with MariaDB 10+ and ditch MYSQL. I want as little
to do with Oracle as possible, I'm sure others share my sentiment.
I run other wordpress sites on the above so don't foresee an issue with
switching, but we'd probably want a week of grace before we switch over to
the new hardware just in case.
When we get new hardware, probably doesn't make sense to hold on to this
cloud instance beyond our subscription period. We can run both staging
and production on our own hardware.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:3>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------+--------------------------------------
Reporter: jive | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: WebSite | Resolution:
Keywords: |
---------------------+--------------------------------------
Changes (by jive):
* owner: sac@… => webcom@…
* component: Systems Admin => WebSite
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:4>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------+--------------------------------------
Reporter: jive | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: WebSite | Resolution:
Keywords: |
---------------------+--------------------------------------
Comment (by robe):
Okay I've got a Debian 9.3 VM with PHP 7, MariaDb 10.1 with the last
night's wordpress backup loaded and using LetsEncrypt. At a cursory
glance all seems to be working without any changes (aside from getting rid
of php5 mod something or other in one of the configs) and fiddle with
.htaccess (and minor changes cause I'm proxing the traffic).
I also have SSH access via LDAP working as well and also working on
Wordpress.
At a glance all looks good. Now all I need is for someone to make a DNS
entry so we can start testing.
Can someone either do a CNAME or A
CNAME staging2.www.osgeo.org to winnie.postgis.net
or
A staging2.www.osgeo.org 50.70.240.108
I'll also put up the instructions for setup on the wiki. I tried to make
as detailed of instructions as possible.
Most of the time spent was figuring out which extensions were missing as
some were missed in our setup docs.
If I had to do it all again with what I know now, shouldn't have taken
more than 2 hrs with a brand new debian box and much of that 2 hrs would
just be waiting for things to install.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:5>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------+--------------------------------------
Reporter: jive | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: WebSite | Resolution:
Keywords: |
---------------------+--------------------------------------
Comment (by strk):
I've added A record, please confirm and close.
From my side: staging2.www.osgeo.org has address 50.70.240.108
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:6>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------+--------------------------------------
Reporter: jive | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: WebSite | Resolution:
Keywords: |
---------------------+--------------------------------------
Comment (by robe):
Sorry I mistyped it should be 50.78.240.108
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:7>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------+--------------------------------------
Reporter: jive | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: WebSite | Resolution:
Keywords: |
---------------------+--------------------------------------
Comment (by strk):
Record updated, now pointing to 50.78.240.108
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:8>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------+--------------------------------------
Reporter: jive | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: WebSite | Resolution:
Keywords: |
---------------------+--------------------------------------
Comment (by robe):
Thanks, strk. I can get to it now.
I put my instructions here
https://wiki.osgeo.org/wiki/SAC:staging2.www.osgeo.org
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:9>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2066: publish new website
---------------------+--------------------------------------
Reporter: jive | Owner: webcom@…
Type: task | Status: closed
Priority: normal | Milestone: Website rebranding 2017
Component: WebSite | Resolution: fixed
Keywords: |
---------------------+--------------------------------------
Changes (by robe):
* status: new => closed
* resolution: => fixed
Comment:
this is done and I think the PHP7 testing is already detailed in another
ticket.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2066#comment:10>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.