Learn how to import data from other providers to your installation of Donation Store
If you are moving from another provider, chances are you probably have some sort of data that you would like to import into Donation Store. Right now we support importing payment data. To allow for one single unified way to import data into Donation Store, there is an example CSV file of how the data should be structured. Depending on the provider, you will more than likely have to manually format some columns to ensure consistency.
When you upload the CSV file to Donation Store, it performs file operations on the data by opening and closing the CSV file. These operations, in any technology can be slow as the data is being read and written to and from the disk respectively. Because of this, the page may try and time out if you provide a file that is large enough. To combat this, before you upload, you will have to configure Gunicorn to not timeout and to just wait. This can be achieved using the --timeout flag set to some high number like 10000
This can be edited on the Donation Store daemon by visiting the following file
Once you've opened it, you should see the service declaration. On the ExecStart line, after --bind [your_ip], add the following timeout flag. The finished file should look like
[Unit] Description=donationstore daemon PartOf=donationstore.service After=donationstore.service [Service] User=donationstore Group=www-data WorkingDirectory=/home/donationstore/env ExecStart=/home/donationstore/env/bin/gunicorn DonationStoreV2.wsgi:application --bind [yourIP]:8000 --timeout 10000 --error-logfile /var/log/donationstore/error.log --access-logfile /var/log/donationstore/access.log [Install] WantedBy=donationstore.service
Reload the Daemon and Restart Donation Store
systemctl daemon-reload service donationstore restart
And that's it. When you are done, remove the timeout and restart again
It is widely known that if you open a CSV file with a tool like Excel, it can add some unknown special characters around certain pieces of text within the CSV file. This can stop the import from working correctly as the special characters can then be used when looking up packages by ID. To fix this, please open your CSV file using a plain text editor to see if those special characters have been added.