git - Prestashop Test/Production Server Best Practices -


we have eshop build on prestashop , developing new features every week. i'm writing here because don't find correct way update our production environment changes, without having upload code again or having upload modified files manually.

now work this:

  • our developers work local copies connected git repo.
  • once have new features , want create new release download latest version repo , test locally on computer.

=> here comes part don't like... :)

  • once tests have been passed in local copy take files have been modified (looking @ commits) , upload them manually development environment.
  • we test again , if works upload same files production environment.

we have been thinking in linking both environments source files repo well, don't link because don't want have .git folder published messing production code.

i didn't find way of having tested copy of our code pushed @ our git repository , update servers automatically, without having upload files manually or having upload entire folders (themes, classes, etc...) via ftp.

is there working prestashop , git , having nice automated system this? :)

many in advance!

regards,

jordi

here workflow use, it's (i guess) pretty standard:

  • one git repo
  • preprod domain
  • prod domain

all development done on branches, when it's ready ship merge on master. on preprod pull branch working on, , on production pull master. preprod , prod domain on same server, it's sub-domain htaccess protect it.

we use not prestashop every thing, works well.

for part want automatically pull code, must possible (à la heroku). me important is: should git everywhere , forget ftp. it's easier , you're sure need updated.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more