Two (or more) developpers, MODx and Git : possible ?

Hi,

I'm working on a very interesting project with another developer.
Together, will build MODx structure AND CSS via Sass files.

We want to be able to work on the same .sass files on the same time, so we want to use Git for the files.
For the MODx structure and content, it's more complicated and I thing the best way is to use the same database located on a webserver.

For the moment, the website is functional on a webserver.
I have set up a git depot the files

Locally, on my computer, I make a "git clone" of the files and this point is operational

I have modified my /core/config/config.inc.php to point to the webserver database and it's working (I will explain why later)
I have also modified the correct path on the files /core/config/config.inc.php and :

• config.core.php
• connectors/config.core.php
• manager/config.core.php

I'm running a xampp instance and when I go to http://localhost/ I can see the page almost perfectly : title, source code of the index page etc...

But somethings are not working :
- the menu (build why wayfinder) is absent while on the distant webserver, it's working perfectly
- the manager is not functional (blank page)

Is someone here use this kind of stuff to work on a project with other developers ?
With success ?
By using other solution (maybe more simple?)

why can't you work both remote at the same installation on a webserver?

Did you change the manager path settings in your /core/config/config.inc.php file? It's a little lower than the first couple of path files.
Also, you should turn on error reporting in your local .htaccess and make sure that's in your .gitignore
PHP will probably give you an error. What's the error?

@Bruno17, that's a really bad suggestion. They will probably overwrite each other's edits (they are both working on the same file at the same time, remember)

In fact, after (re)reflexion, I need this stuff because editing sass files directly on the server is less efficient than working on "local".
I can work localy peacefully and when I'm satisfied, I can push on the webserver.

But you're right bruno17, we can also work directly on the webserver with git... [ed. note: Spheerys last edited this post 12 years ago.]

That's one reason why I like using RO.IDEs and CssSweet for handling my CSS. Since the CSS is broken up across a number of resources, if one person wants to edit the "footer" resource he can, while someone else can be editing the "mainmenu" resource. Since MODX already provides edit locking, two people can't be editing the same resource at the same time.

I strongly recommend this book. It's easy to understand, and it has great examples of how to use Git with multiple developers: http://amzn.to/1w76jlA

BTW, If the Git repo is public, it's critical that you set Git to ignore the config files. If you have already pushed them to git, delete the repo and start over with them ignored. Otherwise, they'll always be there in the history and anyone can log in as you at your site.

Quote from: Magnatron at Oct 14, 2014, 08:56 AM

Did you change the manager path settings in your /core/config/config.inc.php file? It's a little lower than the first couple of path files.
Also, you should turn on error reporting in your local .htaccess and make sure that's in your .gitignore
PHP will probably give you an error. What's the error?

@Bruno17, that's a really bad suggestion. They will probably overwrite each other's edits (they are both working on the same file at the same time, remember)

That's just a matter of your workflow.
You can allways have versionized files for all developers.
A good editor should detect, if there was changes made by another one in the meantime, before saving the file.

Yes, even my simple free TextWrangler alerts me if a file I have open is edited by something else. For example, if I have a .css file open via SFTP, then edit it in the Manager.

It might be interesting to give Gitify a try. It's a new toolkit I'm working on that maks it possible to manage any type of data normally stored in the database, as files. It's not finished yet but here you go: https://github.com/modmore/Gitify

Also there's a video of my presentation about it at the MODX Weekend at https://video.modmore.com/modx-weekend-2014/sunday-backend/staging-workflow-with-git-and-gitify/

Quote from: sottwell at Oct 14, 2014, 07:13 AM

That's one reason why I like using RO.IDEs and CssSweet for handling my CSS. Since the CSS is broken up across a number of resources, if one person wants to edit the "footer" resource he can, while someone else can be editing the "mainmenu" resource. Since MODX already provides edit locking, two people can't be editing the same resource at the same time.

Hi Susan
I realise much water has passed under the bridge since this thread but I am having all sorts of problems with cssSweet. Beyond the default 'csss.custom_css.scss' file, it simply will not compile any other chunks I assign to the 'scss_chunks' plugin setting field.
I have created a chunk for each css module (header, footer etc) and pointed each chunk at their corresponding static resource. I have created a new property set and set the two system events to use that property set.
I have tried combinations of specifying paths, leaving as defaults etc etc.
I keep getting the console hanging on

I have found the author's various threads on the plugin, not very clear at all (to me anyway).
Can you possibly shed some some light on my woes?
This really seems to be the business if I can get it working.
Many thanks in advance.
Chris [ed. note: geordiechris last edited this post 8 years, 8 months ago.]