- #Modx gitify which files should be version controlled skin
- #Modx gitify which files should be version controlled code
- #Modx gitify which files should be version controlled download
However, I'm conflicted as to how the upload/emailing of images should proceed I could either:Įmail the uploaded resources (up to 10 of) direct to the client, or use the API to create a PW page, add the uploaded resources to the page, save page, email resources from the page to the client, and then finally delete the page.
#Modx gitify which files should be version controlled download
User submits a frontend form containing a description of the resource, eg typical resource may be "Study of sustainability of commercial fishing in area X", along with a number of files, for example, shaded maps (image), spreadsheet of data, word or open document of evidence, and a number of other images.ğiles and text descriptions are emailed to my clientĜlient reads through and organises the files and text into one or more PDFs.Ĝlient creates a new PW page, adds a description of resource, and uploads PDF(s) to the page Users then view the PW page and can download or view the accompanying PDFs The final downloadable resources will be produced by my client from files and text (up to 10 files - pdfs, spreadsheets, images etc) uploaded by the user. I'm developing a site for a client which involves (non-logged in) users submitting resources which other anonymous users can then view or download.
#Modx gitify which files should be version controlled code
What I don't understand is the final two lines of Ryans sample where he uses the add method - what is this for? In my code the new repeater field is already added and saved into the page without using this method. So calling getNew() followed by save() creates and saves the new repeater item. I go into the PW admin and confirm it is indeed added to the page. $newroom = $pg->sRoomsRepeater->getNew() Īnd a new repeater is added to the page. Okay, I've followed this with my code as follows: $building->title = 'One Atlantic Center' Using repeaters for the first time and wanted some clarification In the repeater documentation it provides sample code for adding a new repeater via the api:
![modx gitify which files should be version controlled modx gitify which files should be version controlled](https://img.android-apk.org/imgs/2/f/3/2f39284c9ca8e2c513f127a6d3a2e606_screen.png)
#Modx gitify which files should be version controlled skin
Seems like there is a thousand ways to skin this particular cat and working out the best method for my particular workflow is, well. Please excuse if this is a basic question, I'm sure regular git users will think so, but I have to say, implementing git to this stage has been a bit of a mindf*** for me. gitignore handle this scenario and can I set different gitignores for dev and remote pushes? Or is there a better way? Should I be using a separate branch of the entire PW site to version control just the site folder and keep the main branch as my "site backup"?
![modx gitify which files should be version controlled modx gitify which files should be version controlled](https://dt7v1i9vyp3mf.cloudfront.net/styles/news_large/s3/imagelibrary/S/Spotlight-0114-01-0psxaAjrhq3dLtqq2Z7YIGHgBYjcDa1p.jpg)
htaccess or site/assets/files from dev to bitbucket, butĪllow push of /site/assets/files from remote to bitbucket (for pull into dev)ĭoes. There is also the issue of files such as. Also, as the website has a load of users altering images I want to be able to push the site/assets/files folder on the remote server bitbucket and then pull it onto my dev box every now and then, but never push it from dev to remote. I realise I could just version control the site/templates folder but I want the entire site on bitbucket so that it acts as a backup as much as anything else. Ok, now I have the entire PW site as the master branch. Much easier than manually transferring file I grant you that. So a simple git commit/push automatically updates my live site.
![modx gitify which files should be version controlled modx gitify which files should be version controlled](https://s3.amazonaws.com/cleantalk-screenshots/help/install-modx/modx_download_en.jpg)
My ideal workflow is really pretty simple Make changes and test on dev box, commit changes and push to bitbucket, and a bitbucket post hook then pushes the changes received on bitbucket to the remote server (live website) and does an automatic git update. So I've set up git on my dev box and also on the remote server, and have bitbucket in there also. is it really as common as the blogs I'm reading make it seem? Cos to be honest, getting to know git has not been cheap on my time!Īs a solo developer I'm finally taking the plunge into git, seems like everyone is obsessed with version controlling etc so I figure I'm a bit behind the times still manually transferring files. Als, I'd be interested to know how many PW users use version control to manage website deployments. I suspect I need to read up on "git submodule" to handle repos within repos. I'd still like to have the entire site as a repo for backup purposes (to bitbucket) but my understanding of git is still a little limited. For the images I'm talking about almost 2000 image folders with a 10-20 images per folder so doing this sync with WinSCP every few days was a drawn out process, now it's a couple of git commands and magic happens I might cron it as the icing on the cake. OK FWIW I've kind of achieved what I was after by creating a repo solely for pulling images (/site/assets/files) from remote server to dev box and another repo for the site/templates folder to upload all dev changes I make to the remote server.