staging

Best practices for Ruby on Rails *feature* deployment? [closed]

我怕爱的太早我们不能终老 提交于 2019-12-08 02:45:56
问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 5 years ago . We run 2 different environments on our server - say, production.mydomain.com and staging.mydomain.com The staging environment is nearly identical to the production environment, except that it often has several new features which are being reviewed (eg new_user_profile, image

How to clone wordpress site for the develope purpose?

浪子不回头ぞ 提交于 2019-12-08 02:34:23
问题 I have a wordpress site and I have to do modifications very often so i would like to create clone of that website for testing because i would like to test my modification first for a few days before i put them on my site. There are links to the "real" site everywhere so i'm not sure how to do that. UPDATE (improved explanation): Problems: links are absolute this need to be online so other developers can test site 回答1: Copy/paste your entire files from your domain to everywhere you want as

View website live after Git push [duplicate]

最后都变了- 提交于 2019-12-07 19:09:04
问题 This question already has answers here : Closed 7 years ago . Possible Duplicate: Git Post-Receive Hook for Website Staging I started learning Git today and I'm stuck on one thing. When I push my local production repository to my remote staging repository, I would like to immediately be able to view my newly pushed files live. When I try to look for my files in my remote repository (via an FTP client), I can't find them. Do I need to perform some advanced Git magic in order to achieve this

How to clone wordpress site for the develope purpose?

耗尽温柔 提交于 2019-12-06 10:59:53
I have a wordpress site and I have to do modifications very often so i would like to create clone of that website for testing because i would like to test my modification first for a few days before i put them on my site. There are links to the "real" site everywhere so i'm not sure how to do that. UPDATE (improved explanation): Problems: links are absolute this need to be online so other developers can test site Copy/paste your entire files from your domain to everywhere you want as first step. Go to the phpMyAdmin or use a tool that permit to you to export your database as .sql . Open the

Best practices for Ruby on Rails *feature* deployment? [closed]

泪湿孤枕 提交于 2019-12-06 06:35:04
Closed . This question needs to be more focused . It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post . Closed 5 years ago . We run 2 different environments on our server - say, production.mydomain.com and staging.mydomain.com The staging environment is nearly identical to the production environment, except that it often has several new features which are being reviewed (eg new_user_profile, image_tagging, etc). These features are individually accepted by the client at different times. What is the best

View website live after Git push [duplicate]

馋奶兔 提交于 2019-12-06 06:08:20
This question already has answers here : Closed 7 years ago . Possible Duplicate: Git Post-Receive Hook for Website Staging I started learning Git today and I'm stuck on one thing. When I push my local production repository to my remote staging repository, I would like to immediately be able to view my newly pushed files live. When I try to look for my files in my remote repository (via an FTP client), I can't find them. Do I need to perform some advanced Git magic in order to achieve this (hooks?)? What is best practice for this situation? Again, I'm new to Git and don't fully understand the

staging and live app with capistrano

十年热恋 提交于 2019-12-06 02:32:53
问题 I thought I'd do a simple yet potentially very useful thing, and create another symlink called live, that points to an arbitrary release, and leave current at the head where it usually is: 20120519235508 20120521004833 20120521024312 <-- live 20120521025150 20120521030449 <-- current I then configured www.mysite.com to hit live/public and stage.mysite.com to hit current/public Unfortunately both hosts seem to run the same app, and not 2 different apps. I've confirmed the httpd.conf has the

Git invert staging area

℡╲_俬逩灬. 提交于 2019-12-05 18:16:20
问题 I have got changes in my staging area, and others not staged yet (some files have changes both in and out the staging area). I would like to invert the content of the staging area and the changes which are not staged. Does a shortcut exist in order to do that , without doing more complex actions like local side-branch commits, or diffs, or stashes [etc.]? Thanks. 回答1: Here’s how I do it: Commit the index to a temporary commit Commit the remainder to a secondary temporary commit Switch the

What is the main purpose and sense to have staging server the same as production?

。_饼干妹妹 提交于 2019-12-05 17:27:32
In our company we have staging and production servers. I'm trying to have them in state 1:1 after latest release. We've got web application running on several host and many instances of it. The issue is that I am an advocate of having the same architecture (structure) of web applications on staging and production servers to easily test new features and avoid creating of new bugs with new releases. But not everyone agree with me, and for them is not a such big deal to have different connection between staging application instances. Even maybe to have more application and connections between

Running test on Production Code/Server

时光总嘲笑我的痴心妄想 提交于 2019-12-05 10:43:46
I'm relatively inexperienced when it comes to Unit Testing/Automated Testing, so pardon the question if it doesn't make any sense. The current code base I'm working on is so tightly coupled that I'll need to refactor most of the code before ever being able to run unit tests on it, so I read some posts and discovered Selenium, which I think is a really cool program. My client would like specific automated tests to run every ten minutes on our production server to ensure that our site is operational, and that certain features/aspects are running normally. I've never really thought to run tests