Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#1025 closed task (fixed)

account to upload to

Reported by: robe Owned by: sac@…
Priority: normal Milestone:
Component: Systems Admin Keywords: download
Cc: pramsey


Can I have account/rights to upload to

I'll need it soon to upload the latest windows stable builds for upcoming 2.0.2 and 1.5.8.

Not sure it matters I currently lend my account for old postgis to the buildbots we have Winnie and Debbie (others may be born soon). They too will probably be uploading things. Like debbie will be uploading the latest tarballs and winnie might be uploading the buildbot windows experimental binaries.

Is it customary to give bots their own accounts or are they allowed to use mine? If they need their own, they'll also need a subversion account to post updates (though I think I have rights to do that)

Change History (3)

comment:1 by warmerdam, 10 years ago

Keywords: download added
Resolution: fixed
Status: newclosed


I have added account "robe" to the list that can ssh/sftp into (and a few other systems like the ProjectsVM).

I have also added group write permissions on /osgeo/download/postgis/source in the hopes that you will be able to write there. If not, Paul or I should be able to alter things as needed.

I don't have a strong answer to the accounts for robot uploads. I think you can decide yourself how to handle it, as long as the account is setup with an email address that ends up at a human who is somewhat responsible for the account.

Note that uploading nightly binary builds send to fill our backup system up with cruft.

comment:2 by robe, 10 years ago

As far as the nightly builds go - they all have the same name (we don't date interims) so it shouldn't fill up.

We just overwrite the same 2.1, 2.0, 1.5 SVN branches.

For the windows binaries, I'll probably just keep those on my server (and change the download page to point to my server uploading 200 MB each time a change is getting a bit much) or upload once a week. Those get overwritten too. Just one for each permutation of PostgreSQL 9.0 x64),9.1 (x64),9.2 (x32, x64) (for the 2.0 and 2.1 branches currently) -- so 10 in all.

comment:3 by warmerdam, 10 years ago

Regina - replacing the existing one in this fashion works nicely, thanks!

Note: See TracTickets for help on using tickets.