-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a staging server #6
Comments
@jeremiahnpatterson let me know if you want any help getting this set up, have questions, etc. |
@danielbachhuber thanks, I'm sure I'll have a few along the way. I'll ping you when I start work on this. |
Any movement on a staging server yet? I'm making some good progress; and I should be at a point to share that soon. |
I've created a staging server at ona13.danielbachhuber.com. It's behind a login wall. @jeremiahnpatterson @anekola @jeannebrooks I've created accounts for each of you, and you should have passwords in your email. @jeremiahnpatterson It might be worthwhile for you to do an export of production content, import into the staging site, and get things looking in staging like they look in production. @anekola I've set up a Git auto-deploy mechanism, so any pushes to the master branch will go live to staging automatically. You might consider using hub to turn some issues into pull requests so we can do a code review for anything significant before pushing to production. |
Oh, and Github push notifications will go to Jeremiah, Adam and I from now on. |
Great, thanks Daniel. We use Git at Pew through SmartGit, but not Github, so there will be a bit of a learning curve for me. I'm attending a Git workshop through DC jQuery next week, so I should be caught up by then; but I'm not sure what to do with hub... |
Ah, ignore the hub suggestion then :) I think you'll be able to use Feel free to ping me on Skype tomorrow if you'd like help getting set up On Thu, May 23, 2013 at 7:04 PM, anekola notifications@github.com wrote:
|
Hi Daniel, I'm working on setting up the staging server today. It's missing a few plugins we'll need:
Looks like the Git branch is just for the theme. Could you add these? |
Why do you need those menu plugins? On Sun, Jun 2, 2013 at 11:30 AM, anekola notifications@github.com wrote:
|
The site was initially set up using them. |
@jeremiahnpatterson Can you pull them off the production server? It looks like they were paid plugins, and I can't easily download them. |
Yeah. Do you want me to send them to you in a zip file? Or can you send me FTP info for http://ona13.danielbachhuber.com/? Also, wanted to let you know my kitchen flooded some tonight; it wasn't terrible but it killed my productivity. I should be able to work on this most nights this week, though. |
Emailing me a ZIP file is fine On Sun, Jun 2, 2013 at 6:54 PM, anekola notifications@github.com wrote:
|
Hey guys sorry I'm late to the party. Daniel I'm emailing you the plugins now. |
Thanks so much, Jeremiah. On Mon, Jun 3, 2013 at 9:02 AM, jeremiahnpatterson <notifications@github.com
|
Plugins are installed. |
One last thing with the plugin, Daniel. I just discovered a section at the bottom marked * ONA13 *, could you remove that? I'm adding the styles into the theme. EDIT - Sorry, that's in the basic.css file. |
Sorry, I'm not sure I follow what you want me to do. Can you share a screenshot? |
Hey Daniel - were you able to remove the above CSS? After that the initial nav changes and everything should be set up on the staging server. If you like them, we should be able to push them to the live site. Let me know what you think. |
Erps, removed. |
We should have a staging server available at something like ona13.staging.journalists.org so we can test code and stage content before going live.
Ideally, this would require users to be logged in to visit. Also, a few of us should have SSH access so we can switch branches, etc.
Most development should be happening locally, however.
The text was updated successfully, but these errors were encountered: