Adam Kiss Posted August 8, 2012 Share Posted August 8, 2012 Let's say there was a guy who was willing to open source of his code; Which files should not be included in the open git repository, so his site won't be compromised? Thanks Note: /site/config.php is a no-brainer Link to comment Share on other sites More sharing options...
JeffS Posted August 8, 2012 Share Posted August 8, 2012 Adam - without seeing the code I am not sure we can help. It's a mystery meat question, no? How about an outline? Link to comment Share on other sites More sharing options...
apeisa Posted August 8, 2012 Share Posted August 8, 2012 Adam: nothing else I guess. But if you do have written bad code in your templates, then of course one could use it against your site. Not sure why you want to do this? Allow people to contribute, to get feedback or as an example? If for example, one thing you could consider is releasing it as a site profile with dummy content or something like that. Link to comment Share on other sites More sharing options...
Adam Kiss Posted August 8, 2012 Author Share Posted August 8, 2012 It's a mystery meat question, no? How about an outline? Ouch, I didn't see this one coming. I want to put whole source code of my website online; disregarding any passwords in custom modules, what files should be ignored by .git [along /site/config.php]? Allow people to contribute, to get feedback or as an example? There won't be db dump, just for reading through code, I guess. Seeing how different people deal with ProcessWire in real situations. Seemed like a good idea ATM Link to comment Share on other sites More sharing options...
porl Posted August 9, 2012 Share Posted August 9, 2012 I think it's a great idea. Assuming you can do it without any compromising data I'd love to see how other's approach things. I'm still settling in and working out my optimal workflow with ProcessWire so any other approaches are good to compare. Link to comment Share on other sites More sharing options...
ryan Posted August 9, 2012 Share Posted August 9, 2012 You'd just want /site/templates/ right? Or perhaps /site/modules/ too if you've got any module dependencies in the templates. If you want to make it installable as a site profile, then you'd want to run the site profile exporter and include the /site/install/ directory too. But you'd want to double check that none of your module-specific passwords are getting included in the profile. Link to comment Share on other sites More sharing options...
Adam Kiss Posted August 9, 2012 Author Share Posted August 9, 2012 ryan: I don't want it as installable site profile; just dump my site code to github for people interested in it to see. 1 Link to comment Share on other sites More sharing options...
ryan Posted August 10, 2012 Share Posted August 10, 2012 I think the same applies whether site profile or not. Where have you written all your code? I'm guessing primarily just /site/templates/* but possibly /site/modules/ too. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now