Opened 6 years ago

Closed 6 years ago

#7048 closed Task/To do item (fixed)

publish trac configuration for SMO on git.mayfirst.org and on smo itself

Reported by: https://id.mayfirst.org/dkg Owned by: https://id.mayfirst.org/dkg
Priority: Medium Component: Tech
Keywords: support.mayfirst.org git trac svn-to-git Cc:
Sensitive: no

Description

our configuration for this site is stored locally on moses in revision control. It would be good to have it stored elsewhere too, and to have it visible here directly so we can refer to changes.

the revision control history probably needs to be reviewed for confidential information (and possibly pruned) before being re-published.

Change History (3)

comment:1 Changed 6 years ago by https://id.mayfirst.org/ross

  • Owner set to https://id.mayfirst.org/dkg
  • Status changed from new to assigned

I think you should handle this dkg, since you're much clearer on what data might pose security risks if stored in the repository.

~/ross

comment:2 Changed 6 years ago by https://id.mayfirst.org/dkg

  • Keywords svn-to-git added

We currently have some pieces of it in in svn, so this is another part of the svn-to-git push.

comment:3 Changed 6 years ago by https://id.mayfirst.org/dkg

  • Resolution set to fixed
  • Status changed from assigned to closed

I've reviewed the full repository and i believe that none of it is sensitive. we've done a pretty decent job of not keeping secret material in our config files :)

I've pushed this change live, along with a consolidation of tools for managing these repositories.

Future changes to the configuration of SMO should probably be done and tested locally, then pushed through the trac-smo repository, which can be found at the following URLs:

  • git://git.mayfirst.org/mfpl/trac-smo (fetch)
  • gitosis@git.mayfirst.org:mfpl/trac-smo (push)

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.