[Fedora Magazine] Wordpress success!

[Máirín Duffy]

Hi folks,

Nirik set up fedora-mag-admin(a)fedoraproject.org for us and I used it to
set up an OpenShift account. I discovered a few things:

- It's dead simple to set up WordPress on OpenShift.

- WordPress has a built-in update system that seems to work fine on
OpenShift, so maintenance should not be too difficult.

- I tested out the OpenID plugin for WordPress with my FAS account, and
it works fine. We can limit account creations to only those with valid
OpenIDs. Once someone logs in with an OpenID and creates an account, an
admin can promote them to any role needed.

So, it's looking good to run Fedora Magazine on OpenShift / Wordpress.
Here's the running instance I have now:

http://wp-fedoramag.rhcloud.com/

~m

[Kevin Fenzi]

On Tue, 11 Dec 2012 18:12:57 -0500
Máirín Duffy <duffy(a)fedoraproject.org&gt; wrote:

>  Hi folks,
>  
>  Nirik set up fedora-mag-admin(a)fedoraproject.org for us and I used it
>  to set up an OpenShift account. I discovered a few things:
>  
>  - It's dead simple to set up WordPress on OpenShift.
>  
>  - WordPress has a built-in update system that seems to work fine on
>  OpenShift, so maintenance should not be too difficult.
>  
>  - I tested out the OpenID plugin for WordPress with my FAS account,
>  and it works fine. We can limit account creations to only those with
>  valid OpenIDs. Once someone logs in with an OpenID and creates an
>  account, an admin can promote them to any role needed.
>  
>  So, it's looking good to run Fedora Magazine on OpenShift / Wordpress.
>  Here's the running instance I have now:
>  
>  http://wp-fedoramag.rhcloud.com/ 
Cool!

I'll add that it's easy with openshift to associate another
domain/hostname, so we can make this
'fedora-magazine.fedoraproject.org' or the like if that's desired. 

kevin

[Máirín Duffy]

Hi,

On Tue, 2012-12-11 at 18:12 -0500, Máirín Duffy wrote:
>  http://wp-fedoramag.rhcloud.com/ 
So you might have noticed :( I screwed it up before I left the office
but it should be easy to fix; I will fix it tomorrow.

~m

[Máirín Duffy]

Hi folks,

So a quick update: the Wordpress install is secured and ready-to-go! I
updated the OpenShift repo backing it with WordPress 3.5. Some technical
details for future reference below [1]. 

The hostname http://wp-fedoramag.rhcloud.com is definitely not meant to
be the final / real URL we use and publicize. Like Kevin already
mentioned, we can hook it up to whatever URL we'd like. We could do
magazine.fedoraproject.org or fedoramagazine.com as Ruth suggested.

I personally like going for a top-level domain like fedoramagazine.com
better than using a subdomain, although it might be good to have a
subdomain redirect to the top-level domain. 

I'm going to start talking to the design team about coming up with
mockups for the look and feel and coming up with a custom WordPress
theme for this, but you folks are all set to start filling in content!

~m

[1] I was running into an issue where I was trying to update the keys
and salt for the WordPress install to secure it using the OpenShift
repo. When I git pushed the changes, it reverted all the app updates I
had made such as installing OpenID and upgrading to WP 3.5. Talking to
the OpenShift guys, I found out this was because the changes the app
made to the WordPress install aren't automatically committed to the git
repo. So what you have to do to make changes to WordPress on the
filesystem is run the rhc-snapshot command to grab all of the app data,
and copy the 'php-5.3/repo/php' directory over top the 'php' directory
in the git repo and then do a git add *, git commit, and git push. So
the general workflow for updating should be:

- Make any updates / plugin or theme installations as needed directly in
the Wordpress admin UI.

- Use the 'rhc-snapshot' command to pull down the changes, and commit
them to the OpenShift git repo to make sure they are tracked.

[Stephen John Smoogen]

On 12 December 2012 12:25, Máirín Duffy <duffy(a)fedoraproject.org&gt; wrote:
>  Hi folks,
>
>  So a quick update: the Wordpress install is secured and ready-to-go! I
>  updated the OpenShift repo backing it with WordPress 3.5. Some technical
>  details for future reference below [1].
>
>  The hostname http://wp-fedoramag.rhcloud.com is definitely not meant to
>  be the final / real URL we use and publicize. Like Kevin already
>  mentioned, we can hook it up to whatever URL we'd like. We could do
>  magazine.fedoraproject.org or fedoramagazine.com as Ruth suggested.
>
>  I personally like going for a top-level domain like fedoramagazine.com
>  better than using a subdomain, although it might be good to have a
>  subdomain redirect to the top-level domain. 
Ok there will need to be some budget involved here. Getting the domain
name, getting any ssl certs for the domain name, etc.


-- 
Stephen J Smoogen.
"Don't derail a useful feature for the 99% because you're not in it."
Linus Torvalds
"Years ago my mother used to say to me,... Elwood, you must be oh
so smart or oh so pleasant. Well, for years I was smart. I
recommend pleasant. You may quote me."  —James Stewart as Elwood P. Dowd

[Jason Brooks]

>  [1] I was running into an issue where I was trying to update the keys
>  and salt for the WordPress install to secure it using the OpenShift
>  repo. When I git pushed the changes, it reverted all the app updates I
>  had made such as installing OpenID and upgrading to WP 3.5. Talking to
>  the OpenShift guys, I found out this was because the changes the app
>  made to the WordPress install aren't automatically committed to the git
>  repo. So what you have to do to make changes to WordPress on the
>  filesystem is run the rhc-snapshot command to grab all of the app data,
>  and copy the 'php-5.3/repo/php' directory over top the 'php' directory
>  in the git repo and then do a git add *, git commit, and git push. So
>  the general workflow for updating should be:
>
>  - Make any updates / plugin or theme installations as needed directly in
>  the Wordpress admin UI.
>
>  - Use the 'rhc-snapshot' command to pull down the changes, and commit
>  them to the OpenShift git repo to make sure they are tracked. 
When I update my wordpress on openshift, I don't use the web admin
interface, I make the changes to my local git repo and push from
there. I think it ends up being a simpler workflow. Also, I believe
the rhc commands are only accessible through one openshift account,
but you can add multiple ssh keys to openshift to allow different
people to interact w/ it through git.


>  --
>  marketing mailing list
>  marketing(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/marketing

[Sarah White]

I'm +1 for fedoramagazine.com and having magazine.fedoraproject.org,
fedoramagazine.org, etc. redirect to it if necessary.

-S


On Wed, Dec 12, 2012 at 1:04 PM, Jason Brooks <jasonbrooks(a)fedoraproject.org
>  wrote: 
>  >
>  > [1] I was running into an issue where I was trying to update the keys
>  > and salt for the WordPress install to secure it using the OpenShift
>  > repo. When I git pushed the changes, it reverted all the app updates I
>  > had made such as installing OpenID and upgrading to WP 3.5. Talking to
>  > the OpenShift guys, I found out this was because the changes the app
>  > made to the WordPress install aren't automatically committed to the git
>  > repo. So what you have to do to make changes to WordPress on the
>  > filesystem is run the rhc-snapshot command to grab all of the app data,
>  > and copy the 'php-5.3/repo/php' directory over top the 'php'
> directory
>  > in the git repo and then do a git add *, git commit, and git push. So
>  > the general workflow for updating should be:
>  >
>  > - Make any updates / plugin or theme installations as needed directly in
>  > the Wordpress admin UI.
>  >
>  > - Use the 'rhc-snapshot' command to pull down the changes, and commit
>  > them to the OpenShift git repo to make sure they are tracked.
>
>  When I update my wordpress on openshift, I don't use the web admin
>  interface, I make the changes to my local git repo and push from
>  there. I think it ends up being a simpler workflow. Also, I believe
>  the rhc commands are only accessible through one openshift account,
>  but you can add multiple ssh keys to openshift to allow different
>  people to interact w/ it through git.
>
>
>  >
>  > --
>  > marketing mailing list
>  > marketing(a)lists.fedoraproject.org
>  > https://admin.fedoraproject.org/mailman/listinfo/marketing
>  --
>  marketing mailing list
>  marketing(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/marketing
>

[Jason Brooks]

Good rundown of post-install issues related to WP on OpenShift:
http://blog.sumostyle.net/2012/12/moved-to-openshift/

On Tue, Dec 11, 2012 at 3:12 PM, Máirín Duffy <duffy(a)fedoraproject.org&gt; wrote:
>  Hi folks,
>
>  Nirik set up fedora-mag-admin(a)fedoraproject.org for us and I used it to
>  set up an OpenShift account. I discovered a few things:
>
>  - It's dead simple to set up WordPress on OpenShift.
>
>  - WordPress has a built-in update system that seems to work fine on
>  OpenShift, so maintenance should not be too difficult.
>
>  - I tested out the OpenID plugin for WordPress with my FAS account, and
>  it works fine. We can limit account creations to only those with valid
>  OpenIDs. Once someone logs in with an OpenID and creates an account, an
>  admin can promote them to any role needed.
>
>  So, it's looking good to run Fedora Magazine on OpenShift / Wordpress.
>  Here's the running instance I have now:
>
>  http://wp-fedoramag.rhcloud.com/
>
>  ~m
>
>
>  --
>  marketing mailing list
>  marketing(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/marketing