|
Author
|
Message
|
|
Steinar A
|
Monday 27 September 2010 7:15:50 am
.. ..
|
|
Quoc Huy Nguyen Dinh
|
Monday 27 September 2010 8:52:21 am
Hi, 1. Moving eZ Publish from one server to another is a matter of dumping the MySQL DB and re-importing it on the new server and then copy over the codebase and probably edit few config files. You need some MySQL / Linux administration skills. 2. Developing a price comparison search engine should be possible. 3. Have a look at the partners list: http://ez.no/partners/worldwide_partners/(country)/Norway
|
|
Nicolas Pastorino
|
Monday 27 September 2010 9:31:38 am
Hi Steinar, These few dots aligned give us hard times understanding the point :) You may want to leave the original message in place (and mark it as solved if you got the appropriate answer through clicking the grey ticker at the left of the forum topic title). Cheers !
--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board
eZ Publish Community on twitter: http://twitter.com/ezcommunity
t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye
|
|
Tom W
|
Monday 27 September 2010 1:50:22 pm
Maybe I'm doing it wrong, but with the site I'm working on, we also have to move all uploaded files in "/var/.../storage" moving from server to server.
It's somewhat of a pain since it's a content heavy site.
|
|
Nicolas Pastorino
|
Monday 27 September 2010 2:07:48 pm
"
Maybe I'm doing it wrong, but with the site I'm working on, we also have to move all uploaded files in "/var/.../storage" moving from server to server.
It's somewhat of a pain since it's a content heavy site.
"
Changing server or hosting plan ? Or is this a regular event ?
--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board
eZ Publish Community on twitter: http://twitter.com/ezcommunity
t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye
|
|
Tom W
|
Tuesday 28 September 2010 9:03:01 am
It's a regular event.
moving things from dev, to staging, to product environment. It is the project development process used where I work.
I've read somewhere this is best done using siteaccess.
Though the thought of adding more of that will likely make things even more difficult to manage.
We are already using 2 siteaccess for languages(eng/fre), and another 3 to provide individual user group registration.
|
|
Quoc Huy Nguyen Dinh
|
Wednesday 29 September 2010 2:52:29 am
Do you mean when you move from dev to staging, then from staging to production you copy over the DB and all the files? This mean at all time the DB on dev and on staging must be the same as on production or production DB never gets modified live. If not items IDs will change constantly and copying /var/.../storage/... can give you some surprise. You better use some script to export/import. eZ Packages is always working but you could create your own script or use something like http://projects.ez.no/ezxmlinstaller I've done a lot of deployments like this and we've never needed to copy over anything in the var/ folder because our production website is being edited all the time.
|
|
Tom W
|
Wednesday 29 September 2010 11:42:19 am
Thanks for the link. Will see if it will be useful to some degree.
Anyhow, the site has not yet gone live, so all the content is being edited in dev or staging, moved to production for testing, which is why the var storage has to be copied from server to server.
It would be nice if all content editing happens on production and I don't have to do a thing about it.
Then again given the fact that the project wasn't properly scoped, it would be even more difficult. Merging content data, which functional(class, instant of class) data from the 2 env.
|
|
Nicolas Pastorino
|
Friday 01 October 2010 1:24:18 am
Hi guys, The link given by Quoc Huy is definitely a great extension. I have used this extensively on many a project. It basically helps circumventing one of eZ Publish's pet peeves : staging. ezxmlinstaller pushes to XML (thus versionable items) what one usually finds in the database. Content, and content structures. I usually am using this for content structures (read "content classes"). Cheers !
--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board
eZ Publish Community on twitter: http://twitter.com/ezcommunity
t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye
|