Mercurial > p > roundup > code
view website/www/contact.txt @ 8044:f9eaaa63fda2
build: update website build to sync built files
Sourceforge only supports python 2.7. Newer version of sphinx are
required to build docs and they don't work with 2.7.
Set up rsync targets that:
1) copy html build directory to sourceforge target directory
(dev_docs, production and user home directory)
2) backup existing sourceforge target directory re-sync so it
can be served without any missing files.
The Makefile now check to see if .orig or *~ files are present in the
html build tree. It lists the garbage file and fails if so.
Also inserts a .htaccess into the tree to prevent access to:
.buildinfo file
docs_backup-* files
*.orig
*~
The first one is a build artifact from newer version of sphinx.
The second is the backup directory created with all the original files
before a rsync from the local system is done to sourceforge. The backup
directory is timestamped with the time of its sync.
The last two are probably redundant since make html will fail if they
exist.
To rollback a sync:
move the target directory to a new name.
move the backup directory (in the renamed target directory) to the
old target directory name.
I added the --delete flag to remove files missing from the html
directory. Using the -no-times flags will create all new files with
the current directory. Using the --backup, --backup-dir flags backs up
all replaced/deleted files to backup-dir. The --exclude flag preserves
the backup directories on the sourceforge side. Without --exclude the
-delete flag would remove these backup-dir's. Note that
--delete-exclude must not be used otherwise the backup directories
will be deleted.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 26 Jun 2024 19:11:35 -0400 |
| parents | 79779293d77b |
| children |
line wrap: on
line source
.. meta:: :description: Instructions for contacting the authors of the Roundup Issue Tracker. Includes mailing lists (hosted by sourceforge), and the IRC channel #roundup on oftc. How to get support from people. Contact ======= We maintain the following mailing lists: .. rst-class:: linkspacing =================== ========================== =============================== List Name/Signup Archive link Purpose =================== ========================== =============================== roundup-users_ archives `[SourceForge]`__ how to use Roundup roundup-devel_ archives `[SourceForge]`__ develop new Roundup releases roundup-checkins_ archives `[SourceForge]`__ automated check-in messages =================== ========================== =============================== These lists are open-access, but moderated to protect them against spam. The email address is ``<the list name from above>@lists.sourceforge.net``. Please sign up if you intend to mail repeatedly. You may talk to Roundup developers directly using the `WebChat IRC`_ interface. You can also use an IRC client: irc://irc.oftc.net/roundup. .. _roundup-users: https://sourceforge.net/projects/roundup/lists/roundup-users .. _roundup-devel: https://sourceforge.net/projects/roundup/lists/roundup-devel .. _roundup-checkins: https://sourceforge.net/projects/roundup/lists/roundup-checkins .. __: https://sourceforge.net/p/roundup/mailman/roundup-users/ .. __: https://sourceforge.net/p/roundup/mailman/roundup-devel/ .. __: https://sourceforge.net/p/roundup/mailman/roundup-checkins/ .. _WebChat IRC: https://webchat.oftc.net/?randomnick=1&channels=roundup&prompt=1