First off, thanks for all of the great work on the site. Truly appreciated.
I’m posting to ask whether or not there’s a limit to the amount of entries that can be had in a CSV export. I tried doing this recently with my collection here on Grouvee and I keep getting a 504 error so I now wonder whether it’s because I have too many titles in my account.
Thanks in advance.
There’s not a limit, it just might be slower on a big library and time out. I know @aqwelorr was working on making it a little faster so it might not time out on a big library. We also should probably make it to where it just runs on the server for as long as it needs to run, then email you when it’s done with a link to the file.
Yeah I hope to get around to this soon 
It’s getting pretty slow with my collection (around 1000 games and over 100 shelves).
It’s getting pretty slow with my collection (around 1000 games and over 100 shelves).
I did my last backup about a year ago. i just tested it to see what would happen. was a slight delay (for browsing standards) but no time out error) 2.75 megs. (still a lot for text) my grouvee grew about .75 megs in a year. 
I dont have that many shelves. just big wishlist and played lists. statuses and reviews.
We also should probably make it to where it just runs on the server for as long as it needs to run, then email you when it’s done with a link to the file.
These discuss.grouvee forums have their own download feature. Not even sure if discuss is it’s own thing or something you made but i thought i’d mention it as it is nice the way it works (and works exactly as you describe). my friend has made sites that back themselves up time to time (usually daily and overnight) and a temp copy of whatever gets put somewhere in limbo. if you have something like that, then maybe a user request to pull from that overnight version and send it to an email might put less strain on server if current grouvee is actively generating things up to the minute or something like that in its current state (maybe more trouble than its worth)
FYI, anyone having trouble with exporting their collection to a CSV file because it’s so big that Grouvee times out, I’ve almost got a fix working. Instead of generating the file on the spot and returning it to you in the original request, it’ll generate the file in the background on the server, upload it to my Amazon servers, then email you a link to the file to download (it will also put a link on your Settings page for you). I’ve got the background task working, I just have to fix up the UI stuff. Hopefully I’ll be done this week.
OK, the export in the background seems to be working!
For those of you that have large collections, and were getting timeout errors when trying to export, try again. It should export the collection to a file in my Amazon S3 bucket, then it will email you a link to that file when it’s done.
Thanks for the patience!
Thank you very much! You are awesome!
I just tried this out with my collection and now I can see why I’ve been getting timeout messages. I did not expect over 6000 titles to eat up 4.7GB of space
So I actually found a bug with the CSV import. I’m not sure if its my large library causing it or something else but if I decide to sort out a column in the CSV file, I discover that each game entry is present 186 times. That explains why my file size is 4.7GB and why neither LibreOffice nor Google Docs can actually display everything in its entirety.
Just letting you know in case others run into this issue as well.
Hmm, I’ll take a look at that today.
After staring at my code for a really long time, I figured out that it’s the way it’s being written to Amazon’s S3 bucket. I use a library called django-storages, and it’s not doing it very well for a large file. I was able to generate a local file on the server just fine for you, so I’ll figure out how to make it work.
Alright, sorry for spamming your thread so much, but it should be working now. I did a manual export of your collection, and it uploaded the file to Amazon correctly. The way that django-storages code was written, it was trying to send the file up in parts, but every time it would send a “part,” it would send the entire file. So basically it wrote the file 186 times, or however many chunks it was. Try it again, and it should only be about 5 or 6 MB this time!
Thank you very much. Just did a download of the csv file and things are pretty much perfect. I only see one entry per game and the file is at a much more manageable size.
You are awesome!