SUSE Package Hub 12 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-Standard-Pool Package Hub 12 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-Standard-Pool Package Hub 12 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP1 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP1-Standard-Pool Package Hub 12 SP1 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP1 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP1-Standard-Pool Package Hub 12 SP1 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP2 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP2-Standard-Pool Package Hub 12 SP2 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP2 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP2-Standard-Pool Package Hub 12 SP2 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP3 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP3-Standard-Pool Package Hub 12 SP3 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP3 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP3-Standard-Pool Package Hub 12 SP3 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP4 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP4-Standard-Pool Package Hub 12 SP4 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP4 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP4-Standard-Pool Package Hub 12 SP4 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP5 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP5-Standard-Pool Package Hub 12 SP5 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster. SUSE Package Hub 12 SP5 one-click install Install python-django-athumb NOTE: This one-click installation requires that the SUSE Package Hub extension to already be enabled. See http://packagehub.suse.com/how-to-use/ for information on enabling the Package Hub extension If the extension is not enabled, this installation will fail while trying to enable an invalid repo. This package might depend on packages from SUSE Linux Enterprise modules. If those modules are not enabled, a package dependency error will be encountered. SUSE-PackageHub-12-SP5-Standard-Pool Package Hub 12 SP5 Dummy repo - this will fail python-django-athumb A simple, S3-backed thumbnailer field Storing images and their thumbnails on S3 is a bit of a clumbsy endeavor with Django. While this Django app may work with more typical storage backends, it is intended to accept image uploads, thumbnail them, and upload the original plus the thumbs to S3. You may then get to the thumbnails in your template by doing something like: <img src="{% thumbnail some_obj.image '80x80' %}" /> This automatically assembles the remote S3 URL to retrieve the thumbnail from. No error checking is done, and several assumptions are made for the sake of speed. The primary advantage of django-athumb is that, unlike sorl and others, thumbnails are generated at the time of user uploading the original image. Instead of generating thumbs on-demand and making the user wait, we get that out of the way from the beginning. This leads to a few big benefits: * We never check for the existence of a file, after the first save/upload. We assume it exists, and skip a whole lot of Disk I/O trying to determine that. This was horrendously slow on sorl + S3, as it had to hit a remote service every time it wanted to know if a thumbnail needed generating. * Since we define every possible thumbnail in advance via models.py, we have a defined set of possible values. They can also be more intelligently named than other packages. It is also possible to later add more sizes/thumbs. * This may be ran on your own hardware with decent speed. Running it on EC2 makes it just that much faster.